Changes between Version 20 and Version 21 of GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure/Setup


Ignore:
Timestamp:
06/15/16 12:02:52 (3 years ago)
Author:
tteixeir@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure/Setup

    v20 v21  
    199199 
    200200
    201 
     201=== 3.3. Export the modified request RSpec ===
     202Now we will pull back some of the covers and inspect exactly what Jacks has been doing for us when preparing the RSpecs for the experiments we design.  Each node and link has a corresponding element in the RSpec, and the details of the component configuration (such as the install and execute services we requested above) are specified with attributes, or sometimes child elements, within those portions of the document.
     203 
     204{{{
     205#!html
     206<table><tr>
     207<td>
     208   <ol type='a'>
     209   <li>From the <i>Add Resources</i> window (see figure), select the <b>View
     210Rspec</b> button on the top right hand side.  This will bring up a pane showing the
     211current RSpec -- please take a moment to inspect it.  The `&lt;node&gt;` and `&lt;link&gt;` elements
     212contain the specification for the components we will request, and if you
     213look closely, you will be able to see the install and execute service
     214elements you added earlier.  Click on the "View RSpec" button again to return to the main screen.
     215   </li>
     216 
     217   </ol>
     218   </td>
     219   <td>
     220      <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/JacksLab1_7.png?format=raw" width='500'/>
     221         <br/>
     222         <b>Figure 3-4</b> View and save the final request RSpec
     223   </td>
     224</tr></table>
     225 
     226<table><tr>
     227<td>
     228   <ol type='a' start=2>
     229   <li>Use the <b>Download</b> button (in the lower left part of the screen next to Save RSpec) to
     230make a local copy of your RSpec with the name <tt>rspec.xml</tt>.  We'll use this in the next step to
     231demonstrate how other client tools also use RSpec files to communicate
     232requests to aggregate managers.</li>
     233   </ol>
     234</td></tr>
     235</table>
     236}}}
     237 
     238 
     239 
     240=== 3.4. Instantiate the new experiment using Omni ===
     241 
     242For this step, we'll change the approach a bit and switch to a new client tool, the command line Omni client.   
     243 
     244From a terminal, please enter the command:
     245{{{
     246$ omni -a AM_NICKNAME createsliver LabOne RSPEC_FILE
     247}}}
     248where {{{AM_NICKNAME}}} is the nickname for your assigned aggregate manager and {{{LabOne}}} is the name of the slice you created earlier (both of these are given on your worksheet).  {{{RSPEC_FILE}}} should be replaced with the filename of the RSpec you saved in step 3.4.
     249 
     250 
     251If all is well, Omni should give you a number of informational messages, such as:
     252{{{
     253INFO:omni:Loading config file /home/geni/.gcf/omni_config
     254}}}
     255 
     256It should quickly proceed to the point where it makes the request to the remote manager:
     257{{{
     258INFO:omni:Creating sliver(s) from rspec file /home/geni/Downloads/experiments.rspec for slice ...
     259}}}
     260
     261This step can sometimes be time-consuming, so please be patient.  If it succeeds, within a couple of minutes Omni should report:
     262{{{
     263INFO:omni: Completed createsliver:
     264}}}
     265
     266and your resource reservation is complete!
    202267 
    203268