Changes between Initial Version and Version 1 of GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ccn/Procedure/Setup

10/16/14 13:03:12 (8 years ago)



  • GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ccn/Procedure/Setup

    v1 v1  
     1= [wiki:GENIExperimenter/Tutorials/GettingStarted_PartII_ccn/Procedure/Setup  Understanding the AM API using Content Centric Networking] =
     6<div style="text-align:center; width:495px; margin-left:auto; margin-right:auto;">
     7<img id="Image-Maps_5201305222028436" src="" usemap="#Image-Maps_5201305222028436" border="0" width="495" height="138" alt="" />
     8<map id="_Image-Maps_5201305222028436" name="Image-Maps_5201305222028436">
     9<area shape="rect" coords="18,18,135,110" href="./Setup" alt="" title=""    />
     10<area shape="rect" coords="180,18,297,111" href="./Execute" alt="" title=""    />
     11<area shape="rect" coords="344,17,460,110" href="./Finish" alt="" title=""    />
     12<area shape="rect" coords="493,136,495,138" href="" alt="Image Map" title="Image Map" />
     14<!-- Image map text links - End - -->
     21== 1.  Design the Experiment ==
     25<table border="0">
     26   <tr>
     27     <td >
     28        <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</i> </li>
     29 </li>
     30        </ol>
     31     </td>
     32   </tr>
     36== 2.  Establish the Environment ==
     38=== 2.1 Pre-work: Ensure SSH keys are setup ===
     40Verify 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.
     42=== 2.2 Configure Omni ===
     49        <ol type='a'>
     50          <li>Login to the <a href=""> GENI Portal </a> </li>
     51           <li> Click on the `Profile tab` link on the top of your
     52           screen. Then click on the `Configure omni` tab under
     53           `PROFILE`.</li>
     54        </ol>
     56           <img
     57           src=""
     58           width="400" />
     59     <br />
     60     <b>Figure 2-1</b> Click on the <i>Configure omni</i> tab under
     61     <i>Profile</i>.</i>
     64        <ol type='a' start='3'>
     65           <li> Click on the `Download your omni data` button under step 2. </li>
     68           <img
     69           src=""
     70           width="400" />
     71     <br />
     72     <b>Figure 2-2</b> <i>Download your omni data</i> under step 2.
     75        <ol type='a' start='4'>
     76           <li> If this is the first time you try to access your GENI
     77           certificate you will have to generate one. Click on the
     78           `generate a certificate` link.</li>
     81           <img
     82           src=""
     83           width="400" />
     84     <br />
     85     <b>Figure 2-3</b> Click on <i>Generate a certificate</i>.</i>
     88        <ol type='a' start='5'>
     89           <li> Unless you really understand how SSL certificates
     90           work, choose the simple option. Click on the `Generate
     91           Combined Certificate and Key File` button and then click on
     92           `Close`.  You will be taken back to the download page with
     93           the warning.  Reload the page to enable the download
     94           button.</li>
     97           <img
     98           src=""
     99           width="350"/>
     100     <br />
     101     <b>Figure 2-4</b> Click on <i>Generate Combined Certificate and Key File</i>.
     104        <ol type='a' start='6'>
     105           <li> If you are a member of more than one project, select
     106           which project you would like to be the default one for
     107           running experiments in GENI. You can always change the
     108           project that is used by the `-r` command line option of
     109           Omni.  Then click on `Download your omni data`.</li>
     112        <img
     113        src=""
     114        width="400"/> 
     115     <br />
     116     <b>Figure 2-5</b> Click on <i>Download your omni data</i>.
     121        <ol type='a' start='7'>
     122           <li> The bundle will be saved at <code>~/Downloads/omni.bundle</code> </li>
     123<li>Open a terminal window and type:<pre
     124class="wiki">omni-configure</pre>The cert and key files you need will
     125be installed in the appropriate folders.</li>
     131== 3.  Obtain Resources ==
     134=== 3.1 Create a slice ===
     136Create a slice using `omni` and the slice name of your choice.  From now on that slice name will be referred to as `SLICENAME`.
     138$ omni createslice SLICENAME
     141=== 3.2. Load a simple topology in Flack ===
     142For this exercise, we will edit an existing RSpec file.  Start by loading this predefined topology into Flack.
     148  <ol type='a'>
     149    <li>In the Portal, launch Flack for this slice.</li>
     150    <li>From the <b>Import</b> menu (see figure), select the <b>Import from the web</b> item.</li>
     151  </ol>
     152  </td>
     153  <td>
     154     <img border="0"
     155        src=""
     156        alt="Import an RSpec into Flack"  title="Import an RSpec into Flack" />
     157     <br />
     158     <b>Figure 3-1</b> <i>Import an RSpec into Flack.</i>
     159  </td>
     164  <ol type='a' start='3'>
     165    <li>Enter the URL for the RSpec: <br>
     166       <tt> </tt> <br>
     167    then click <b>Ok</b>.<br/>
     168    </li>
     169    <li>When Flack pops up a message asking you to pick a manager to use click <b>OK</b> and then select the manager listed on your worksheet from the
     170    list.  After you click <b>Accept</b>, and a network topology should appear
     171    on the canvas.
     174<table id="Table_01" border="0" cellpadding="5" cellspacing="0">
     175        <tr>
     176                <td>
     177                        <img src="" width="50" height="50" alt="Note">
     178               </td>
     180Because this RSpec file contains a generic description of resources and does not specify any particular aggregate manager, Flack will pop up a message asking you to specify an aggregate to use:
     183There were resources detected without a manager selected, please select which manager you would like to use.
     186        </tr>
     189    </li>
     190  </ol>
     197=== 3.3. Modify the RSpec to automatically install and execute CCNX software ===
     199For this experiment, we need to install the following software on the nodes:
     200   * The CCNX software (ccnx-0.6.1-F15-x64.tar.gz)
     201   * Scripts that set up the CCNX software (ccnx-setup.tar.gz)
     202   * Scripts used to pull atmospheric precipitation data using the CCNX protocol (ccnx-atmos-F15-x64.tar.gz)
     204When the nodes start up, we need the following scripts to be executed:
     205   * Script that sets up the node (node-setup)
     206   * Script that sets up the ccnx protocol (ccnx-setup)
     207   * Script that setup up ccnx protocol routes (add-precip-routes)
     209We automate the installation and running of the software using install and execute scripts in the RSpec.
     214<td colspan=2>
     215  <ol type='a'>
     216     <li>Click on the the <i>i</i> button on the <b>collab node</b> (see figure) to manipulate details of the node configuration.
     219<table id="Table_01" border="0" cellpadding="5" cellspacing="0">
     220        <tr>
     221                <td>
     222                        <img src="" width="50" height="50" alt="Note">
     223               </td>
     225When you open the node information, you should see options like those
     226in the figure. 
     228        </tr>
     232     </li>
     233  </ol>
     237<td colspan=2>
     238  <img src="" width='400'/>
     239     <br />
     240     <b>Figure 3-2</b> <i>Edit the nodes</i>
     246<tr><td colspan='2'>
     247  <ol type='a' start='2'>
     249<li>The way we will request installation of the proper software and execution
     250of our experiment is to add <i>install</i> and <i>execute</i> services.
     255<td colspan='2'>
     256<img width='800' src="" />
     257     <br />
     258     <b>Figure 3-3</b> <i>Specify the install and execute scripts </i>
     262<td colspan=2>
     263<ol  type='a' start='3'>
     265First, select "<tt>+ Add Install Service</tt>" as shown.  In the box the Install box enter (cut-and-paste): <br>
     267and enter
     269in the box next to it (labeled 'in').
     272Now, select "<tt>+ Add Install Service</tt>" again.  This time add: <br>
     274and enter <br>
     276in the box next to it (labeled 'in').
     279Similarly, add a third install service:
     281and enter <br>
     283in the box next to it (labeled 'in').  <strong> Note the different install directory this time. </strong>
     287  <li>In a similar manner, use the "<tt>+ Add Execute Service</tt>" button to add three execute services on this node:
     290cd /tmp/ccnx-setup &&  ./node-setup
     291cd /tmp/ccnx-setup &&  ./add-precip-routes rsrchr
     292cd /tmp/ccnx-setup && ./ccnx-setup router 4
     294  </li>
     296<table border="0" cellpadding="0" cellspacing="0"><tr><td><img src="" width='50' height='50'/></td><td>Be very careful when entering this information -- these commands will not
     297be executed yet, so it will be some time before you will see any relevant
     298error messages if there is a mistake here.</td></tr></table>
     299  </li>
     307  <ol type='a' start='5'>
     308  <li>Once both the <i>install</i> and <i>execute</i> services are specified, click <b>Apply</b>. 
     309  </li>
     310  <li> You <i> DO NOT </i> have to specify install and execute scripts for the other nodes as they have already been done for you.  You can check this by clicking on the i button next to the icons for these nodes.
     321=== 3.4. Add GEMINI extensions ===
     322This assignment has the option of instrumenting the experiment and viewing graphs of traffic on links using the GENI Desktop.  To prepare for this option, you need to turn on GEMINI extensions.  Do this by
     326  <tr>
     327    <td>
     328      <ol type='a'>
     329       <li> Select the tab in the middle panel of Flack with the 'puzzle piece' icon </li>
     330       <li> Check the box "Use GEMINI Extensions" </li>
     331       </ol>
     332     </td>
     333     <td>
     334         <img width='500' src="" />
     335              <br />
     336              <b>Figure 3-4</b> <i>Add GEMINI Extensions</i>
     337      </td>
     338  </tr>
     342=== 3.5. Export the modified request RSpec ===
     343Now 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.
     349   <ol type='a'>
     350   <li>From the <i>View</i> menu (see figure), select the <b>Preview
     351request document(s)</b> item.  This will bring up a window showing the
     352current RSpec -- please take a moment to inspect it.  The XML elements
     353under the "<tt>flack</tt>" namespace were added for Flack's internal
     354use (containing information about the canvas layout, editing history, etc.),
     355and are ignored by aggregate managers.  The `&lt;node&gt;` and `&lt;link&gt;` elements
     356contain the specification for the components we will request, and if you
     357look closely, you will be able to see the install and execute service
     358elements you added earlier.
     359   </li>
     361   </ol>
     362   </td>
     363   <td>
     364      <img src="" width='400'/>
     365         <br/>
     366         <b>Figure 3-5</b> View and save the final request RSpec
     367   </td>
     372   <ol type='a'>
     373   <li>Use the <b>Save to file</b> button (in the upper left) to
     374a local copy of your RSpec with the name <tt>lab1_rspec.xml</tt>.  We'll use this in the next step to
     375demonstrate how other client tools also use RSpec files to communicate
     376requests to aggregate managers.</li>
     377   </ol>
     384=== 3.6. Instantiate the new experiment using Omni ===
     386For this step, we'll change the approach a bit and switch to a new client tool, the command line Omni client. 
     388From a terminal, please enter the command:
     390$ omni -a AM_NICKNAME createsliver SLICENAME RSPEC_FILE
     392where {{{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.
     395If all is well, Omni should give you a number of informational messages, such as:
     397INFO:omni:Loading config file /home/geni/.gcf/omni_config
     400It should quickly proceed to the point where it makes the request to the remote manager:
     402INFO:omni:Creating sliver(s) from rspec file /home/geni/Downloads/experiments.rspec for slice ...
     405This step can sometimes be time-consuming, so please be patient.  If it succeeds, within a couple of minutes Omni should report:
     407INFO:omni: Completed createsliver:
     410and your resource reservation is complete!
     414= [wiki:GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ccn/Procedure/Setup Introduction] =
     415= [ Next:  Execute] =