EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI TS8.10 A new approach to Computing Availability/Reliability reports for EGI K. Koumantaros GRNET 3/16/2016 1

EGI-InSPIRE RI Current Status A/R reports are delivered monthly Computations are performed on a centralized infrastructure Current implementation is more or less a closed solution EGI Operations cannot interact via a direct interface Re-computations etc are handled via GGUS (SLM unit)

EGI-InSPIRE RI Proposal New A/R reporting service Open source solution Include extensions for VO-wide metrics (in addition to service-wise, site-wise and NGI- wise) Direct interface for SLM Units and EGI Operations (via API) Computations performed under profiles Deliver/Query results via front-end module

EGI-InSPIRE RI Overview

EGI-InSPIRE RI Workplan Phase 1: Requirements assessment Requirements gathering is going to be performed by EGI OMB Create a Working Group to define requirements for this mini project. Assessment by TSA8.10 and OMB of feasibility, priority and scope

EGI-InSPIRE RI Workplan Phase 2: Implementation Results collection from PROD MSG brokers Implementation of core mechanism for A/R VO-wise, Service-wise, Site-wise and NGI-wise Implementation of A/R computation profiles repository Implementation of A/R API Interoperation of Operations Portal A/R Frontend module using A/R API

EGI-InSPIRE RI Workplan Phase 3: Pilot Validation of results Assessment of new A/R service approach Documentation

EGI-InSPIRE RI Workplan Phase 4: Service Deployment Service Rollout into production Refinements to the service In collaboration with EGI OMB Release Packaging and documentation

EGI-InSPIRE RI Consortium GRNET (Project leader) CNRS/IN2P3 SRCE

EGI-InSPIRE RI Proposal for and Working group Questions to be answered Profiles The current implementation is kind of monolithic in regards to supporting multiple/different profiles. This has been one of the major pains that EGI has with the current service. It would be very useful if we could a set of use cases for new profiles that will need to be supported by the A/R User Interface The current implementation does not provide any interaction for external users (e.g. EGI Operations Team). Is there a requirement for a User Interface and if yes what is the envisaged functionality. Regionalization (?) The current service is implemented as a central service. This is the path that we will also follow. Still, we could have the ability to provide the service packaged in a way that an NGI or any other external entity could take it and install it and have their own A/R calculations. Of course any other installations will NOT affect the central A/R service which will independently calculate the results. How high would this be in the priorities of EGI ?