Changes between Version 1 and Version 2 of OTM-CustomMetric


Ignore:
Timestamp:
11/12/11 10:38:22 (10 years ago)
Author:
Prasad Calyam
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OTM-CustomMetric

    v1 v2  
    1212To integrate your custom measurement metrics in your application into !OnTimeMeasure, you will need to provide information on: '''''Control Actors''''', '''''Control Actions''''', '''''Data Sources''''' and '''''Data Structures'''''.
    1313
    14  [[Image(arch1.png, 50%)]]
     14 [[Image(custom-metric-concept.png, 50%)]]
    1515
    1616 * '''''Control Actors''''': Project members or your research experiment who can provide the “slice password” to the !OnTimeMeasure instance in an experiment slice, and would access the I&M data or share the data with other actors
     
    154154From Researcher Web-portal (!OnTimeBeacon):
    155155
    156  [[Image(Query.png, 50%)]]
     156 [[Image(query.png, 50%)]]
    157157
    158158Or, From Command-line (!OnTimeControl):
     
    176176== 3. Underlying Process for Custom Metric Integration within !OnTimeMeasure ==
    177177
    178 [[Image(arch2.png,60%)]]
     178[[Image(custom-metric-integrations.png,60%)]]
    179179
    180180With the slice password, the Control Actor (person or program) has access to Root Beacon and Node Beacons through the Researcher web-portal (http://ontime.oar.net) or command-line tool (!OnTimeControl).
     
    190190The experiment is conducted on machines from two different data centers in Utah and Kentucky. As illustrated in figure below, node fe1, bl1 and be1 are located in Utah; Node fe2 and bl2 are located in Kentucky. A delay node (bridge-0) is deployed on the path between fe1 and bl1 nodes to change the link delays. Instrumented web applications are running on all nodes. MySQL server is installed on be1 to host the application database.
    191191
    192 [[Image(Purdue.png)]]
     192[[Image(purdue-expt-setup.png)]]
    193193
    194194To see this experiment case study of !OnTimeMeasure in action, please see [http://ontime.oar.net/demo/framelength.htm demo video]. The experiment uses !OnTimeMeasure to measure all links delay across inter and intra federated sites periodically using Ping tool, and measures "!FrameLength" of http requests across all links using Tshark periodically. The measurement results are compared and studied with various other aspects of data from the experiment application. To accomplish these measurements with !OnTimeMeasure, the !RootBeacon is installed on an extra node in the experiment slice, and !NodeBeacons are installed on nodes f1, bl1, be1, fe2 and bl2 within the experiment slice.