RiftWare installation (release 0): Difference between revisions

From OSM Public Wiki
Jump to: navigation, search
No edit summary
No edit summary
Line 59: Line 59:




the rest of this script can be run from inside the new VM [[ RiftWare Build VM Script ]]
the rest of this script can be run from inside the new VM [[ RiftWare Build VM Script ]]. Note that this script can also be used as a package list.


be sure to reboot the VM after building to load the new kernel
be sure to reboot the VM after building to load the new kernel

Revision as of 00:35, 12 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
    • 1 network interface to the OSM network
  • 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 - Build a VM from the outside

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:

 # sudo yum install git
 # git clone https://osm.etsi.org/gerrit/osm/riftware.git rift
 # cd rift
 # ./rift-shell
 # sudo ./scripts/vm_image/mkvmimg -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

 # sudo ./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 scripts/vm_image.


OPTION 2 - download a pre built image

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.

OPTION 3 - build a VM from the inside

This is the recommended base image: http://repo.riftio.com/releases/4.0/vm_images/Fedora-x86_64-20-20131211.1-sda.qcow2

resize the disk to 40 GB and set the root password

qemu-img create -f qcow2 -o preallocation=metadata rift.qcow2 40G
virt-resize --expand /dev/sda1 Fedora-x86_64-20-20131211.1-sda.qcow2 rift.qcow2
virt-sysprep --root-password password:xxxx  -a rift.qcow2

Instantiate an instance

  • allocate 4 CPUs and 32 GB RAM if you can
  • minimum is 1 vCPU and 8 GB RAM


the rest of this script can be run from inside the new VM RiftWare Build VM Script . Note that this script can also be used as a package list.

be sure to reboot the VM after building to load the new kernel


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

Configuration