Version 1 (modified by, 12 years ago) (diff)


On Time Measuraments Tools

The On Time Measuraments tools V1.0 is still being evaluated.

On Time Measurement software is available at: 

Software installation instructions are at available at: 

User account is required for Research Portal at to add and control OnTimeMeasure service within user's ProtoGENI slice.

An OnTimeMeasure Tutorial is available which provide a useful overview of features and usage.

Time frame: This evaluation took place from June 4 through July 21, 2010.

On Time Measurement Tools Findings

The 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.

Suggested installation instruction document restructuring to streamline and clarify instructions to users. Found few prerequisites no captured. Requested that ports used be undocumented. See attached Install Feedback for a complilation of feedback on installation instructions. Majority of input has been implemented in latest release.

Suggested 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 Feedback Compilation for details and dispatch for each request.

Various 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.

Outstanding Issues:

  • Only one experiment can be handled per user account.
  • Once the experiment is defined it cannot be modified.
  • Domain names are not handled by parts the system.

While evaluating this package found features that are not yet documented:

  • A Node Beacon can run both Centralized and Distributed orchestrations concurrently.
  • A node can run Root Beacon and Node Beacon concurrently.

To Debug Ontime Measurament tools problems simply run all "nohup" processes in the fore ground without nohup. This will show all operations in the xterm where the process is started.

On Time Measurement Tools How-to

Installation instructions capture all requirements, also scripts are delivered that install all prerequisites.

Two types of configurations are supported, which are referred to as orchestrations:

  • Distributed orchestration - Includes only Node Beacons
  • Centralized Orchestration - Includes Node Beacons and Root Beacons.

Following is a capture of the Centralized Orchestration On ProtoGENI Nodes. Using ProtoGENI tools registered a slice:

lnevers@riva:~/protogeni-tests$ ./ -n ln_slice_pgt
Got my SA credential
No such slice registered here:Creating new slice called ln_slice_pgt
New slice created:

and created a sliver with 3 nodes:

lnevers@riva:~/protogeni-tests$ ./ -n ln_slice_pgt 3node.xml 
Got my SA credential
Asking for slice credential for ln_slice_pgt
Got the slice credential
Creating the Sliver ...
Created the sliver
<rspec xmlns=""> 
 <node virtual_id="geni1" virtualization_type="raw" exclusive="1" component_urn="" component_uuid="de9ea263-773e-102b-8eb4-001143e453fe" component_manager_urn="" component_manager_uuid="28a10955-aa00-11dd-ad1f-001143e453fe" sliver_uuid="de9ea263-773e-102b-8eb4-001143e453fe" hostname="" sshdport="22" sliver_urn=""> 
   <interface virtual_id="virt0" component_id="eth4"/> 
   <disk_image name=""/>
 <services><login authentication="ssh-keys" hostname="" port="22"/></services></node>
 <node virtual_id="geni2" virtualization_type="raw" exclusive="1" component_urn="" component_uuid="de9fca0e-773e-102b-8eb4-001143e453fe" component_manager_urn="" component_manager_uuid="28a10955-aa00-11dd-ad1f-001143e453fe" sliver_uuid="de9fca0e-773e-102b-8eb4-001143e453fe" hostname="" sshdport="22" sliver_urn=""> 
   <interface virtual_id="virt0" component_id="eth2"/>
   <interface virtual_id="virt1" component_id="eth4"/>
   <disk_image name=""/>
 <services><login authentication="ssh-keys" hostname="" port="22"/></services></node>
 <node virtual_id="geni3" virtualization_type="raw" exclusive="1" component_urn="" component_uuid="de9dfa4f-773e-102b-8eb4-001143e453fe" component_manager_urn="" component_manager_uuid="28a10955-aa00-11dd-ad1f-001143e453fe" sliver_uuid="de9dfa4f-773e-102b-8eb4-001143e453fe" hostname="" sshdport="22" sliver_urn=""> 
   <interface virtual_id="virt0" component_id="eth4"/>
   <disk_image name=""/>
 <services><login authentication="ssh-keys" hostname="" port="22"/></services></node>
 <link virtual_id="link0" link_type="VLAN" sliver_uuid="486be29b-8059-11df-ad83-001143e453fe" sliver_urn=""> 
   <interface_ref virtual_interface_id="virt0" virtual_node_id="geni1" sliver_uuid="48c1eb45-8059-11df-ad83-001143e453fe" component_urn="" sliver_urn="" MAC="000423a8fc0e" IP=""/> 
   <interface_ref virtual_interface_id="virt0" virtual_node_id="geni2" sliver_uuid="49372ba4-8059-11df-ad83-001143e453fe" component_urn="" sliver_urn="" MAC="000423b71496" IP=""/>
 <link virtual_id="link1" link_type="VLAN" sliver_uuid="49f0b3ea-8059-11df-ad83-001143e453fe" sliver_urn=""> 
   <interface_ref virtual_interface_id="virt1" virtual_node_id="geni2" sliver_uuid="4a815d37-8059-11df-ad83-001143e453fe" component_urn="" sliver_urn="" MAC="000423b714a6" IP=""/> 
   <interface_ref virtual_interface_id="virt0" virtual_node_id="geni3" sliver_uuid="4af60f64-8059-11df-ad83-001143e453fe" component_urn="" sliver_urn="" MAC="000423b71e02"/>

The above set up 3 FEDORA 8 nodes which are used as follows: => Root Beacon => Node Beacon => Node Beacon

Once the slices are created, the user request an account at the OnTimeMeasure Portal. The Registration request can be started by clicking on the "Register" button at This brings up the registration page:

Once account is enabled, user must register the nodes that are part of the experiment by clicking the "Create Measurements" button on main page:

Choosing "Create Measurement" brings up the "Resource Setup" Pages, which is the first of 3 steps required node to set up monitoring:

Next, the "Measurement Request Specification" must be defined where the user can choose the nodes, types of metric and time pattern to be executed for the monitoring. The following pages show two measurement tasks defined:

Once node are registered and measurements are defined the user start measurement collection:

Once measurements are being collected, the user may query for the measurement collected:

Once data is collected, the user can view real-time graphs of measurement data details from the dashboard via their own graphite portal:

MORE TO BE ADDED when DATA is collected and can be displayed in portal.

Attachments (11)

Download all attachments as: .zip