Changes between Initial Version and Version 1 of GIR2.1_OnTimeMeasurements


Ignore:
Timestamp:
03/14/11 22:00:03 (13 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GIR2.1_OnTimeMeasurements

    v1 v1  
     1
     2= On Time Measuraments Tools =
     3
     4The On Time Measuraments tools V1.0 is still being evaluated.
     5
     6On Time Measurement software is available at:
     7{{{
     8 http://ontime.oar.net/download/OnTimeMeasure-v1.0.tar.gz
     9}}}
     10Software installation instructions are at available at:
     11{{{
     12 http://groups.geni.net/geni/wiki/OnTime-Installv1
     13}}}
     14
     15User account is required for Research Portal at http://ontime.oar.net/ to add and control !OnTimeMeasure service within user's ProtoGENI slice.
     16
     17An [http://groups.geni.net/geni/attachment/wiki/OnTimeMeasure/OnTimeMeasure-v1_Tutorial_061610.pdf OnTimeMeasure Tutorial] is available which provide a useful overview of features and usage.
     18
     19Time frame:  This evaluation took place from June 4 through July 21, 2010.
     20
     21= On Time Measurement Tools Findings =
     22
     23The software package delivers a README that includes Copyright information and some modification history. An installation pdf is enclosed, thus creating a need for an undocumented requirement to install acroread. Request was submitted for text install instructions.
     24
     25Suggested installation instruction document restructuring to streamline and clarify instructions to users. Found few prerequisites no captured. Requested that ports used be undocumented. See attached [http://groups.geni.net/syseng/attachment/wiki/GIR2.1_OnTimeMeasuraments/OnTimeMeasure_Install_Instructions-feedback-20100623.doc Install Feedback] for a complilation of feedback on installation instructions. Majority of input has been implemented in latest release.
     26
     27Suggested restructuring release package to simplify installation of the possible node types, input has been implemented in latest version, where the content of each node type is packaged individually. See attached [http://groups.geni.net/syseng/attachment/wiki/GIR2.1_OnTimeMeasuraments/Luisa-Feedback-Compilation_062310.pdf Feedback Compilation ]  for details and dispatch for each request.
     28
     29Various configuration syntax issues were found with files delivered, such as spaces being interpreted and case mismatch.  The graphite database had incorrect permissions, due to the installation script setting permissions at the wrong time.
     30
     31Outstanding Issues: 
     32 * Only one experiment can be handled per user account.
     33 * Once the experiment is defined it cannot be modified.
     34 * Domain names are not handled by parts the system.
     35
     36While evaluating this package found features that are not yet documented:
     37   * A Node Beacon can run both Centralized and Distributed orchestrations concurrently.
     38   * A node can run Root Beacon and Node Beacon concurrently.
     39
     40To Debug Ontime Measurament tools problems simply run all "nohup" processes in the fore ground without nohup.
     41This will show all operations in the xterm where the process is started.
     42
     43
     44= On Time Measurement Tools How-to =
     45
     46Installation instructions capture all requirements, also scripts are delivered that install all prerequisites.
     47
     48Two types of configurations are supported, which are referred to as orchestrations:
     49 * Distributed orchestration - Includes only Node Beacons
     50 * Centralized Orchestration - Includes Node Beacons and Root Beacons.
     51
     52
     53Following is a capture of the Centralized Orchestration On ProtoGENI Nodes.  Using ProtoGENI tools registered a slice:
     54{{{
     55lnevers@riva:~/protogeni-tests$ ./registerslice.py -n ln_slice_pgt
     56Got my SA credential
     57No such slice registered here:Creating new slice called ln_slice_pgt
     58New slice created: urn:publicid:IDN+emulab.net+slice+ln_slice_pgt
     59}}}
     60and created a sliver with 3 nodes:
     61{{{
     62lnevers@riva:~/protogeni-tests$ ./createsliver.py -n ln_slice_pgt 3node.xml
     63Got my SA credential
     64Asking for slice credential for ln_slice_pgt
     65Got the slice credential
     66Creating the Sliver ...
     67Created the sliver
     68<rspec xmlns="http://protogeni.net/resources/rspec/0.1">
     69 <node virtual_id="geni1" virtualization_type="raw" exclusive="1" component_urn="urn:publicid:IDN+emulab.net+node+pc321" component_uuid="de9ea263-773e-102b-8eb4-001143e453fe" component_manager_urn="urn:publicid:IDN+emulab.net+authority+cm" component_manager_uuid="28a10955-aa00-11dd-ad1f-001143e453fe" sliver_uuid="de9ea263-773e-102b-8eb4-001143e453fe" hostname="pc321.emulab.net" sshdport="22" sliver_urn="urn:publicid:IDN+emulab.net+sliver+12127">
     70   <interface virtual_id="virt0" component_id="eth4"/>
     71   <disk_image name="urn:publicid:IDN+emulab.net+image+emulab-ops//FEDORA8-STD"/>
     72 <services><login authentication="ssh-keys" hostname="pc321.emulab.net" port="22"/></services></node>
     73 <node virtual_id="geni2" virtualization_type="raw" exclusive="1" component_urn="urn:publicid:IDN+emulab.net+node+pc217" component_uuid="de9fca0e-773e-102b-8eb4-001143e453fe" component_manager_urn="urn:publicid:IDN+emulab.net+authority+cm" component_manager_uuid="28a10955-aa00-11dd-ad1f-001143e453fe" sliver_uuid="de9fca0e-773e-102b-8eb4-001143e453fe" hostname="pc217.emulab.net" sshdport="22" sliver_urn="urn:publicid:IDN+emulab.net+sliver+12128">
     74   <interface virtual_id="virt0" component_id="eth2"/>
     75   <interface virtual_id="virt1" component_id="eth4"/>
     76   <disk_image name="urn:publicid:IDN+emulab.net+image+emulab-ops//FEDORA8-STD"/>
     77 <services><login authentication="ssh-keys" hostname="pc217.emulab.net" port="22"/></services></node>
     78 <node virtual_id="geni3" virtualization_type="raw" exclusive="1" component_urn="urn:publicid:IDN+emulab.net+node+pc354" component_uuid="de9dfa4f-773e-102b-8eb4-001143e453fe" component_manager_urn="urn:publicid:IDN+emulab.net+authority+cm" component_manager_uuid="28a10955-aa00-11dd-ad1f-001143e453fe" sliver_uuid="de9dfa4f-773e-102b-8eb4-001143e453fe" hostname="pc354.emulab.net" sshdport="22" sliver_urn="urn:publicid:IDN+emulab.net+sliver+12129">
     79   <interface virtual_id="virt0" component_id="eth4"/>
     80   <disk_image name="urn:publicid:IDN+emulab.net+image+emulab-ops//FEDORA8-STD"/>
     81 <services><login authentication="ssh-keys" hostname="pc354.emulab.net" port="22"/></services></node>
     82 <link virtual_id="link0" link_type="VLAN" sliver_uuid="486be29b-8059-11df-ad83-001143e453fe" sliver_urn="urn:publicid:IDN+emulab.net+sliver+12130">
     83   <interface_ref virtual_interface_id="virt0" virtual_node_id="geni1" sliver_uuid="48c1eb45-8059-11df-ad83-001143e453fe" component_urn="urn:publicid:IDN+emulab.net+interface+pc321:eth4" sliver_urn="urn:publicid:IDN+emulab.net+sliver+12131" MAC="000423a8fc0e" IP="10.10.1.1"/>
     84   <interface_ref virtual_interface_id="virt0" virtual_node_id="geni2" sliver_uuid="49372ba4-8059-11df-ad83-001143e453fe" component_urn="urn:publicid:IDN+emulab.net+interface+pc217:eth2" sliver_urn="urn:publicid:IDN+emulab.net+sliver+12132" MAC="000423b71496" IP="10.10.2.1"/>
     85 </link>
     86 <link virtual_id="link1" link_type="VLAN" sliver_uuid="49f0b3ea-8059-11df-ad83-001143e453fe" sliver_urn="urn:publicid:IDN+emulab.net+sliver+12133">
     87   <interface_ref virtual_interface_id="virt1" virtual_node_id="geni2" sliver_uuid="4a815d37-8059-11df-ad83-001143e453fe" component_urn="urn:publicid:IDN+emulab.net+interface+pc217:eth4" sliver_urn="urn:publicid:IDN+emulab.net+sliver+12134" MAC="000423b714a6" IP="10.10.1.2"/>
     88   <interface_ref virtual_interface_id="virt0" virtual_node_id="geni3" sliver_uuid="4af60f64-8059-11df-ad83-001143e453fe" component_urn="urn:publicid:IDN+emulab.net+interface+pc354:eth4" sliver_urn="urn:publicid:IDN+emulab.net+sliver+12135" MAC="000423b71e02"/>
     89 </link>
     90<!--
     91 <valid_until>2010-08-14T12:00:00</valid_until>
     92 -->
     93</rspec>
     94}}}
     95
     96The above set up 3 FEDORA 8 nodes which are used as follows:
     97{{{
     98 pc133.emulab.net => Root Beacon
     99 pc135.emulab.net => Node Beacon
     100 pc141.emulab.net => Node Beacon
     101}}}
     102
     103Once the slices are created, the user request an account at the [http://ontime.oar.net/ OnTimeMeasure Portal].
     104The Registration request can be started by clicking on the "Register" button at  http://ontime.oar.net/.
     105This brings up the registration page:
     106
     107[[Image(2010-06-25_Ontime-0.jpg)]]
     108
     109
     110Once account is enabled, user must register the nodes that are part of the experiment by clicking the
     111"Create Measurements" button on main page:
     112
     113[[Image(2010-06-25_Ontime-1.jpg)]]
     114
     115Choosing "Create Measurement" brings up the "Resource Setup" Pages, which is the first of 3
     116steps required node to set up monitoring:
     117
     118[[Image(2010-06-28_Ontime-4.jpg)]]
     119
     120Next, the "Measurement Request Specification" must be defined where the user can choose the nodes, types of metric and time pattern to
     121be executed for the monitoring.  The following pages show two measurement tasks defined:
     122
     123[[Image(2010-06-28_Ontime-6.jpg)]]
     124
     125Once node are registered and measurements are defined the user start measurement collection:
     126
     127[[Image(2010-06-28_Ontime-7.jpg)]]
     128
     129
     130[[Image(2010-06-29_Ontime-8.jpg)]]
     131
     132Once measurements are being collected, the user may query for the measurement collected:
     133
     134[[Image(2010-07-21Ontime-11.jpg)]]
     135
     136Once data is collected, the user can view real-time graphs of measurement data details from the dashboard via their own graphite portal:
     137
     138
     139[[Image(2010-06-30_Ontime-9.jpg)]]
     140
     141''' MORE TO BE ADDED when DATA is collected and can be displayed in portal. '''