Changes between Version 3 and Version 4 of GENIExperimenter/Tutorials/SystematicExperimentationAnsible/Design


Ignore:
Timestamp:
09/17/15 19:38:31 (9 years ago)
Author:
sedwards@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/Tutorials/SystematicExperimentationAnsible/Design

    v3 v4  
    6666=== 3.1 Create Representative "Server" and "Client" Node Types ===
    6767
    68  1. Create a new slice.
    69  1. Click the Add Resources button to open the Add Resources page.
    70  1. Create a representative "server" node.  We will copy this node to make other servers.
    71    a. Drag a "Xen VM" onto the canvas (this is the multicolored icon on the left).
    72    a. Click on the node to display the configuration panel on the left.  The remaining items can all be set in this panel.
    73    a. Set the name of the node to "server".  The hostname of all of the servers will start with this string.
    74    a. Set the Icon for this node to be a "Server".  By setting the icon, it makes it easier to visually identify the node types.
    75    a. Give the node a "Publicly Routable IP".  This will allow users to access the webserver via the public Internet.
    76    a. Set the Disk Image to "Ubuntu 12.04 LTS". While there are defaults, it is usually good to configure the OS image so you know what you are getting.  In this case, we know how to configure a webserver and nmap on an Ubuntu disk image so we choose the OS appropriately.
    77  1. Create a representative "client" node.  We will copy this node to make other clients.
    78    a. Drag a default VM onto the canvas (this is the black icon on the left) and configure the fields described below.
    79    a. Set the name of the node to "client".
    80    a. Set the Icon for this node to a "Node".
    81  1. Draw a link between the two nodes.
    82  1. Save the RSpec with these two representatives node types to a file on your local machine.  For a real experiment, you would commit this file to a version control system for safe keeping.
     68{{{
     69#!html
     70<table border="0">
     71      <tr>
     72       <td >
     73         <ol  type='a'>
     74            <li>Create a new slice. </li>
     75            <li>Click the Add Resources button to open the Add Resources page.</li>
     76            <li>Create a representative "server" node.  We will copy this node to make other servers.
     77                <ol  type='i'>
     78                  <li>Drag a "Xen VM" onto the canvas (this is the multicolored icon on the left).</li>
     79                  <li>Click on the node to display the configuration panel on the left.  The remaining items can all be set in this panel.</li>
     80                  <li>Set the name of the node to "server".  The hostname of all of the servers will start with this string.</li>
     81                  <li>Set the Icon for this node to be a "Server".  By setting the icon, it makes it easier to visually identify the node types.</li>
     82                  <li>Give the node a "Publicly Routable IP".  This will allow users to access the webserver via the public Internet.</li>
     83                  <li>Set the Disk Image to "Ubuntu 12.04 LTS". While there are defaults, it is usually good to configure the OS image so you know what you are getting.  In this case, we know how to configure a webserver and nmap on an Ubuntu disk image so we choose the OS appropriately.</li>
     84                </ol>
     85            </li>
     86          </ol>
     87       </td>
     88       <td>
     89
     90        <img border="0" src="http://groups.geni.net/geni/raw-attachment/wiki/GENIExperimenter/Tutorials/SystematicExperimentationAnsible/Graphics/configserver.png" alt="Server node configuration"  width="400" title="Jacks" />
     91<br />
     92         <b>Figure 3-1</b> <i>Configuring the server node.</i>
     93       </td>
     94    </tr>
     95</table>
     96
     97<table border="0">
     98      <tr>
     99       <td >
     100         <ol  type='a'>
     101            <li>Create a representative "client" node.  We will copy this node to make other clients.
     102                <ol  type='i'>
     103                  <li>Drag a default VM onto the canvas (this is the black icon on the left) and configure the fields described below.</li>
     104                  <li>Set the name of the node to "client".</li>
     105                  <li>Set the Icon for this node to a "Node".</li>
     106                </ol>
     107            </li>
     108            <li>Draw a link between the two nodes.</li>
     109            <li>Save the RSpec with these two representatives node types to a file on your local machine.  For a real experiment, you would commit this file to a version control system for safe keeping.
     110</li>
     111          </ol>
     112       </td>
     113       <td>
     114
     115        <img border="0" src="http://groups.geni.net/geni/raw-attachment/wiki/GENIExperimenter/Tutorials/SystematicExperimentationAnsible/Graphics/notetypes.png" alt="Server and client nodes"  width="400" title="Jacks" />
     116<br />
     117         <b>Figure 3-2</b> <i>The server and client nodes.</i>
     118       </td>
     119    </tr>
     120</table>
     121}}}
     122
    83123
    84124Tip: For a real experiment, we would now define the IP addresses on the dataplane interfaces, reserve the topology, and write and test the automated configuration of the nodes for your experiment.  The idea is that by taking the time to properly automate the configuration of these two nodes, we will be able to build larger topologies easily.  This step may take some time, but in exchange it will make running the rest of the experiment quicker and easier and save you a great deal of frustration.  For today's exercise, this work has already been done and tested for you.