EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI EG recent developments T. Ferrari/EGI.eu ADC Weekly Meeting 15/05/2012 1

EGI-InSPIRE RI Outline Progress report on several technical areas discussed in the operations TEG –WP1 – monitoring and metrics –WP2 – support tools SAGrid 2

EGI-InSPIRE RI WG1 Network monitoring –EGI/ DANTE MoU under discussion for Perfsonar-MDM deployment support –Updates from DANTE at the main –Which kind of collaboration with ATLAS? Monitoring of services –Relying on EMI support to this 3

EGI-InSPIRE RI WP1 – monitoring and metrics “It should be discussed if SAM should provide more or different granularity than the service endpoint. Some experiment for example finds important to test the granularity of the Storage Space Token (rather than the storage endpoint). At the same time, it should be discussed if the current limitation (endorsed by the MB) of testing only services published in GOCDB should be revisited” GOCDB support of Custom Service Types for VO or site-specific servicesCustom Service Types –CUSTOM.org.squid-cache.Squid –CUSTOM.ch.cern.frontier.FroNTier –CUSTOM_SERVICE –New type can be requested through GGUS/RT/ GGUS/RT/ GOCDB developments v4.4 (June/July) –Multiple Endpoints per Service conforming to GLUE 2.0 information model –GLUE2 rendering of GOCDB data (requires update of the XML output module)  useful for GOCDB/OIM harmonization of the interface 4

EGI-InSPIRE RI WP1 – monitoring and metrics Monitoring as a service. Monitoring systems should be treated as any other critical service. This includes a proper release cycle (including a pre-production instance for integration), a scalable deployment and proper operational procedures for upgrades/incidents/downtimes. The SAM project for example already follows those guidelines and should be considered as an example SAM releases are tested by Early Adopters in EGI –NGI SAM instances (together with other central operational services) will be monitored by a central SAM instance (waiting for SAM update 17) Monthly availability/reliability statistics Minimum availability: 99%  will be assessed 5

EGI-InSPIRE RI WP2 – support tools Full implementation of GGUS failover expected in QR (GGUS plans for 2012)GGUS plans for 2012 Accuracy of CPU benchmarking information –General issue concerning information from BDII –Waiting for EMI 2 release notes to see level of support of information validation Storage accounting –In progress: STAR and sensor development (EMI), accounting portal views (EGI-InSPIRE JRA1) The messaging infrastructure should be more reliable (SAM, Accounting in the future) –QR7: upgrade to ActiveMQ 5.5 allowing load distribution across the broker instances, reliability of message delivery (TTL = 3 days), automatic clearing of inactive connections 6

EGI-InSPIRE RI WP2 – support tools/ cont Provide an easy way to define new service types  now supported in GOCDB The Accounting Portal should have a better API and show more users data –XML datafeeds available on tree views in Accounting Portal release Electra 4.2 (10 May) –Also addressing RT requirement Provide a better integration of GOCDB and OIM through a uniform interface –Discussions in progress with OSG (EGI Community Forum) –GOCDB exposing information in GLUE 2.0 format The GOCDB/OIM information should be better kept up to date 7

EGI-InSPIRE RI WP2 – underlying services/cont Improve the security and scalability of the messaging services –Authenticated connections by end of 2012 (see milestones 2012)see milestones 2012 Improve the reliability and the availability of the messaging services –See previous comments on reliability –Availability: central EGI messaging infrastructure will be soon under central SAM monitoring 8

EGI-InSPIRE RI WP2 – underlying services/cont Improve the stability, accuracy, validity of the information services –Stability: several BDII improvements (site/top) recently released in EMI 1 tested in EGI staged rollout and distributed through UMD –Caching released in EMI 1 (default: 12 hours) –Top-BDII availability being reported from Jan 2012 –Series of workshop for publishing of ARC, globus and UNICORE information in BDII –GLUE 2.0 migration –Accuracy and validation: several requirements submitted to EMI during 2011, waiting for EMI 2 release 9

EGI-InSPIRE RI WP2 – underlying services/cont Provide a long term solution for a scalable and open source batch system –SLURM support in CREAM requested in 2011 –Create interest groups (e.g. GE, SLURM) to facilitate community support Provide adequate support for the batch systems currently in use in WLCG –2 nd level support effort being reallocated within EGI to cover batch systems (currently relying on best effort) 10

EGI-InSPIRE RI For discussion Provide a reliable way to publish VO-specific service downtime information –EGI-InSPIRE JRA1 discussions of feasibility –More information on the use case needed 11

EGI-InSPIRE RI SAGrid EGI/SAGrid MoU signed in Sep 2011MoU Integration started in Aug 2011 (GGUS 73185), on-hold for several months, but now almost completed –Operations Centre Certification procedure (PROC02)PROC02 12

EGI-InSPIRE RI References Overview of recent GOCDB developmentsOverview Tool deployment plans 2012deployment plans 2012 Operations plans 2012Operations plans 13