Changes between Version 9 and Version 10 of LAMP/Tutorial


Ignore:
Timestamp:
09/21/10 02:18:34 (9 years ago)
Author:
fernande@cis.udel.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • LAMP/Tutorial

    v9 v10  
    22= LAMP I&M System: Tutorial =
    33
    4 Welcome to the LAMP I&M System tutorial. This tutorial will take you through the steps in creating a [https://www.protogeni.net/trac/protogeni/ ProtoGENI] slice with Instrumentation & Measurement (I&M) capabilities based on the [http://www.perfsonar.net/ perfSONAR framework] and the [http://psps.perfsonar.net/ perfSONAR-PS software suite]. This tutorial and the full documentation for the LAMP I&M System is still under development, but we have made a [wiki:LAMP/Tutorial#QuickStart Quick Start Guide] to get you started right away. Please feel free to contact us with questions or any type of feedback at lamp@damsl.cis.udel.edu.
     4Welcome to the LAMP Instrumentation & Measurement (I&M) System tutorial. This tutorial will take you through the steps in creating a [https://www.protogeni.net/trac/protogeni/ ProtoGENI] slice with Instrumentation & Measurement (I&M) capabilities based on the [http://www.perfsonar.net/ perfSONAR framework] and the [http://psps.perfsonar.net/ perfSONAR-PS software suite]. This tutorial and the full documentation for the LAMP I&M System is still under development, but we have made a [wiki:LAMP/Tutorial#QuickStart Quick Start Guide] to get you started right away. Please feel free to contact us with questions or any type of feedback at lamp@damsl.cis.udel.edu.
    55
    66== Getting Ready ==
     
    1717== Quick Start ==
    1818
    19 This section will guide you through creating and starting a slice, requesting a LAMP services certificate for you slice, uploading your experiment's topology to [http://groups.geni.net/geni/wiki/LAMP/Glossary#UNIS UNIS], and setting up the instrumentation and measurement of your slice.
     19This section will guide you through creating and starting a slice, requesting a LAMP services certificate for you slice, uploading your experiment's topology to [http://groups.geni.net/geni/wiki/LAMP/Glossary#UNIS UNIS], and setting up the instrumentation and measurement facilities of your slice. The expected time required to setup your slice with the LAMP I&M System is around 10 minutes. Following this guide through the end is aimed to take about 30 minutes. Let us know how long it takes you and places for improvement!
    2020
    2121=== Few words on the LAMP I&M System design ===
     
    2727- UNIS and Topology-based Configuration: xxxxxxx
    2828
    29 - perfSONAR-PS software suite: xxxxx
     29- I&M software (measurement tools and perfSONAR services): xxxxx
    3030
    3131
    3232All the services on the LAMP I&M System have Authentication and Authorization (AA) capabilities based on the ProtoGENI AA model. See our [http://groups.geni.net/geni/wiki/LAMP/AA AA page] for more information.
    3333
     34=== 1. Modifying the RSpec ===
     35
     36There's only one thing that '''must''' be done to have LAMP I&M on your slice: specify the LAMP disk image to be loaded on each node that needs I&M. The URN for the LAMP disk image is '''urn:publicid:IDN+emulab.net+image+GeniSlices//UBUNTU91-LAMP'''. See the [http://www.protogeni.net/trac/protogeni/wiki/RSpecRequestDiskImageExample RSpec Disk Image Example] and our tutorial RSpec below for how to specify the disk image to be used on a node.
     37
     38Nodes booting the LAMP disk image will have all the LAMP services available, but only the topology-based configuration service (pSConfig) will be running by default. This isn't very useful for the experimenter as not even the LAMP Portal will be accessible (remember that you have to specify in which node(s) the portal will be enabled). To make the process simpler to the user, an initial configuration for the slice can be specified on a LAMP extension to the RSpec. Let's see our tutorial's RSpec and go through the different elements to understand how this configuration can be specified. For this Quick Start guide we will use a very simple topology: two nodes will be connected through a link with 100ms latency and 0.05 loss, and a third node with no interfaces (only the control plane interface) will lodge the LAMP Portal (and eventually store host monitoring data). This is our RSpec:
     39
     40{{{
     41<rspec xmlns="http://protogeni.net/resources/rspec/0.2"
     42   xmlns:lamp="http://protogeni.net/resources/rspec/0.2/ext/lamp/1">
     43   
     44   <node virtual_id="node1" virtualization_type="raw" exclusive="1">
     45      <node_type type_name="pc" type_slots="1"/>
     46      <disk_image name="urn:publicid:IDN+emulab.net+image+GeniSlices//UBUNTU91-LAMP" />
     47      <lamp:config />
     48      <interface virtual_id="iface0"/>
     49   </node>
     50   
     51   <node virtual_id="node2" virtualization_type="raw" exclusive="1">
     52      <node_type type_name="pc" type_slots="1"/>
     53      <disk_image name="urn:publicid:IDN+emulab.net+image+GeniSlices//UBUNTU91-LAMP" />
     54      <lamp:config />
     55      <interface virtual_id="iface0"/>
     56   </node>
     57   
     58   <link virtual_id="link1" >
     59      <interface_ref virtual_node_id="client1" virtual_interface_id="iface0"/>
     60      <interface_ref virtual_node_id="client2" virtual_interface_id="iface0"/>
     61      <link_type type_name="ethernet" />
     62      <!-- bandwidth>1000000</bandwidth -->
     63      <latency>100</latency>
     64      <packet_loss>0.05</packet_loss>
     65   </link>
     66   
     67   <node virtual_id="lamp" virtualization_type="raw" exclusive="1">
     68      <node_type type_name="pc" type_slots="1"/>
     69      <disk_image name="urn:publicid:IDN+emulab.net+image+GeniSlices//UBUNTU91-LAMP" />
     70      <lamp:config>
     71         <lamp:service type="lamp_portal" enable="true" />
     72      </lamp:config>
     73   </node>
     74</rspec>
     75}}}
    3476
    3577