Revision as of 22:31, 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

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.

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

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

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

@@ Line 15: / Line 15: @@
 =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
 There are two ways to set up a build environment suitable for building RIFT.ware.
@@ Line 49: / Line 54: @@
   # ./rift-shell
   # make rw.ext
-Download confd-basic-6.0.linux.x86_64.zip from Cisco DevNet Downloads and extract the file to a location on your system.
-The zip archive contains several files, but you need only the following two:
-* confd-basic-6.0.linux.x86_64.installer.bin
-* confd-basic-6.0.libconfd.tar.gz
-Move or copy the extracted confd files to the following directories on the VM. Type y (yes) if you are prompted to overwrite existing files.
- # cd /home/rift
- # mv confd-basic-6.0.linux.x86_64.installer.bin modules/ext/mgmt/confd_basic
- # mv confd-basic-6.0.libconfd.tar.gz modules/ext/mgmt/libconfd/libconfd-basic-6.0
- # chmod +x modules/ext/mgmt/confd_basic/confd-basic-6.0.linux.x86_64.installer.bin
- # chmod +x modules/ext/mgmt/libconfd/libconfd-basic-6.0/confd-basic-6.0.libconfd.tar.gz
-Note: In RIFT.ware 4.1.1, if the operator tries to use the Logs feature, LogAnalyzer is unable to access /var/log/rift/rift.log because permissions on /var/log/rift are set to 600. To resolve permissions issues, run: chmod 755 /var/log/rift
 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 CONFD=BASIC rw
+  # make -j8 RIFT_AGENT_BUILD=XML_ONLY rw
 Start the RIFT.ware Launchpad service
+ # make rw.start_lp
-Change to the /home/rift directory:
+logs are in /var/log/rift/ and /var/log/launchpad_console.log
- # cd /home/rift
-Create the riftware-launchpad services directory:
- # mkdir -p .install/var/rift/services/riftware-launchpad/
-Copy the Launchpad helper scripts:
- # cp -p scripts/packaging/services/riftware-launchpad/rwlp-start.sh .install/var/rift/services/riftware-launchpad
- # cp -p scripts/packaging/services/riftware-launchpad/rwlp-stop.sh .install/var/rift/services/riftware-launchpad
- # cp -p scripts/packaging/services/riftware-launchpad/rwlp.screenrc .install/var/rift/services/riftware-launchpad
-Copy the rwlp.service to systemd location:
-  # install -p -D -m 644 scripts/packaging/services/riftware-launchpad/rwlp.service /usr/lib/systemd/system/rwlp.service
+You can attach to the session by running
-Reload systemd to process the new service:
+  # screen -R
-  # systemctl daemon-reload
+you can stop launchpad using
-Start the RIFT.ware Launchpad service:
+  # systemctl stop rwlp
- # service rwlp start
 if you have questions or hit any problems, please contact us at support-team@riftio.com

RiftWare installation (release 0): Difference between revisions