Changes between Version 5 and Version 6 of OnTimeMeasureTutorial


Ignore:
Timestamp:
02/10/12 14:50:09 (7 years ago)
Author:
yxu@osc.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OnTimeMeasureTutorial

    v5 v6  
    318318You may need to wait a while for measurement data to start appearing in the Root Beacon database for query. The wait time depends on how you configure the measurement schedules in the measurement.yaml file.
    319319
    320 You can access Root Beacon through port 17280 in your web-browser (i.e., http://pc355.emulab.net:17280/) to check all the measurement data generated already. 
     320You can access Root Beacon through port 17280 in your web-browser (i.e., http://pc355.emulab.net:17280/) to check all the measurement data generated already in measurement dashboard.
     321
     322For video of navigate measurement dashboard, please see - http://ontime.oar.net/demo/dashboard.htm
     323
    321324
    322325To query using !OnTimeControl command-line tool, enter the following command (you may need to change the start-and-end dates in the query option).
     
    363366
    364367=== 4.3 Control ===
    365 
    366368Next, you will be directed to the "Service Control" page. If you have modified measurement tasks in previous page, you need to click "Stop" button to stop measurement collection in your slice. Next, click "Start" button to restart measurement collection in your slice.
    367369 
     
    386388For overview and details of the custom metric integration feature of OnTimeMeasure, please see - http://groups.geni.net/geni/wiki/OTM-CustomMetric
    387389
     390For videos of integrate custom metric of experiment , please see - http://ontime.oar.net/demo
     391
     392
    388393=== 5.1 Compose custom file for custom metric specifications and a parser file for the custom metric ===
    389 
    390394For demo, you can download a sample from http://ontime.oar.net/INSTALL/metric/CPU.tgz by typing the following command
    391395{{{
     
    448452NOTE: Mycpu is the metric name configured in CPUSpecs.yaml
    449453
    450 5.4 Manage Measurement Tasks with Custom Metric Measurement and Restart the Measurement
     454=== 5.4 Manage Measurement Tasks with Custom Metric Measurement and Restart the Measurement ===
    451455
    452456Run command "task_manage.py" to manage the measurement tasks with custom metric (i.e., requests), which are configured in the measurement.yaml file.