Changes between Version 41 and Version 42 of GENIEducation/SampleAssignments/UnderstandAMAPI/Procedure/DesignSetup


Ignore:
Timestamp:
02/12/14 15:50:32 (6 years ago)
Author:
sedwards@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIEducation/SampleAssignments/UnderstandAMAPI/Procedure/DesignSetup

    v41 v42  
    330330<tr><td>
    331331  <ol type='a' start='6'>
    332   <li>Once both the "install" and "execute" services are specified, please
    333 choose "Apply".  Then repeat the procedure to add the same "install" and
    334 "execute" services on the server node.
     332  <li>Once both the <i>install</i> and <i>execute</i> services are specified, please
     333choose <b>Apply</b>.  Then repeat the procedure to add the appropriate <i>install</i> and
     334<i>execute</i> services on the server node.
    335335  </li>
    336   <li> Also on the server node, click on the "link" tab
    337       and select "Routable Control IP" as shown in the figure.
     336  <li> Also on the server node, click on the <i>link</i> tab
     337      and select <b>Routable Control IP</b> as shown in the figure.
    338338  </li>
    339339</ol>
     
    346346         <br/>
    347347         <b>Figure 3-5</b> On the <i>Link</i> tab, select the
    348       "Routable Control IP" button.</i>
     348      "Routable Control IP" button.
    349349       </td>
    350350
     
    358358
    359359== 3.4. Export the modified request RSpec ==
    360 {{{
    361 #!html
    362 <p>Now we will pull back some of the covers and inspect exactly what Flack 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.</p>
     360Now we will pull back some of the covers and inspect exactly what Flack 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.
     361
     362{{{
     363#!html
    363364
    364365<table><tr>
    365366<td>
    366 <ol>
    367 <li>From the "View" menu (see figure), select the "Preview
    368 request document(s)" item.  This will bring up a window showing the
     367   <ol type='a'>
     368   <li>From the <i>View</i> menu (see figure), select the <b>Preview
     369request document(s)</b> item.  This will bring up a window showing the
    369370current RSpec -- please take a moment to inspect it.  The XML elements
    370371under the "<tt>flack</tt>" namespace were added for Flack's internal
    371372use (containing information about the canvas layout, editing history, etc.),
    372 and are ignored by aggregate managers.  The "node" and "link" elements
     373and are ignored by aggregate managers.  The `<node>` and `<link>` elements
    373374contain the specification for the components we will request, and if you
    374375look closely, you will be able to see the install and execute service
    375376elements you added earlier.</li>
    376 <li>Use the "Save to file" button (in the upper left) to
     377   <li>Use the <b>Save to file</b> button (in the upper left) to
    377378make a local copy of your RSpec.  We'll use this in the next step to
    378379demonstrate how other client tools also use RSpec files to communicate
    379380requests to aggregate managers.</li>
    380 </ol>
    381 </td>
    382 <td><img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/PortalOmniExample/ObtainResources/flack-view-small.png?format=raw" /></td>
     381   </ol>
     382   </td>
     383   <td>
     384      <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/PortalOmniExample/ObtainResources/flack-view-small.png?format=raw" width='400'/>
     385         <br/>
     386         <b>Figure 3-6</b> View and save the final request RSpec
     387   </td>
    383388</tr></table>
    384389}}}
     
    386391== 3.5. Instantiate the new experiment using Omni ==
    387392
    388 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:
     393For 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:
    389394
    390395{{{
     
    405410}}}
    406411
    407 This step can sometimes be time-consuming, so please be patient.  If it succeeds, within a few minutes Omni should report:
     412This step can sometimes be time-consuming, so please be patient.  If it succeeds, within a couple of minutes Omni should report:
    408413{{{
    409414INFO:omni: Completed createsliver:
    410415}}}
    411416
    412 and your sliver is complete!
     417and your resource reservation is complete!
    413418
    414419