Changes between Initial Version and Version 1 of GENIExperimenter/Tutorials/jFed/GettingStarted_PartII_ndn/Procedure/Setup

Timestamp:

06/20/16 14:49:41 (8 years ago)

Author:

tteixeir@bbn.com

Comment:

--

GENIExperimenter/Tutorials/jFed/GettingStarted_PartII_ndn/Procedure/Setup

@@ +1 @@
+= [wiki:GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ccn/Procedure/Setup  Understanding the AM API using Named Data Networking] =
+{{{
+#!html
+
+
+<div style="text-align:center; width:495px; margin-left:auto; margin-right:auto;">
+<img id="Image-Maps_5201305222028436" src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/Setup.jpg?format=raw" usemap="#Image-Maps_5201305222028436" border="0" width="495" height="138" alt="" />
+<map id="_Image-Maps_5201305222028436" name="Image-Maps_5201305222028436">
+<area shape="rect" coords="18,18,135,110" href="./Setup" alt="" title=""    />
+<area shape="rect" coords="180,18,297,111" href="http://groups.geni.net/geni/wiki/GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ccn/Procedure/Execute" alt="" title=""    />
+<area shape="rect" coords="344,17,460,110" href="http://groups.geni.net/geni/wiki/GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ccn/Procedure/Finish" alt="" title=""    />
+<area shape="rect" coords="493,136,495,138" href="http://www.image-maps.com/index.php?aff=mapped_users_5201305222028436" alt="Image Map" title="Image Map" />
+</map>
+<!-- Image map text links - End - -->
+
+</div>
+}}}
+
+
+
+== 1.  Design the Experiment ==
+  
+{{{
+#!html
+<table border="0">
+   <tr>
+     <td >
+        <ol type='a'><li>In today's experiment you will use resources at the aggregate listed on the worksheet. If you don't have a worksheet use <i>Clemson InstaGENI (aka instageni.clemson.edu)</i> </li>
+ </li>
+        </ol>
+     </td>
+   </tr>
+</table>
+}}}
+
+== 2.  Establish the Environment ==
+
+=== 2.1 Set up ssh keys and configure Omni ===
+
+If your account is from the [http://portal.geni.net GENI Portal] follow the instructions  [wiki:GENIExperimenter/Tutorials/jFed/GettingStarted_PartII_ccn/Procedure/omni-config here].
+
+If your account is from the iMinds member authority (https://www.wall2.ilabt.iminds.be) follow the instructions [http://trac.gpolab.bbn.com/gcf/wiki/OmniConfigure/AutomaticProtoGENI here].
+
+
+{{{
+#!comment
+
+=== 2.1 Pre-work: Ensure SSH keys are setup ===
+
+Verify that you have at least one public key associated with your account. To do that, after you login to the portal check under your Profile, under the `SSH keys` tab. If you do not have SSH keys associated yet, please follow the instructions on that tab of the Portal.
+
+=== 2.2 Configure Omni ===
+
+
+{{{
+#!html
+<table>
+<tr><td>
+        <ol type='a'>
+          <li>Login to the <a href="http://portal.geni.net"> GENI Portal </a> </li>
+           <li> Click on the `Profile tab` link on the top of your
+           screen. Then click on the `Configure omni` tab under
+           `PROFILE`.</li>
+        </ol>
+</td><td>
+           <img
+           src="http://trac.gpolab.bbn.com/gcf/raw-attachment/wiki/OmniConfigure/Automatic/ConfigureOmniTab.png"
+           width="400" /> 
+     <br />
+     <b>Figure 2-1</b> Click on the <i>Configure omni</i> tab under
+     <i>Profile</i>.</i>
+</td></tr>
+<tr><td>
+        <ol type='a' start='3'>
+           <li> Click on the `Download your omni data` button under step 2. </li>
+</ol>
+</td><td>
+           <img
+           src="http://trac.gpolab.bbn.com/gcf/raw-attachment/wiki/OmniConfigure/Automatic/DownloadOmniDataButton.jpg"
+           width="400" />
+     <br />
+     <b>Figure 2-2</b> <i>Download your omni data</i> under step 2.
+</td></tr>
+<tr><td>
+        <ol type='a' start='4'>
+           <li> If this is the first time you try to access your GENI
+           certificate you will have to generate one. Click on the
+           `generate a certificate` link.</li>
+</ol>
+</td><td>
+           <img
+           src="http://trac.gpolab.bbn.com/gcf/raw-attachment/wiki/OmniConfigure/Automatic/GenerateCertLink.jpg"
+           width="400" />
+     <br />
+     <b>Figure 2-3</b> Click on <i>Generate a certificate</i>.</i>
+</td></tr>
+<tr><td>
+        <ol type='a' start='5'>
+           <li> Unless you really understand how SSL certificates
+           work, choose the simple option. Click on the `Generate
+           Combined Certificate and Key File` button and then click on
+           `Close`.  You will be taken back to the download page with
+           the warning.  Reload the page to enable the download
+           button.</li>
+</ol>
+</td><td>
+           <img
+           src="http://trac.gpolab.bbn.com/gcf/raw-attachment/wiki/OmniConfigure/Automatic/SimpleOption.jpg"
+           width="350"/> 
+     <br />
+     <b>Figure 2-4</b> Click on <i>Generate Combined Certificate and Key File</i>.
+</td></tr>
+<tr><td>
+        <ol type='a' start='6'>
+           <li> If you are a member of more than one project, select
+           which project you would like to be the default one for
+           running experiments in GENI. You can always change the
+           project that is used by the `-r` command line option of
+           Omni.  Then click on `Download your omni data`.</li> 
+</ol>
+</td><td>
+        <img
+        src="http://trac.gpolab.bbn.com/gcf/raw-attachment/wiki/OmniConfigure/Automatic/DownloadOmniData.jpg"
+        width="400"/>  
+     <br />
+     <b>Figure 2-5</b> Click on <i>Download your omni data</i>.
+</td></tr>
+</table>
+<table>
+<tr><td>
+        <ol type='a' start='7'>
+           <li> The bundle will be saved at <code>~/Downloads/omni.bundle</code> </li>
+<li>Open a terminal window and type:<pre
+class="wiki">omni-configure</pre>The cert and key files you need will
+be installed in the appropriate folders.</li>
+</ol>
+</td></tr>
+</table>
+}}}
+
+}}}
+== 3.  Obtain Resources ==
+
+
+=== 3.1 Create a slice ===
+
+Create a slice using `omni` and the slice name of your choice.  From now on that slice name will be referred to as `SLICENAME`.
+{{{
+$ omni createslice SLICENAME
+}}}
+
+=== 3.2. Load a simple topology in jFed ===
+For this exercise, we will edit an existing RSpec file.  Start by loading this predefined topology into jFed.
+
+{{{
+#!html
+<table>
+<tr><td>
+  <ol type='a'>
+    <li>In the Portal, launch jFed for this slice.</li>
+    <li>From the <b>jFed Experimenter Toolkit</b> menu (see figure), select the <b>Open URL</b> button.</li>
+  </ol>
+  </td>
+  <td> 
+     <img border="0"
+        src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/JFedLab1_1.png?format=raw"
+        width=400 alt="Import an RSpec into jFed"  title="Import an RSpec into jFed" /> 
+     <br />
+     <b>Figure 3-1</b> <i>Import an RSpec into jFed.</i>
+  </td>
+</tr>
+</table>
+<table>
+<tr><td>
+  <ol type='a' start='3'>
+    <li>Enter the URL for the RSpec: <br>
+       <tt>http://www.gpolab.bbn.com/experiment-support/LabOne/ccnx/lab1ccn-3node-jfed-rawpc.xml</tt><br>
+    then click <b>Ok</b>.<br/>
+    </li>
+    <li>When jFed pops up a message asking you to pick a manager to use, select the manager listed on your worksheet from the
+    list.  After you pick an aggregate manager, a network topology should appear
+    on the canvas.
+
+
+<table id="Table_01" border="0" cellpadding="5" cellspacing="0">
+        <tr>
+<td> 
+     <img border="0"
+        src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/JFedLab1_2.png?format=raw"
+        width="400" alt="Pick Aggregate Manager"  title="Pick Aggregate Manager" /> 
+     <br />
+     <b>Figure 3-2</b> <i>Pick an Aggregate Manager.</i>
+  </td>
+<td>
+Because this RSpec file contains a generic description of resources and does not specify any particular aggregate manager, jFed will pop up a message asking you to specify an aggregate to use:
+<br/>
+<i>
+Assign these nodes now ....
+</i>
+</td>
+        </tr>
+</table>
+
+    </li>
+  </ol>
+</td>
+
+
+</tr></table>
+}}}
+
+=== 3.3. Modify the RSpec to automatically install and execute CCNX software ===
+
+For this experiment, we need to install the following software on the nodes:
+   * The CCNX software (ccnx-0.6.2.tar.gz)
+   * Scripts that set up the CCNX software (ccnx-setup.tar.gz)
+   * Scripts used to pull atmospheric precipitation data using the CCNX protocol (ccnx-atmos.tar.gz)
+
+When the nodes start up, we need the following scripts to be executed:
+   * Script that sets up the node (node-setup)
+   * Script that sets up the ccnx protocol (ccnx-setup)
+   * Script that setup up ccnx protocol routes (add-precip-routes)
+
+We automate the installation and running of the proper software using `install` and `execute` scripts in the RSpec. These can be added by double clicking on a node, and then clicking a "+" under the "Boot scripts" tab.
+
+{{{
+#!comment
+
+Most of the nodes have an install script specified for each of the three pieces of software listed above which loads a tarball of software onto each node:
+ * `http://www.gpolab.bbn.com/experiment-support/ccnx-xen/ccnx-0.6.2.tar.gz`
+ * `http://www.gpolab.bbn.com/experiment-support/ccnx-xen/ccnx-atmos.tar.gz`
+ * `http://www.gpolab.bbn.com/experiment-support/ccnx-xen/ccnx-setup.tar.gz`
+
+Likewise, the nodes have execute scripts to configure the software on each node:
+ * `cd /tmp/ccnx-setup && ./node-setup`
+ * `cd /tmp/ccnx-setup && ./add-precip-routes router`
+ * `cd /tmp/ccnx-setup && ./ccnx-setup router 5`
+}}}
+
+{{{
+#!html
+<table border="0" cellpadding="0" cellspacing="0"><tr><td><img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/warning-icon-hi.png?format=raw" width='50' height='50'/></td><td>
+You <i> DO NOT </i> have to specify install and execute scripts for the nodes as they have already been done for you.  You can check this by clicking on the icons for these nodes.
+<br/><br/>
+In general, be very careful when entering this information.  These commands will not
+be executed until the nodes boot up and may fail silently.
+</td></tr></table>
+}}}
+
+
+
+{{{
+#!html
+<table><tr>
+<td colspan=2>
+  <ol type='a'>
+     <li>Click on each node to manipulate details of the node configuration. The execute commands below are found under the "Boot scripts" tab.
+<br/><br/>
+The <tt>ccnx-setup</tt> execute command takes as parameters the name of a single "barrier" node, which must be up in order for the experiment to start, and the number of nodes in the topology as follows:
+<pre>ccnx-setup BARRIER_NODE NUM_NODES</pre>
+We will continue to use the node <tt>router</tt> as the barrier node.
+<br/><br/>
+We will add two nodes to the topology, so go ahead and change the number of nodes from 3 to 5.
+The new <tt>router</tt> execute command on <b>all three nodes</b> should be:
+<pre>cd /tmp/ccnx-setup && ./ccnx-setup router 5</pre>
+
+     </li>
+  </ol>
+</td>
+
+<td colspan=2>
+  <img src="http://groups.geni.net/geni/raw-attachment/wiki/GENIEducation/SampleAssignments/LabZero/Graphics/LabOne_JFed_Fig3-2.png" width='500'/>
+     <br />
+     <b>Figure 3-2</b> <i>Edit all three nodes</i>
+</td>
+</tr>
+</table>
+
+
+
+<table><tr>
+<td colspan=2>
+  <ol type='a' start='2'>
+     <li>Copy the <tt>user</tt> node by:
+<ul>
+<li>Click on the <tt>user</tt> node. </li>
+<li>Press the <b>Duplicate</b> button. </li>
+<li>A new node should appear. </li>
+<li>Double click on the new node and rename it <tt>user0</tt>.</li>
+<li>Remove each link connecting <tt>user0</tt> to the topology. Delete the link by right clicking on each link and selecting "Delete". You may need to move the nodes around to see the added links.</li>
+<li>Look at the install and execute scripts.  They should be the same as on the original <tt>user</tt> node.</li>
+</ul>
+     </li>
+     <li>Copy the <tt>router</tt> node the same way setting the name of the new node to be <tt>router1</tt>.  Be sure to delete the links from this node as well.</li>
+  </ol>
+</td>
+
+<td colspan=2>
+  <img src="http://groups.geni.net/geni/raw-attachment/wiki/GENIEducation/SampleAssignments/LabZero/Graphics/LabOne_JFed_Fig3-3.png" width='500'/>
+     <br />
+     <b>Figure 3-3</b> <i>Copy the <tt>router</tt> and <tt>user</tt> nodes.</i>
+</td>
+</tr>
+</table>
+<table><tr>
+<td colspan=2>
+  <ol type='a' start='4'>
+     <li>Draw a link between the <tt>router</tt> and <tt>router1</tt> nodes.</li>
+     <li>Draw another link between the new <tt>router1</tt> node and the <tt>user0</tt> node.</li>
+     <li>The topology should look like Figure 3-4</li>
+  </ol>
+</td>
+
+<td colspan=2>
+  <img src="http://groups.geni.net/geni/raw-attachment/wiki/GENIEducation/SampleAssignments/LabZero/Graphics/LabOne_JFed_Fig3-4.png" width='500'/>
+     <br />
+     <b>Figure 3-4</b> <i>Draw links to connect the nodes.</i>
+</td>
+</tr>
+</table>
+
+<table><tr>
+<td colspan=2>
+  <ol type='a' start='7'>
+     <li>Let the aggregate selecting IP addresses for you.  To do this, click on each link and set the "Configuration Type" field to "Auto".</li>
+     <li>
+The <tt>add-precip-routes</tt> execute command takes as a parameter the name of the "next hop" node, which is the next node on the path to the <tt>data</tt> node:
+<pre>add-precip-routes NEXT_HOP_NODE</pre>
+
+Edit the new <tt>router1</tt> node to point to <tt>router</tt>.
+<br/><br/>
+The new <tt>add-precip-routes</tt> execute command on <b>router1</b> should be:
+<pre>cd /tmp/ccnx-setup && ./add-precip-routes router</pre>
+</li>
+<li>
+Edit the new <tt>user0</tt> node to point to <tt>router1</tt>.
+<br/><br/>
+The new <tt>add-precip-routes</tt> execute command on <b>user0</b> should be:
+<pre>cd /tmp/ccnx-setup && ./add-precip-routes router1</pre>
+
+</li>
+  </ol>
+</td>
+
+<td colspan=2>
+  <img src="http://groups.geni.net/geni/raw-attachment/wiki/GENIEducation/SampleAssignments/LabZero/Graphics/LabOne_JFed_Fig3-5.png" width='500'/>
+     <br />
+     <b>Figure 3-5</b> <i>Edit the next hop on <tt>router1</tt> and <tt>user0</tt>.</i>
+</td>
+</tr>
+</table>
+}}}
+
+
+=== 3.4. Export the modified request RSpec ===
+Now we will pull back some of the covers and inspect exactly what jFed 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>jFed Experimenter Toolkit</i> window (see figure), select the <b>RSpec Editor</b> tab.  This will bring up a window 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.
+   </li>
+
+   </ol>
+   </td>
+   <td>
+      <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/JFedLab1_7.png?format=raw" width='400'/>
+         <br/>
+         <b>Figure 3-5</b> View the final request RSpec
+   </td>
+</tr></table>
+
+<table><tr>
+<td>
+   <ol type='a'>
+   <li>Use the <b>Save to file</b> button (in the upper left) to
+a local copy of your RSpec with the name <tt>ccn_precip.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>
+   <td>
+      <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/JFedLab1_8.png?format=raw" width='400'/>
+         <br/>
+         <b>Figure 3-6</b> Save the final request RSpec
+   </td>
+</tr>
+</table>
+}}}
+
+
+
+=== 3.6. 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 SLICENAME RSPEC_FILE
+}}}
+where {{{AM_NICKNAME}}} is the nickname for your assigned aggregate manager and {{{SLICENAME}}} 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 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!
+
+
+----
+= [wiki:GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ccn/Procedure/Setup  Introduction] =
+= [http://groups.geni.net/geni/wiki/GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ccn/Procedure/Execute Next:  Execute] =