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

Timestamp:

06/15/16 12:02:52 (8 years ago)

Author:

tteixeir@bbn.com

Comment:

--

GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure/Setup

@@ -199 +199 @@
  
 
-
+=== 3.3. Export the modified request RSpec === 
+Now 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. 
+ 
+{{{ 
+#!html 
+<table><tr> 
+<td> 
+   <ol type='a'> 
+   <li>From the <i>Add Resources</i> window (see figure), select the <b>View 
+Rspec</b> button on the top right hand side.  This will bring up a pane showing the 
+current RSpec -- please take a moment to inspect it.  The `&lt;node&gt;` and `&lt;link&gt;` elements 
+contain the specification for the components we will request, and if you 
+look closely, you will be able to see the install and execute service 
+elements you added earlier.  Click on the "View RSpec" button again to return to the main screen. 
+   </li> 
+ 
+   </ol> 
+   </td> 
+   <td> 
+      <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/JacksLab1_7.png?format=raw" width='500'/> 
+         <br/> 
+         <b>Figure 3-4</b> View and save the final request RSpec 
+   </td> 
+</tr></table> 
+ 
+<table><tr> 
+<td> 
+   <ol type='a' start=2> 
+   <li>Use the <b>Download</b> button (in the lower left part of the screen next to Save RSpec) to 
+make a local copy of your RSpec with the name <tt>rspec.xml</tt>.  We'll use this in the next step to 
+demonstrate how other client tools also use RSpec files to communicate 
+requests to aggregate managers.</li> 
+   </ol> 
+</td></tr> 
+</table> 
+}}} 
+ 
+ 
+ 
+=== 3.4. Instantiate the new experiment using Omni === 
+ 
+For this step, we'll change the approach a bit and switch to a new client tool, the command line Omni client.   
+ 
+From a terminal, please enter the command: 
+{{{ 
+$ omni -a AM_NICKNAME createsliver LabOne RSPEC_FILE 
+}}} 
+where {{{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. 
+ 
+ 
+If all is well, Omni should give you a number of informational messages, such as: 
+{{{ 
+INFO:omni:Loading config file /home/geni/.gcf/omni_config 
+}}} 
+ 
+It should quickly proceed to the point where it makes the request to the remote manager: 
+{{{ 
+INFO:omni:Creating sliver(s) from rspec file /home/geni/Downloads/experiments.rspec for slice ... 
+}}} 
+
+This step can sometimes be time-consuming, so please be patient.  If it succeeds, within a couple of minutes Omni should report: 
+{{{ 
+INFO:omni: Completed createsliver: 
+}}} 
+
+and your resource reservation is complete!