Changes between Version 4 and Version 5 of OTM-CustomMetric


Ignore:
Timestamp:
11/12/11 10:47:32 (8 years ago)
Author:
Prasad Calyam
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OTM-CustomMetric

    v4 v5  
    2323== 2. Steps for Custom Metric Integration ==
    2424
    25 === 2.1 Specify custom metric information ===
     25=== Step-1: Specify custom metric information ===
    2626
    2727Let us consider an example of "!FrameLength" metric for illustration purposes below.
     
    4545}}}
    4646
    47 === 2.2 Compose a configuration file and add custom metric specifications ===
     47=== Step-2: Compose a configuration file and add custom metric specifications ===
    4848
    4949In a new configuration file !FrameLengthSpecs.yaml, add the following:
     
    6969}}}
    7070
    71 === 2.3 Compose a parser file to extract the custom metric "timeseries record" from output of measurement tool  ===
     71=== Step-3: Compose a parser file to extract the custom metric "timeseries record" from output of measurement tool  ===
    7272Please see !FrameLengthParser.pm example written in Perl.
    7373
    74 === 2.4: Add custom metric configuration file and parser file into !OnTimeMeasure framework ===
     74=== Step-4: Add custom metric configuration file and parser file into !OnTimeMeasure framework ===
    7575
    7676From Researcher Web-portal (!OnTimeBeacon):
     
    9494The custom metric !FrameLength is now integrated into !OnTimeMeasure!
    9595
    96 === 2.5 Add measurement tasks with the custom metric ===
     96=== Step-5: Add measurement tasks with the custom metric ===
    9797From Researcher Web-portal (!OnTimeBeacon):
    9898The custom metric will appear in the "Measurement Request Specification" page to add related measurement tasks.
     
    150150}}}
    151151
    152 === 2.6: Query measurement results of the integrated custom metric ===
     152=== Step-6: Query measurement results of the integrated custom metric ===
    153153
    154154From Researcher Web-portal (!OnTimeBeacon):
     
    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. 
    195195
    196 === 4.2 Case Study 2: Resource allocation in virtual desktop clouds ===
     196== 4.2 Case Study 2: Resource allocation in Virtual Desktop Clouds ==
    197197
    198198A GENI experiment being led by The Ohio State University aims to develop utility-directed resource allocation schemes within virtual desktop clouds (VDCs). The schemes allocate resources (i.e., CPU, memory, network bandwidth) such that the global utility (i.e., combined utility of all virtual desktops at a data center) is maximized under the constraint that each virtual desktop at least meets it minimum quality requirement specified in service level agreements. The allocation adaptation is based on feedback of network health from the client, and CPU/memory load on the server.