RiftWare installation (release 0)

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

Build and Installation procedure for R0

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/4.2.0/rift-build-latest.qcow2. Also download the ssh key from http://repo.riftio.com/releases/open.riftio.com/4.2.0/id_grunt

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 -j1  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

FYI...the keystroke sequence to exit screen is control-a control-d

you can stop launchpad using

# systemctl stop rwlp

Step 4 -- connect to the service

Google Chrome version 50 or later is recommended.

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