Context Navigation

B. Obtain Slice

B.1 Select target aggregates

In this tutorial, we focus on ExoGENI and do not select any additional aggregates. In future tutorials we will present
how GIMI can support experiments on other aggregates and a combination of aggregates (e.g., ExoGENI and WiMAX).

B.2 Formulate slice topology for experiment, and build request rspec

We will not go into any detail on this topic since this is covered in the ExoGENI tutorial.

The steps described in Section B.2.1.2 do NOT have to be executed during the tutorial!! We are describing them in case you should have to change the credential configuration in .flukes.properties manually!

B.2.1.2 Before experimenters can use Flukes, its properties file has to be modified.

To verify settings right-click on each node and select Edit Properties

To create a slice enter your slice name gimiXX-tutorial in to the empty field next to the Submit Request button and the click the latter.

B.2.1.5 To check if all the resources have come up go to the Manifest View tab and enter your slice name (gimiXX-tutorial) into the empty field. Then click Query for Manifest. After a short moment a box with all the requested resources and their respective status will appear. (This box does not update automatically and you have to hit the Query for Manifest button again to receive and update).

B.2.1.6 GIMI specific post boot script. Each node uses the same image but runs a slightly different post boot script. The latter allows for individualized settings at each node. An example post boot script for NodeA is shown below:

#!/bin/bash
# Experiment slice name used by OMF. Should be unique for each experiment
sn=gimi30
# For now ExoGENI does not assign the "Name" assigned in Flukes as hostname. This will not be needed in future versions.
hostname nodeA
curl http://emmy9.casa.umass.edu/pingWrap.rb -o /root/pingWrap.rb
chmod +x /root/pingWrap.rb
#Adds the slice name to the resource controller configuration file
curl http://emmy9.casa.umass.edu/omf-resctl.yaml -o /etc/omf-resctl-5.4/omf-resctl.yaml
perl -i.bak -pe "s/\:slice\:/\:slice\: $sn/g" /etc/omf-resctl-5.4/omf-resctl.yaml
# The above updates require a restart of the OMF resource controller.
/etc/init.d/omf-resctl-5.4 restart

This section will NOT be covered during the tutorial!! Nevertheless, we describe in Section B.2.2 how you can use Omni to set up and ExoGENI slice should you consider not using Flukes for future experiments.

B.2.2 Omni

In this section, we present an alternative approach to setup a slice by using the Omni command line tools to reserve resources. To perform this task the following steps have to be executed:

B.2.2.1 The post boot script that is used in the case of slice reservation via Flukes has to be converted from an RDF file into a single bash script that takes slice name and node ID as arguments.

This script will be installed and executed on the nodes by an execute service defined in the rspec as follows:

B.2.2.2 The rdf file has to be converted into an rspec (see attached gec15-tutorial-gimi09-nospec.rspec). You will notice that the rspec has to be slice-specific because it needs to pass the slice name into the post boot script.

B.2.2.3 Then the following commands have to be executed to set up and manage the slice with Omni:

B.2.3 Register slice and node names (create Pubsub nodes)

The RCs and the EC communicate via an XMPP server. The GIMI XMPP is running on emmy9.casa.umass.edu.

The ExoGENI instances and the experiment slice should be registered with the XMPP server. You can achieve this using the OMF AM by issuing the following command from a terminal in the user workspace. In the following command, please change "gimiXX" to the user name provided to you.