Changes between Version 27 and Version 28 of GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure/Setup

06/17/16 16:25:22 (3 years ago)



  • GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure/Setup

    v27 v28  
    149149=== 3.1 Create a slice ===
    151 Create a slice using `omni` and the slice name of your choice.  From now on that slice name will be referred to as `LabOne`.
    152 {{{
    153 $ omni createslice LabOne
     151Create a slice using `omni` and the slice name of your choice.  From now on that slice name will be referred to as <SLICE_NAME>.
     153$ omni createslice <SLICE_NAME>
    201 === 3.3. Export your RSpec ===
     204 === 3.3. Modify the RSpec to automatically install and execute CCNX software ===
     206'''Background:''' For this experiment, we need to install the following software on the nodes:
     207   * The CCNX software (ccnx-0.6.2.tar.gz)
     208   * Scripts that set up the CCNX software (ccnx-setup.tar.gz)
     209   * Scripts used to pull atmospheric precipitation data using the CCNX protocol (ccnx-atmos.tar.gz)
     211When the nodes start up, we need the following scripts to be executed:
     212   * Script that sets up the node (node-setup)
     213   * Script that sets up the ccnx protocol (ccnx-setup)
     214   * Script that setup up ccnx protocol routes (add-precip-routes)
     216In the following steps we automate the installation and running of the software using install and execute scripts in the RSpec. 
     221<td colspan=2>
     222  <ol type='a'>
     223     <li>Click on the <b>collab node</b> (see figure) to manipulate details of the node configuration.
     226<table id="Table_01" border="0" cellpadding="5" cellspacing="0">
     227        <tr>
     228                <td>
     229                        <img src="" width="50" height="50" alt="Note">
     230               </td>
     232When you open the node information, you should see a new pane with fields to fill in like
     233in the figure.   
     235        </tr>
     239     </li>
     240 </ol>
     243<td colspan=2>
     244  <img src="" width='500'/>
     245     <br />
     246     <b>Figure 3-2</b> <i>Edit the nodes</i>
     253  <ol type='a' start='2'>
     255<li>The way we will request installation of the proper software and execution
     256of our experiment is to add <i>install</i> and <i>execute</i> services.
     260<img width='500' src="" />
     261     <br />
     262     <b>Figure 3-3</b> <i>Specify the install and execute scripts </i>
     271<td colspan=2>
     272<ol  type='a' start='3'>
     274You will be adding three install scripts.  First, select "<tt>Add</tt>" under the <b>Install Scripts</b> sections as shown.  In the box in the <b>URL</b> field enter (cut-and-paste): <br>
     276and enter
     278in the box under it (labeled 'Install Path:').
     281Now, select "<tt>Add</tt>" under the <b>Install Scripts</b> again.  This time add: <br>
     283and enter <br>
     285in the box under it (labeled 'Install Path:').
     288Similarly, add a third install service: 
     290and enter <br>
     292in the box under it (labeled 'Install Path:').  <strong> Note the different install directory this time. </strong>
     296  <li>In a similar manner, use the "<tt>Add</tt>" button under the <b>Execute Scripts</b> section to add three execute services on this node:
     299cd /tmp/ccnx-setup &&  ./node-setup
     300cd /tmp/ccnx-setup &&  ./add-precip-routes rsrchr
     301cd /tmp/ccnx-setup && ./ccnx-setup router 4
     303  </li>
     305<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
     306be executed yet, so it will be some time before you will see any relevant
     307error messages if there is a mistake here.</td></tr></table>
     308   </li> 
     309                </ol> 
     310                </table> 
     314  <ol type='a' start='5'>
     315  <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 icons for these nodes. </li>
     325=== 3.4. Export your RSpec ===
    202326Now 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) are specified with attributes, or sometimes child elements, within those portions of the document.
    240 === 3.4. Instantiate the new experiment using Omni ===
     362=== 3.5. Instantiate the new experiment using Omni ===
    242364For this step, we'll change the approach a bit and switch to a new client tool, the command line Omni client.