1 / 12

An XML Schema for Exchanging Grid Network Measurements

An XML Schema for Exchanging Grid Network Measurements. Dan Gunter Monday, 6 October 2003 GGF9: Chicago, IL. Who will use this? Why XML?. Common language for OGSI grid services to communicate network measurements to other OGSI grid services

cameron-mckay
Télécharger la présentation

An XML Schema for Exchanging Grid Network Measurements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An XML Schema for Exchanging Grid Network Measurements Dan Gunter Monday, 6 October 2003 GGF9: Chicago, IL

  2. Who will use this? Why XML? • Common language for OGSI grid services to communicate network measurements to other OGSI grid services • XML Schema the most supported mechanism in this space for interoperable data exchange • Eventually: Ontologies!

  3. Schema overview Name of characteristic being measured Characteristic Subject (src,dst,…) Network topology that the characteristic is measuring Methodology (tool(toolParams)) How the characteristic is measured Result-Set (result,summary)* Results of measurement

  4. Flexibility Assumptions • Assume that all characteristics are not known in advance • Characteristic identified by a string, not a “type” • Relation between characteristics and tools not specified – assume tools come and go, and relation may be a many-to-many • Assume new “result” types are common, relation to tool/characteristic not known in advance: • Any result can appear for any characteristic / tool combination

  5. Results • Allow multiple “raw” results to be combined with multiple “summary” results • Pre-defined summary types exist but they are extensible (base “SummaryData” type)

  6. DelayResult diagram A little out of date: can occur zero or more times This stuff is all in DoubleResult

  7. Topology • Most concepts in NM-WG document are represented (thanks to Bruce L.) • Multi-hop paths not yet implemented (but would be easy)

  8. Tools and Parameters • Tool is named and versioned • Inputs to the tool, called “tool parameters” are selected from groups • Only 1 group now: IPToolParameters • Reporting any parameter is optional

  9. Examples • iperf measurement from NTAF (slightly modified to show multiple results) • iperf_from_ntaf.xml • Ping measurement from NTAF • ping_from_ntaf.xml

  10. “Demo” • Use XPath expressions on real NTAF results to find: • Most recent achievable bandwidth measurement on any path • Most recent round-trip between two specific hosts • All round-trip measurements, raw number only, between a host pair since October 3rd • By the way, what is XPath? • Xpath is the glob of XML • Will be “built in” to OGSI services • Xquery is the SQL-like big brother, not implemented much yet

  11. Compare with CIM instance at InstanceDelay.xml • More compact; CIM-compatible(?) • Test-centric: characteristic name is buried in the “test settings” • Single topology (src/dst) • Results less flexible • Set of results for a characteristic pre-defined • No way to do time series • Summary elements not reusable • What is the “InstanceID”? • Hard to say more, since schema not available

More Related