1 / 10

UK Network Monitoring

UK Network Monitoring. GGF9: 5-8 th October 2003. Contents. GridMon: UK e-Science toolkit Plug ‘n’ Play: multi-domain monitoring Questions. “…design and deploy an infrastructure for network performance monitoring within the UK e-Science community.”

bree-brewer
Download Presentation

UK Network Monitoring

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. UK Network Monitoring GGF9: 5-8th October 2003

  2. Contents • GridMon: UK e-Science toolkit • Plug ‘n’ Play: multi-domain monitoring • Questions

  3. “…design and deploy an infrastructure for network performance monitoring within the UK e-Science community.” European Data Grid derivative, focusing on: Publication to humans and Grid middleware End-to-end performance (what users see)

  4. SOAP Example consumer • metric value/msg • secs since epoch Tomcat index.jsp results.jsp Java Bean SOAP Axis Web Service • secs since epoch • metric • site (hostname) Flat files GridMon: web service

  5. GridMon: the TAKE Crying out for an agreed schema to help answer our questions… • Need to retire the flat file structure. Something relational would allow more complex searches (e.g. NMWGs own examples) to be performed (probably quicker). Conversion from flat file to DB raises some questions. • We’re creating a DB from scratch, so we don't have exisiting format. Do we use this as an opportunity to define a structure to fit in with the NMWG profiles and schema? If so, is there an optimum design? • Do we use a relational database at all? Would we be better using an XML database? • Being able to publish data in an agreed format is cool, but don’t we also need a agreed way of advertising what data we have and what tests we can run? If so, how? TIES IN WITH… • We’re heading towards a unified method of publishing data. Do we also need a unifed way of asking for it? • Do we need to say “I want loss.oneWay” OR can we get away with asking what’s available and making a decision based on the answer? • How far will OGSA/OGSI go to solving this problem for us?

  6. GridMon: the GIVE GridMon is an existing infrastructure with historic data. ANSWER those questions! Could be used as a testbed for developing schema based web/Grid services. Test the Schema Could test suitability & identify any missing components, e.g. try implementing NMWG example queries.

  7. ADI Administrative Domain Interface architecture e.g. piPEs tool e.g. iperf P‘n’P: multi-domain monitoring • “Plug ‘n’ Play” collaboration: UCL and DL…. • BIG thanks to Internet2’s piPEs, and Dante • ADI = major component • Provide generic abstraction for users (whether human or machine): additional layer, or wrapper

  8. Populated XML schema reference to data gimme data request running of test authorised? capable? anything suitable? Web service Client interface GridMon Database Database Response i/f Acceptor ADI Request i/f Initiator ADI Internal i/f Internal i/f authorised? capable? do test do test finished! store data monitoring system specifics monitoring system specifics P‘n’P: to be implemented P‘n’P: multi-domain monitoring Client

  9. Conclusion • GridMon & P‘n’P ready to test schema and answer some questions

  10. Questions m.j.leese@dl.ac.ukhttp://gridmon.dl.ac.uk/~mjl ? ? ? ? ?

More Related