Changes between Version 19 and Version 20 of IMInteroperability/SliceWithGIMIAndGEMINI


Ignore:
Timestamp:
08/02/13 16:32:48 (6 years ago)
Author:
koneil@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • IMInteroperability/SliceWithGIMIAndGEMINI

    v19 v20  
    3636./gdesktop-init.py -n GEMINIandGIMI -f ~/Downloads/geni-keleigh.pem
    3737}}}
     38 You should get output similar to this but the AM will be replaced with the one you used: [[BR]]
     39 [[Image(gdesktopInit.png, 40%)]][[BR]][[BR]]
    3840
    3941Instrumentize your slice by using the following command, replacing my slice name and sshkey location with yours.
     
    4143./gdesktop-instrumentize.py -n GEMINIandGIMI -f ~/Downloads/geni-keleigh.pem
    4244}}}
    43 [[BR]]
    44 When your slice finishes instrumentizing, login to the GENI Desktop and click on your slice there.
     45 You should get output similar to this: [[BR]]
     46 [[Image(gdesktopInstrument.png, 40%)]][[BR]]
     47'''When your slice finishes instrumentizing, login to the GENI Desktop and click on your slice there.'''
    4548[[BR]][[BR]]
    4649
     
    9093== Creation ==
    9194Use this [http://groups.geni.net/geni/attachment/wiki/IMInteroperability/SliceWithGIMIAndGEMINI/GIMI_GEC17wGN.xml rspec] to create ExoGENI slices in Flack that had both GIMI and GEMINI. Below is the topology created.[[BR]][[BR]]
    92 [[Image(GnGExoTopology.png, 50%)]]
     95[[Image(GnGExoTopology.png, 40%)]]
    9396[[BR]][[BR]]
    9497'''If you are creating your own topology here are some things to keep in mind:''' [[BR]]
     
    110113
    111114== GEMINI ==
    112 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.
     115The 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. 
     116=== GENI Desktop ===
     117Login to GENI Desktop before creating slice. Once on page with slices listed, go to address bar and change “stable” in the link to “dev” and refresh page. Keep this window open & create your slice as explained above. Go back to the GENI Desktop and refresh the page. [[BR]]
     118Follow the same steps for initializing and instrumentizing your slice as for with an InstaGENI slice. You will notice a green background when you are in development mode.
     119
     120=== Gdesktop Scripts ===
     121For the development version of the gdesktop scripts be sure to add the –devel flag as seen below when running all scripts.
     122{{{
     123./gdesktop-init.py -n GEMINIandGIMI2 -f ~/Downloads/geni-keleigh.pem  --devel
     124}}}
     125{{{
     126./gdesktop-instrumentize.py -n GEMINIandGIMI2 -f ~/Downloads/geni-keleigh.pem  --devel
     127}}}
     128
     129=== GENI Desktop Features ===
     130Within the GENI Desktop I could not see graphs or tables. I was able to SSH into the nodes via the GENI Desktop.
     131
    113132
    114133
     
    116135In !LabWiki run the four experiment  scripts on the slices just as you did with your InstaGENI slices. Instructions are [http://groups.geni.net/geni/wiki/IMInteroperability/SliceWithGIMIAndGEMINI#GIMI here]. Be sure to edit the boxes labelled source1 through source5 so they match the names of your nodes.
    117136
    118 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.
    119 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.
    120 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.
    121 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.