RiftWare installation (release 0): Difference between revisions

From OSM Public Wiki
Jump to: navigation, search
No edit summary
No edit summary
Line 54: Line 54:
  # make -j1  rw
  # make -j1  rw


== Step 3 -- run RIFT.ware ==
=Running=


Start the RIFT.ware Launchpad service
Start the RIFT.ware Launchpad service
  # make rw.start_lp
  # make rw.start_lp


Line 67: Line 66:
FYI...the keystroke sequence to exit screen is control-a control-d
FYI...the keystroke sequence to exit screen is control-a control-d


You can stop launchpad using  
You can stop launchpad using:
  # systemctl stop rwlp
  # systemctl stop rwlp


== Step 4 -- connect to the service ==
You can connect to the service via a web browser (Google Chrome version 50 or later is recommended). Open a browser and connect to https://1.2.3.4:8000 , replacing 1.2.3.4 with the IP address of your VM. Note that it uses https, not http.
 
Google Chrome version 50 or later is recommended.


Open a browser and connect to https://1.2.3.4:8000 , replacing 1.2.3.4 with the IP address of your VM. Note that it uses https, not http.


{{Feedback}}
{{Feedback}}

Revision as of 13:45, 26 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 - Download a pre built image

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

Create an instance:

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

Once done, from inside the new VM, follow these instructions (RiftWare Build VM Script) to install all required packages, including a new kernel. 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

Running

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

You can connect to the service via a web browser (Google Chrome version 50 or later is recommended). Open a browser and connect to https://1.2.3.4:8000 , replacing 1.2.3.4 with the IP address of your VM. Note that it uses https, not http.


Your feedback is most welcome!
You can send us your comments and questions to OSM_TECH@list.etsi.org
Or join the OpenSourceMANO Slack Workplace
See hereafter some best practices to report issues on OSM