mardi 30 mars 2010 Lavoisier : a way to integrate heteregeneous monitoring systems. Cyril LOrphelin IN2P3/CNRS Computing Centre, Lyon, France

HEPiX Spring 2010 Workshop2 Outlines - Motivations - Main benefits of using Lavoisier - Concrete example : the Operations Dashboard - Future developments

HEPiX Spring 2010 Workshop330/03/103 EGEE / LCG information providers EGEE / LCG information providers CIC-DB - VO Information - VO Contacts - User Contacts SQL VO repository (static) GOC-DB - Site Information - Site Contacts - Downtimes SQL Site repository (static) GGUS - Create ticket - Update ticket - View ticket SOAP Ticketing System SAM - Test results - Status per nodes X-SQL Job Submission Framework BDII LDAP Dynamic information per nodes, per sites... LDAP Database for sites VOMS HTTP + Script - VOMS certificates. - VOMS users VO User repository (dynamic) - GIIS status per site - Storage Information - Jobs Information GSTAT HTTP GIIS browser HTTP Monitoring Framework Nagios Notifications about problem on services AMQ

HEPiX Spring 2010 Workshop4 Multiple heterogeneous sources and technologies : No common language No direct cross queries For a web application, it means lot of computations and treatment and a dependency to the technologies proposed The information might be : Not usable Not available Too long to be queried Motivations - Context

HEPiX Spring 2010 Workshop530/03/105 Our solution : Lavoisier An answer developped at CC-IN2P3: the Lavoisier service A good mechanism to build unified views from heterogeneous data sources "Nothing is lost, nothing is created, all is transformed" Antoine Laurent Lavoisier ( )

HEPiX Spring 2010 Workshop6 Accesses to data

HEPiX Spring 2010 Workshop7 Separation of roles

HEPiX Spring 2010 Workshop8 Other main features

HEPiX Spring 2010 Workshop9 Lavoisier Console

HEPiX Spring 2010 Workshop10 The Operations dashboard Heterogeneous data XMLHTML

HEPiX Spring 2010 Workshop11 The Synoptic view

HEPiX Spring 2010 Workshop12 Access to details

HEPiX Spring 2010 Workshop13 Future developments (Lavoisier 1.x) RDBMS adaptor (on-going development) user see the entire database as a huge XML document structure described by Hibernate or Doctrine ORM mapping file query with XPath / response as XML but of course this huge XML document is never built XPath query is translated to SQL query only the result set is converted to XML data XQuery and XPath as alternatives to XSLT available through SOAP and REST operations available as adapters (=> cacheable processing result)

HEPiX Spring 2010 Workshop14 Future developments (Lavoisier 2.0) Refactoring of core engine based on JMS to increase flexibility for notifications within a Lavoisier instance (through in-memory messages) between Lavoisier instances (though OpenWire protocol) improve extensibility with adapter interfaces for… Data protocol connectors Data format transformers Cache content managers4 hard-coded managers Cache refresh triggers8 hard-coded triggers Cache refresh schedulerNo scheduler (overload risk) Adapters do both (less reusable) Lavoisier 2.0 Lavoisier 1.x

HEPiX Spring 2010 Workshop15 Links Lavoisier : Dashboard : (you need to be registered in GOC DB )