Version 19 (modified by 11 years ago) (diff) | ,
---|
Table of Contents
GIMI & GEMINI on one InstaGENI slice
Creation
Start with this rspec which was created to use GIMI on InstaGENI. Create a couple slices & use that rspec in Flack with an InstaGENI aggregate. Then add GEMINI extensions through Flack. Here is an example of the final rspec at Utah InstaGENI. Below is the topology created.
GEMINI
There are two ways to initialize and instrumentize slices: through the GENI Desktop or using the gdesktop scripts. You only need to choose one of these two options.
GENI Desktop
Access the GENI Desktop at the following link: http://genidesktop.netlab.uky.edu/.
Login to the GENI Desktop using a supported clearinghouse. The GENI Desktop will direct you to your login page. Once you return to the GENI Desktop you will need to give your passphrase that you set when created your SSH key pair.
From the GENI Desktop you will be able to see your slices and their status. Click on the slice it want to initialize and the process will begin.
Once your slice has been initialized, click on the instrument to instrumentize your slice.
Instrumentation will take some time. When it is complete, a blue bar will appear at the top of your screen that you must click to reload your slice.
Gdesktop Scripts
On the GEC 17 tutorial VM, the gdesktop scripts are located at the following directory: ~/GEC17Tutorials/GEMINI/UW/geminiv2/. To run these scripts switch to this directory using the following command in the VM.
cd ~/GEC17Tutorials/GEMINI/UW/geminiv2/
To check the status of your slice, use the following command. In this example “GEMINIandGIMI” is the name of the slice and “~/Download/geni-keleigh.pem” is the location of my ssh key.
./gdesktop-opstatus-new.py -n GEMINIandGIMI -f ~/Downloads/geni-keleigh.pem
Initialize your slice using the following command, replacing my slice name and ssh key location with yours.
./gdesktop-init.py -n GEMINIandGIMI -f ~/Downloads/geni-keleigh.pem
Instrumentize your slice by using the following command, replacing my slice name and sshkey location with yours.
./gdesktop-instrumentize.py -n GEMINIandGIMI -f ~/Downloads/geni-keleigh.pem
When your slice finishes instrumentizing, login to the GENI Desktop and click on your slice there.
GENI Desktop features
SSH:
From the GENI Desktop you can SSH into your nodes. Click on the launch icon(which looks like a rocket ship) and select “SSH”. Then click on the node you want to SSH into and select “Open SSH”.
You may get a window saying that the site is untrusted. Continue and accept the security certificate.
Graphs:
To see graphs of the GENI Desktop, click on the launch icon(which looks like a rocket ship) and select “GEMINI Graphs”.
Select the graphs you would like to appear and the nodes for which you would like to see graphs. Then press "Add Graphs" or "Add Graphs with Title". You can click on these graphs to open them in a new window.
Global Node:
Access the global node by choosing GEMINI GN from the launch menu. From here you can choose “View Live Feed” which allows you to see all the tables and graphs stored within the global node and use tools such as Wireshark.
Click on “Open PS Config” to open a window that allows you to view active measurements & create various tests to run on your slice.
GIMI
Access LabWiki at the following link: http://labwiki.casa.umass.edu:4000/resource/login/openid.html. Login to LabWiki using your GENI Portal credentials. When prompted send your information to LabWiki.
Type “step” in the search bar below “Prepare”. It should give options. Select the script ending in “step1-ping_all.rb”. Click and drag the paper and pencil icon to the column titled “Execute”.
Type your experiment name and slice name in the respective boxes under the Execute column. Make any necessary edits to the boxes labeled source1 through source5 so that they match the names of your nodes(if you used the rspec above the node will already be named properly). Write “true” in the graph box.
Scroll to the bottom of the Execute column and click on “Start Experiment”. Your experiment will begin and you can see progress in the log under the Execute column. When the experiment end a thin green bar will appear in that column.
If you open your slice in the GENI Desktop you can see changes on the graphs shown by the GENI Desktop while LabWiki is running experiments.
Repeat these LabWiki steps with the scripts ending with “step2-routing.rb”, “step3-ping_e2e.rb”, and “step4-otg_nmetrics.rb”. The input will very depending on the experiment script.
GIMI & GEMINI on one ExoGENI slice
Creation
Use this rspec to create ExoGENI slices in Flack that had both GIMI and GEMINI. Below is the topology created.
If you are creating your own topology here are some things to keep in mind:
For GEMINI, the nodes must be named in a specific way. All global nodes must start with the prefix “GN-” and all other nodes must start with the prefix “MP-”. You will want to use an image from a GEMINI ExoGENI rspec for your global node rather than a GIMI image. Below is an example image for the global node:
<disk_image name="http://gemini.netlab.uky.edu/Images/vm/exogeni/centos/centos6.3-v1.0.7-GEMINI.xml" version="58b9dd5ff527b570398124443e17ac2e66925bbd"/>
GEMINI needs to execute commands on each node with sudo. Sudo requires that each node has a hostname that is resolvable. Thus we will include a postboot script that sets a unique hostname and adds an entry in the /etc/hosts file so the hostname can be resolved. This allows the sudo commands to run without returning an error code.
On your MP nodes include the following section of code to add this postboot script:
<services> <install url="http://emmy9.casa.umass.edu/InstaGENI_Images/install-script-gimi-exo.tar.gz" install_path="/tmp" /> <execute shell="/bin/bash" command="/tmp/postboot_script_exo.sh $sliceName $self.Name()"/> </services>
GEMINI
The stable version of the GENI Desktop does not currently handle ExoGENI slices. I used the development version of the GENI Desktop and the development version of the gdesktop scripts to initialize & instrumentize the slices. Within the GENI Desktop I could not see graphs or tables. I was able to SSH into the nodes via the GENI Desktop.
GIMI
In LabWiki run the four experiment scripts on the slices just as you did with your InstaGENI slices. Instructions are here. Be sure to edit the boxes labelled source1 through source5 so they match the names of your nodes.
Jeanne Ohren: 3. I think it might be good to have a little more detail about what the postboot script is doing. I probably didn't explain that in enough detail. Jeanne Ohren: GEMINI needs to execute commands on the node with sudo. Sudo requires that the node has a hostname that is resolvable. The postboot script that you give in the example sets a unique hostname and adds an entry in the /etc/hosts file so the hostname can be resolved. This allows the sudo commands to run without returning an error code. Jeanne Ohren: 4. In the section where you mention running the gdesktop scripts and GENI Desktop in dev mode, I think it would be helpful to include examples of how to do that. Jeanne Ohren: 5. In the GIMI section where you include the command lines for running the gdesktop scripts, I think it would be helpful to include the last few lines of the output so they know what to look for when the script runs successfully.
Attachments (36)
- GnGInstTopology.png (49.1 KB) - added by 11 years ago.
-
GIMI5nodeInstaGENInoAM.xml (7.8 KB) - added by 11 years ago.
GIMI with InstaGENI rspec
-
GnGInstaRspec.xml (11.8 KB) - added by 11 years ago.
Utah InstaGENI rspec with GIMI & GEMINI
- GnGSliceOnGENIDesktop.png (311.1 KB) - added by 11 years ago.
- LabwikiAndGENIDesktop.png (365.7 KB) - added by 11 years ago.
-
GIMI_GEC17wGN.xml (6.2 KB) - added by 11 years ago.
GIMI ExoGENI with GEMINI
- GnGExoTopology.png (44.6 KB) - added by 11 years ago.
- GENIDesktopLogin.png (30.9 KB) - added by 11 years ago.
- GENIDesktopLogin2.png (47.7 KB) - added by 11 years ago.
- GENIDesktopLoginSSHPass.png (51.4 KB) - added by 11 years ago.
- GENIDesktopClickInstrument.png (33.9 KB) - added by 11 years ago.
- GENIDesktopInstrumentized.png (37.5 KB) - added by 11 years ago.
- GENIDesktopSSHWindow.png (24.4 KB) - added by 11 years ago.
- GENIDeskopSSH.png (35.2 KB) - added by 11 years ago.
- GENIDesktopUntrustedSSH.png (64.0 KB) - added by 11 years ago.
- GENIDesktopLaunchGraphs.png (23.3 KB) - added by 11 years ago.
- GENIDesktopGraph.png (201.1 KB) - added by 11 years ago.
- GENIDesktopLaunchGN.png (106.5 KB) - added by 11 years ago.
- GENIDesktopActiveMeasure.png (197.4 KB) - added by 11 years ago.
- LabWikiSendInfo.png (24.8 KB) - added by 11 years ago.
- LabwikiTypeStep.png (17.9 KB) - added by 11 years ago.
- LabWikiStep1Save.png (44.2 KB) - added by 11 years ago.
- LabWikiStep1Drag.png (58.2 KB) - added by 11 years ago.
- GENIDesktopPickSlice.png (38.7 KB) - added by 11 years ago.
- LabWiki.png (75.3 KB) - added by 11 years ago.
- GENIDesktopInitialize.png (14.6 KB) - added by 11 years ago.
- LabWikiandGEMINIGraphs.png (408.6 KB) - added by 11 years ago.
- LabWikiEnd.png (56.9 KB) - added by 11 years ago.
- LabWikiExpRunning.png (121.4 KB) - added by 11 years ago.
- LabWikiStep1Input.png (74.1 KB) - added by 11 years ago.
- LabWikiStart2.png (54.9 KB) - added by 11 years ago.
- gdesktopInit.png (50.1 KB) - added by 11 years ago.
- gdesktopInstrument.png (52.6 KB) - added by 11 years ago.
- GENIDesktopStable.png (45.2 KB) - added by 11 years ago.
- GENIDesktopDevelopment.png (59.9 KB) - added by 11 years ago.
- GnGonExo.png (278.6 KB) - added by 11 years ago.