wiki:GIMI-GEC16-Tutorials/GIMI-GEC16-TutorialB/Slice

Version 4 (modified by divyashri.bhat@gmail.com, 7 years ago) (diff)

--

B. Obtain Slice

Image Map

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.


B.2 Acquire resources and load images/packages for I&M tools and experiment services

B.2.1 Flukes

B.2.1.1 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.

$ omf_create_psnode-5.4 "XMPP Server" mkslice "slice_name" "list_of_nodenames"

E.g., omf_create_psnode-5.4 emmy9.casa.umass.edu mkslice gimiXX nodeA nodeB nodeC nodeD nodeE

If this succeeds you should see an output similar to the one below

$ omf_create_psnode-5.4 emmy9.casa.umass.edu mkslice gimi28 nodeA nodeB nodeC nodeD nodeE
DEBUG: Try to connect to Pubsub Gateway 'emmy9.casa.umass.edu'...
DEBUG: Try to connect to Pubsub Gateway 'emmy9.casa.umass.edu:5222'...
DEBUG: Connected as 'aggmgr@emmy9.casa.umass.edu' to XMPP server: 'emmy9.casa.umass.edu'
Connected to PubSub Server: 'emmy9.casa.umass.edu'

You only need to create pubsub node once for each new slice name.

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

The steps described in Section B.2.1.3 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!

Open the properties file with your favorite text editor (e.g., nano):

$ nano ~/.flukes.properties

Then change the file as indicated below.

# Do not change these
orca.xmlrpc.url=https://geni.renci.org:11443/orca/xmlrpc
ssh.options=-o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -X
xterm.path=/usr/bin/xterm

user.keystore=/home/geni/.ssl/gimi30.jks
ssh.key=/home/geni/.ssh/geni_key
ssh.pubkey=/home/geni/.ssh/geni_key.pub

image1.name=gimi
image1.url=http://emmy9.casa.umass.edu/Disk_Images/ExoGENI/exogeni-umass-1.2.xml
image1.hash=49f0c193cc91d7b2fc1a6f038427935f4c296a8a

image2.name=gimi-ovs
image2.url=http://emmy9.casa.umass.edu/Disk_Images/ExoGENI/exogeni-umass-ovs-1.0.2.xml
image2.hash=de35e71b31771870bcdfcccb4dee11657ba145b8

The following video gives more details on the necessary changes of the file.

B.2.1.3 In the tutorial VM start Flukes and load gimiXX.rdf. (Also here, replace gimiXX with your assigned user ID.) In Flukes select Files->Open Request->select gimiXX.rdf in ~/Tutorials/GIMI/gimiXX.

B.2.1.4 Verify settings and create slice.

  • First select the the Request View tab.
  • To verify settings, right-click on each node and select Edit Properties, inspect, and close if everything looks right. In case you detect an error (which we don't expect for the tutorial) you can fix it here and then save a new version of the RDF file by clicking on File from the top menu in Flukes and selecting Save Request.
  • To create a slice enter your slice name gimiXX in to the empty field next to the Submit Request button and the click the latter.
  • When you are prompted for login please enter the following data: Key alias: gimiXX Password: The one that has been handed out to you

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) 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. This script is already part of the gimiXX.rdf file. 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

The following video gives an overview on how to load an RDF file, request a slice, and verify the creation of a slice with Flukes.

B.2.1.6 Information about the ExoGENI image we use for this tutorial can be found here.


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.

http://groups.geni.net/geni/wiki/GIMI-GEC16-Tutorials/GIMI-GEC16-TutorialB/Environment Back to previous step

http://groups.geni.net/geni/wiki/GIMI-GEC16-Tutorials/GIMI-GEC16-TutorialB/Orchestrate Forward to next step

http://groups.geni.net/geni/wiki/GIMI-GEC16-Tutorials/GIMI-GEC16-TutorialB/ Back to tutorial main page