RiftWare installation (release 0): Difference between revisions

From OSM Public Wiki
Jump to: navigation, search
No edit summary
No edit summary
Line 19: Line 19:
These instructions have been updated for the code that will be pushed very soon. In the mean time, you should go back to version that does not include this notice
These instructions have been updated for the code that will be pushed very soon. In the mean time, you should go back to version that does not include this notice


== STEP 1 -- build or download a build VM ==


There are two ways to set up a build environment suitable for building RIFT.ware.  
There are two ways to set up a build environment suitable for building RIFT.ware.  
Line 46: Line 48:


Log in as root using the ssh key downloaded above, e.g <pre>ssh -l root -i id_grunt 1.2.3.4</pre> or use Horizon to install your own ssh keys.  
Log in as root using the ssh key downloaded above, e.g <pre>ssh -l root -i id_grunt 1.2.3.4</pre> or use Horizon to install your own ssh keys.  
== Step 2 -- build RIFT.ware ==


Download the RIFT.ware source code from ETSI
Download the RIFT.ware source code from ETSI
Line 58: Line 63:


  # make -j8 RIFT_AGENT_BUILD=XML_ONLY rw
  # make -j8 RIFT_AGENT_BUILD=XML_ONLY rw
== step 3 -- run RIFT.ware ==


Start the RIFT.ware Launchpad service
Start the RIFT.ware Launchpad service
Line 70: Line 77:
you can stop launchpad using  
you can stop launchpad using  
  # systemctl stop rwlp
  # systemctl stop rwlp
== step 4 -- connect to the service ==
open a browser and connect to https://1.2.3.4:8000 -- replace 1.2.3.4 with the IP address of your VM.
note that this is now https, not http




if you have questions or hit any problems, please contact us at support-team@riftio.com
if you have questions or hit any problems, please contact us at support-team@riftio.com

Revision as of 22:34, 3 May 2016

VM creation

  • Requirements:
    • 1 VCPU (16 recommended)
    • 8 GB RAM (32 GB recommended)
    • 40 GB disk storage available on the hypervisor to hold the disk image
  • Base image: Fedora 20 (fc20) or later

Installing required packages and libraries

Building and installing the module

Configuring

Previous installation procedure

IMPORTANT

These instructions have been updated for the code that will be pushed very soon. In the mean time, you should go back to version that does not include this notice


STEP 1 -- build or download a build VM

There are two ways to set up a build environment suitable for building RIFT.ware.


OPTION 1 - If you have a recent Fedora machine (fc20 or later), you can extract the code from the ETSI repo, run the mkvmimg script in the scripts/vm_image directory with the -m build option and build your own VM image:

 # git clone https://osm.etsi.org/gerrit/osm/riftware.git rift
 # cd rift
 # ./rift-shell
 # ./scripts/vm_image/mkvmimage -c -m build -e 8

Note that the same procedure can produce a smaller image that only has the components needed to run RIFT.ware Launchpad

 # ./scripts/vm_image/mkvmimage -c -m ui

If you are curious about the packages needed to build and/or run RIFT.ware, examine the files in script/vm_image.


OPTION 2 - you can download the images from http://repo.riftio.com/releases/open.riftio.com/latest/rift-build-latest.qcow2. Also download the ssh key.


Launch the build VM, Please allocate at least the following resources to the VM:

  • 1 VCPU (16 recommended)
  • 8 GB RAM (32 GB recommended)
  • 40 GB disk storage available on the hypervisor to hold the disk image

Log in as root using the ssh key downloaded above, e.g

ssh -l root -i id_grunt 1.2.3.4

or use Horizon to install your own ssh keys.


Step 2 -- build RIFT.ware

Download the RIFT.ware source code from ETSI

# rm -rf /home/rift 
# cd /home
# git clone https://osm.etsi.org/gerrit/osm/riftware.git rift
# cd rift
# ./rift-shell
# make rw.ext

Build. Depending on the amount of memory allocated to the VM, you can adjust the -j setting. With 8 GB RAM, use -j1. With 32 GB RAM, you can use -j8 and the build will be much faster.

# make -j8 RIFT_AGENT_BUILD=XML_ONLY rw

step 3 -- run RIFT.ware

Start the RIFT.ware Launchpad service

# make rw.start_lp

logs are in /var/log/rift/ and /var/log/launchpad_console.log

You can attach to the session by running

# screen -R

you can stop launchpad using

# systemctl stop rwlp

step 4 -- connect to the service

open a browser and connect to https://1.2.3.4:8000 -- replace 1.2.3.4 with the IP address of your VM.

note that this is now https, not http


if you have questions or hit any problems, please contact us at support-team@riftio.com