Changes between Version 16 and Version 17 of PhoebusExperimentGEMINI


Ignore:
Timestamp:
03/20/13 18:06:12 (6 years ago)
Author:
kissel@cis.udel.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PhoebusExperimentGEMINI

    v16 v17  
    4242== 4. Create the experiment slice ==
    4343
    44 We will do this through Flack with InstaGENI AMs.
     44OUr experiment topology will be generated in Flack on InstaGENI racks at Kentucky and Utah.
     45
     46Use the "Flack GENI Client" link in the bookmarks par to load the Flack interface.
     47
     48Select UKY and Utah instageni AMs.
    4549
    4650[[Image(select_am.png)]]
    4751
     52Create your topology as shown using VM nodes from either UKY or Utah.
     53
    4854[[Image(flack_topo.png)]]
     55
     56Click on the "i" on each node to configure additional properties, such as the node name and the desired IP addresses.
    4957
    5058[[Image(flack_config_node.png)]]
    5159
     60To allow for GEMINI instrumentation, enable the GEMINI extensions in the right-most tab as shown in the screenshot.  Selecting this extension will automatically create an additional node in your experiment for measurement configuration and collection.
     61
    5262[[Image(flack_gemini_button.png)]]
     63
     64To modify the request RSpec in the following steps, you need to save the RSpec to your local filesystem.  Click on View->Request RSpec to display the XML representation of your topology and save to file as shown.
    5365
    5466[[Image(flack_save_request.png)]]
    5567
    56 Now we do some editing of the request RSpec. [http://groups.geni.net/geni/attachment/wiki/PhoebusExperimentGEMINI/edit_rspec.sh edit_rspec.sh]
     68Now we do some editing of the request RSpec. Either download or save the following script in your working directory.
     69
     70[http://groups.geni.net/geni/attachment/wiki/PhoebusExperimentGEMINI/edit_rspec.sh edit_rspec.sh]
    5771
    5872{{{
     
    7387}}}
    7488
     89The script adds extra service elements to each node that will allow a custom script to be executed when the node boots.  In our case, this script will download and install the Phoebus software packages and other supporting scripts needed for the experiment.  Your own experiments may have many such scripts, each of which is completely customizeable.
     90
     91
     92At this point our request RSpec is ready to go.  We now want to interact with the GENI control framework to instantiate our experiment.  In this tutorial, we will use Omni.
     93
    7594First, renew the slice created in Flack via Omni.
    7695
    7796[[Image(omni_renew_slice.png)]]
    7897
    79 Create the slivers at each AM.  (ig-utah and/or ig-ky)
     98You now want to invoke "createsliver" to create the slivers at each AM involved in your experiment topology.  In our case, this is either ig-utah or ig-ky as configured in your Omni configuration file.
    8099
    81100[[Image(omni_create_uky.png)]]
    82101
     102
     103After the request is submitted, Omni can be used to monitor the slice status.  More conveniently, you can reload the slice in Flack and watch the progress until your slice display turns green.
     104
     105
    83106== 5. Instrument the slice ==
     107
     108Now that the slice is created, you may instrument the slice with GEMINI.  The GENI Desktop provides this same functionality via a browser interface, but here we will use the "instrumentize" scripts available on the UW VM.
     109
     110Note that you specify your slice name and the location of your SSL certificate when executing these scripts. 
    84111
    85112{{{
     
    90117geni@GEC16-Tutorials:~/src/GEMINI/geminiv2$ ./gdesktop-instrumentize.py -n ezraslice2 -f ~/.ssl/geni_cert.pem
    91118}}}
     119
     120Once these scripts return, your slice has been instrumentized and will begin collecting default, passive measurements.  We will visit the GENI Desktop in later sections, but while the slice is being instrumented, we can use this time time to login and configure our nodes for our experiment.
    92121
    93122== 6. Login and configure experiment nodes ==
     
    150179Note that this step requires that you first login to your Slice Authority Emulab site.
    151180
     181Explore the desktop.
     182
     183For our experiment, we'd also like to measure the latency across all of our nodes.  We can use the active measurement configuration page to do so.
     184
    152185[[Image(desktop_psconfig.png)]]
     186
     187You may add new ping tests under "Schedul BLiPP Test".
    153188
    154189[[Image(psconfig_ping.png)]]
     
    156191== 8. Run experiments ==
    157192
     193
     194
    158195== 9. View results ==