1 / 14

Administrative domain interface

This project focuses on the design and implementation of Administrative Domain Interfaces (ADI) for End-to-End (E2E) pipelining in monitoring systems. Our current work integrates Web Services (WS) support into the GridMon system, leveraging SOAP/RPC over HTTP and utilizing WSDL for interface definitions. Key features include client-server interactions for data requests and responses, with a focus on measurement scripts and error management. Future steps involve refining NMWG request and response documentation, facilitating service registration, and enhancing the interoperability of the system.

iola
Télécharger la présentation

Administrative domain interface

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. Administrative domain interface Paul Mealor, Yee-Ting Li, Mark Leese

  2. Menu • What we are doing • Components and interfaces • The messages

  3. What are we doing • We are working on ADI and database interfaces design for E2E piPES • We would like to use that work for UK monitoring • Currently adding this WS support to the GridMon system • We would like to say that we helped make an interoperable system

  4. Technologies • SOAP/RPC over HTTP • Interface definitions in WSDL • Use schemas defined by GGF NMWG • Implementation • Using Apache Axis with Tomcat • i.e. Java-based

  5. Populated NMWG schema reference to data gimme data request running of test authorised? capable? Initiator ADI Request i/f anything suitable? Client interface Database Response i/f Acceptor ADI Internal i/f authorised? capable? do test finished! store data monitoring system specifics monitoring system specifics Operation Client

  6. With Gridmon Client Client interface Flat files Response i/f Acceptor ADI Initiator ADI Request i/f Measurement scripts Tool server e.g. Iperf

  7. Operation with piPES Client Client interface Database Response i/f Acceptor ADI Initiator ADI Request i/f Internal i/f PMC PMC PMP PMP

  8. The messages • MeasurementRequest • MeasurementReference • Faults • PermissionDenied • HostUnavailable • ToolUnavailable • CharacteristicUnavailable • TimeUnavailable

  9. MeasurementRequest <MeasurementRequest> <characteristic name=“path.delay.roundTrip”/> <tool name=“ping” rank=“1”/> <source host=“hosta.foo.ac.uk”/> <sink host=“hostb.bar.edu”/> <credential xsi:type=“X509Cert”>FTtvgddE… </MeasurementRequest>

  10. MeasurementReference <MeasurementReference> <reference xsi:type=“GridmonWSReference”> <service> http://dbhost.foo.ac.uk:8080/axis/services/gridmon </service> <characteristic> path.delay.roundTrip </characteristic> <target>hostb.bar.edu</target> <time>106456746345</time> </reference> </MeasurementReference>

  11. PermissionDeniedException <PermissionDeniedException> <message>You do not have the appropriate credentials to access this service</message> </PermissionDeniedException>

  12. Next steps • NMWG request document? • NWMG response doc. interface on DB • OGSA-ify? • Registration of ADIs for client to search • Registration of PMCs for ADI to search • Registration of ADIs for other ADIs to search • Make better use of OGSA instance control, lifetime management, service data?

  13. End http://www.hep.ucl.ac.uk/~pdm/e2epipes/ http://gridmon.dl.ac.uk/

More Related