Summary of Past and Current work of the GGF Network Measurements Working Group

1. Summary of Past and Current work of the GGF Network Measurements Working Group Brian L. Tierney Lawrence Berkeley National Laboratory GGF

2. GGF Perf-WG / NM-WG Work • GMA: Grid Monitoring Architecture • What monitoring components are needed? • DAMED: Discovery and Monitoring Event Descriptions • What are the Top-N monitoring events we need to support NOW? • NMWG: Network Characteristics Hierarchy • What does “bandwidth” mean anyway? • NMWG: Network Request / Response Schemas • Need a self-describing “language” for requesting network monitoring data and interpreting the results • Overall Goal of all this: information portability GGF

3. GMA Monitoring Event Publication:Terminology and Architecture • (Performance) Event: • Typed collection of data with a specific structure • Producer Interface: • makes performance data (events) available • Consumer Interface: • receives performance data (events) • Directory Service: • supports information publication and discovery • must be distributed and/or replicated GGF

4. GMA Status: Done • GGF Approved Informational Drafts • GMA Architecture Document • http://www-didc.lbl.gov/GGF-PERF/GMA-WG/papers/GWD-GP-16-2.pdf • Final version, January, 2002 • GMA Use Case Document • http://www-didc.lbl.gov/GGF-PERF/GMA-WG/papers/GWD-GP-9-2.pdf • Final version January, 2002 • GMA only step 1; step 2: define standard event schemas and event dictionaries GGF

5. Discovery And Monitoring Event Description Working Group (DAMED) • Terminology: • Events names composed of: Target.Type • E.g.: network.link; delay.TCP • Sample Targets: • Host: IP • Process: IP, PID • Disk Partition: /home • Network Link: IP {port},IP {port} • Software: String • Scheduler: IP, String Sample Event Names GGF

6. DAMED Status: almost Done • Document: Top 10 Events • http://www-didc.lbl.gov/damed/documents/TopN_Events_final_draft.pdf • Finished: Feb. 2003 • Currently in 60 public comment period GGF

7. Network Measurements WG (NM-WG) • Network Measurements Working Group • Chairs: • Brian Tierney (LBNL) • Richard Hughes-Jones (Manchester) • Bruce Lowekamp (W&M) (till 2003); Eric Boyd (I2) (starting 2004) • Goal: • Portability of network measurements via Web/Grid Services • Steps: • Define hierarchy of types of measurements • Define schemas to request results (previous test and test on demand) and schemas to interpret results GGF

8. Terminology • Network Characteristics • Intrinsic properties of a portion of the network that are related to its performance and reliability • Network Entity • The part of the network described by the measurement • Link, path, host, etc. • Measurement Methodologies • Means and methods of measuring those characteristics • Observation • An instance of information obtained by applying a measurement methodology. GGF

9. Characteristics Overview GGF

10. “Standard” DAMED Names for Network Monitoring GGF

11. XML request message Client/ Requestor Receiving System Interim communication XML response message(s) Current NMWG Work: Request/Response Schema • Define schemas to request results (previous test and test on demand) and schemas to interpret results • Define use cases • Define capability discovery schema GGF

12. Sample Request <!--Example: command line: iperf -c -p 5001 -w 1048576 -t 5 -fb --> <subject xsi:type="NetworkPathType"> <source xsi:type="NodeType"> <address xsi:type="DNSAddressType"> <name>hostA</name> </address> </source> <destination xsi:type="NodeType"> <address xsi:type="DNSAddressType"> <name>hostB</name><port>5001</port> </address> </destination> </subject> <time/> <!-- Null time = “most recent” --> <characteristic>path.throughput.achievable</characteristic> <methodology> <parameters xsi:type="ToolParameterSetType"> <tool use="required"> <name>iperf</name></tool> </parameters> <parameters xsi:type="TCPParameterSetType"> <duration units="seconds" > 5 </duration> <tcpBufferSize units="bytes" >1048576</tcpBufferSize> </parameters> </methodology> </NetworkMeasurementRequest> GGF

13. Sample Response <methodology> <tool> <name>iperf</name> <major>1</major> <minor>7</minor> </tool> <parameterSet> <duration units="s"> 10 </duration> <packetType>TCP</packetType> </parameterSet> </methodology> <results> <timestamp> <iso8601>2004-01-14T12:10:08.123456Z</iso8601> </timeInterval> <result> <achievableThroughput units='Mb/s'> 7.0 </achievableThroughput> </results> GGF

14. NMWG-Status • Document: “A Hierarchy of Network Performance Characteristics for Grid Applications and Services” • http://www-didc.lbl.gov/NMWG/docs/draft-ggf-nmwg-hierarchy-02.pdf • Status: only about 2 weeks left in “60 day public comment period” • Request/Response Schemas: • Draft documents on gridforge • Almost done with 2 proof-of-concept implementations • Will finallize recommendations draft over the next 6 months GGF

15. Proposed Network Measurements Research Group BoF in Hawaii to discuss formation of a new research group to address such topics as: • What network characteristics (monitoring data) is most useful to Grid Applications • E.g.: taxonomy of types of Grid applications and types of monitoring data required by each • Are there "derived characteristics" (combinations of characteristics) that are even more useful (e.g.: “cost functions”) • When can passive monitoring be used, and when must active monitoring be used? GGF

16. For More Information • http://dsd.lbl/gov/NMWG/ • Mailing List: <nm-wg@gridforum.org> • Subscription Request:send email to <majordomo@gridforum.org> with the body "subscribe nm-wg" GGF