1 / 6

CrossGrid WP3 Task 3.3 .2 Non-invasive Monitoring

CrossGrid WP3 Task 3.3 .2 Non-invasive Monitoring. Trinity College Dublin Brian Coghlan , Stuart Kenny , David O’Callaghan. Santiago FEB -200 3. Technical Annex: ‘ SQL-query-based tool support for non-invasive monitoring’. Achieve relational behaviour using EDG R-GMA.

kathrynp
Download Presentation

CrossGrid WP3 Task 3.3 .2 Non-invasive 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. CrossGrid WP3Task 3.3.2Non-invasiveMonitoring Trinity College Dublin Brian Coghlan, Stuart Kenny, David O’Callaghan SantiagoFEB-2003

  2. Technical Annex: ‘SQL-query-based tool support for non-invasive monitoring’ • Achieve relational behaviour using EDG R-GMA • R-GMA defines 5 fundamental Producers. Four are from EDG StreamProducer Grid Information System (R-GMA) Latest Producer System Being Monitored DataBase Producer Resilient Producer 3rd Party Information Acquisition Instrument Canonical Producer • The 5th is being developed by CrossGrid Task 3.3.2 Design

  3. Create table Conn ID Create table control Conn ID status query query resultset resultset Although the User Code can essentially be anything, certain components will almost always be present: seek To Registry Sensor Query Engine data Authentication Search Engine Authorisation SANTA-G Network Tracer Demonstrator System Being Monitored DBProducer Sensor CP API CP Servlet UserCode 3rd Party Network Trace Instrument (TCPdump) Query Engine QE API Query Service SE API There are 2 major activities: Trace Files Initialize/Register/Acquire Search Engine Query/Response

  4. Task 3.3.2 Status • CP/SANTA-G: installed in TCD & LIP, and works as per deliverable done sources in EDG and X# CVS, RPMs in X# GridPortal done • Constraints: can only use off-line data from TCPdump  logfiles restricted schema & restricted SQL parsing no authentication or authorization sensor & query engine are separate modules • Dependencies: R-GMA, Tomcat, … No dependencies on other CrossGrid tasks

  5. Integration with other WPs/Tasks: M12-M24 R-GMA Task 3.3.2 SANTA-G Task 3.3.4 Postprocessing Task 3.3.3 JIRO Task 3.3.2 Plans Enhancement: Extend schema & SQL parsing support M18 Add on-line data acquisition M18 Integrate sensor and query engines M18 Add authentication/authorization (R-GMA/LCAS) M36 OGSA-fication be ready Extend viewer opportunistically

  6. Internet TCD Dublin  proxy-arp Firewall Net Tracer   100Mb switch 100Mb switch    CA server  disbabled  cagnode32 (CE00) HTTP server RA server   NIS master & slave Irish RB/LB server cagnode39 (CE07)  cagnode00 Irish GIIS/R-GMA   LCFG server    cagnode44 (UI) cagnode15 not connected cagnode47 (SE00) cagnode45 Gatekeeper CE Local GIIS/R-GMA  RAID servers • Register • Query • Response SANTA-G Demonstration at Santiago CESGA Santiago We did a TCPdump on MPI ports at LIP while HEP application was executing We copied the trace file off-line to cagnode00 at TCD NOW:Sensor/Q.Engine@cagnode00:R-GMA@cagnode45:Viewer@CESGA

More Related