1 / 11

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. Four are being developed within EDG. The 5 th is being developed within CrossGrid. StreamProducer. Grid Information System (R-GMA).

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

  3. CreateTable, Port, Protocol, Security, SQL Support, Multiple Query Support CP API Conn ID, Security Query from Consumer Servlet Query User Code ResultSet ResultSet to Consumer Servlet To Registry Canonical Producer CP Servlet Port Information may be in 3rd Party Instrument

  4. Sensor Authentication Authorisation Sensor Authentication Query Parser Authorisation Query Parser Search Engine Search Engine CP User Code Structure Although the User Code can essentially be anything, certain components will almost always be present: CP API User Code

  5. Create table Conn ID Create table control Conn ID status query query resultset resultset seek To Registry data SANTA-G Network Tracer Demonstrator System Being Monitored DBProducer Sensor CP API CP Servlet 3rd Party Network Trace Instrument (TCPdump) Query Engine QE API Query Service SE API Trace Files Search Engine

  6. Task 3.3.2 Status • CP/SANTA-G: installed in TCD & LIP done it works done sources are in EDG and X# CVS done RPMs are in X# GridPortal done functionality is as per deliverable done • Current Status: only can use off-line data from TCPdump  logfiles restricted schema & restricted SQL parsing no authentication or authorization sensor & query engine are separate modules

  7. Task 3.3.2 SANTA-G Task 3.3.4 Postprocessing Task 3.3.3 JIRO Task 3.3.2 Status • Dependencies: • R-GMA, Tomcat, … • Integration with other WPs/Tasks: • Task 3.3.2 + Task 3.3.3  Task 3.3.4 • To be done M12-M24 R-GMA

  8. Task 3.3.2 Status Plans: Complete the schema M18 Add more SQL parsing support M18 Add on-line data acquisition M18 Integrate sensor and query engines M18 Add authentication (with R-GMA) M36 Add authorization (LCAS?) M36 OGSA-fication be ready Extend viewer opportunistically

  9. 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 • ResultSet SANTA-G Demonstration CESGA Santiago

  10. SANTA-G Query View

  11. SANTA-G Packet View

More Related