EGEE-II INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks Deliverable DSA1.4 Jules Wolfrat ARM-9 – Karlsruhe,

Enabling Grids for E-sciencE EGEE-II INFSO-RI ARM-9 – Karlruhe, Deliverable DSA1.4 Title: Assessment of Production Service Status Follow up of EGEE-I deliverable DSA1.8: Assessment of Operational Service Status – Description of operational services: COD, GGUS, ESC …. From the TA (TSA1.1) As a basis for planning and monitoring improvements to the reliability and stability of the service, several deliverables (DSA1.4, DSA1.6) are proposed to assess the status of the service. These will use a set of metrics to be defined in MSA1.1 and take as a baseline the final service assessment from EGEE (DSA1.8). The metrics defined in MSA1.1will also be reported on in the quarterly reports

Enabling Grids for E-sciencE EGEE-II INFSO-RI ARM-9 – Karlruhe, SA1 services Services (objectives) defined in TA: a)The operation of core infrastructure services b)Grid monitoring and control c)Middleware deployment and introducing new resources d)Resource and user support: e)Grid management f)International collaboration g)Capture and provide requirements h)Long term sustainability

Enabling Grids for E-sciencE EGEE-II INFSO-RI ARM-9 – Karlruhe, Metrics defined in MSA1.1 (1) 2.1. Size metrics – Number of sites and CPUs in production – Total available computing power – Computing power available per VO – Total storage available – Storage available per VO – Number of active VOs – Number of active users – Number of countries connected to EGEE infrastructure 2.2. Operations metrics – Response time – Tickets created – Tickets modified – Scheduled downtime – Critical tests

Enabling Grids for E-sciencE EGEE-II INFSO-RI ARM-9 – Karlruhe, Metrics defined in MSA1.1 (2) 2.3. Usage metrics10 – Number of jobs10 – Job efficiency11 – Job failure rate11 – Data transfer11 – Data transfer failure rate11 – CPU usage12 – Storage usage User Support metrics12 – Total number of user support tickets12 – Resolved tickets12 – Total number of user support tickets broken down by category 13 – Resolved tickets13 – Ticket response time13 – Average number of hops to solve tickets13 – Ticket escalation13 – Wrong ticket assignment14

Enabling Grids for E-sciencE EGEE-II INFSO-RI ARM-9 – Karlruhe, Metrics defined in MSA1.1 (3) 2.5. Service metrics14 – Resource broker match time14 – Resource broker round trip time14 – Resource broker passive metric14 – LFC availability15 – SRM availability15 – VOMS active availability15 – VOMS passive availability15 – Information system availability16 – FTS availability16 – CE availability16 – R-GMA availability16

Enabling Grids for E-sciencE EGEE-II INFSO-RI ARM-9 – Karlruhe, Services and metrics (1) SA1 BASIC PRODUCTION SERVICES –3.1. Introduction –3.2. Overview of production Infrastructure  Size metrics – from BDII (Gstat), GOC DB –3.3. Core infrastructure services  Operations metrics - SAM tests  Service metrics – Gridview, SAM –3.4. Grid monitoring and control  Operations metrics – APEL interface, Gridview, BDII, SAM –3.5. Middleware deployment and introducing new resources  Metrics ?  Relation with SA3  PPS service –3.6. Resource and user support  User support metrics – GGUS

Enabling Grids for E-sciencE EGEE-II INFSO-RI ARM-9 – Karlruhe, Services and metrics (2) SA1 BASIC PRODUCTION SERVICES –3.7. Grid management To co-ordinate the implementation of the above points (3.3 – 3.6) by the Regional Operations Centres (ROC), as well as to manage the relations with resource providers through negotiation of service-level agreements (SLAs), and relations with the wider Grid community through participating standards bodies.  No metrics. SLA status?  OAG activity ? –Tier1 (SC4) assessment? – gridview

Enabling Grids for E-sciencE EGEE-II INFSO-RI ARM-9 – Karlruhe, Services and metrics (3) SA1 SUPPORTING SERVICES –4.1. International collaboration  number of VOs –4.2. Capture and provide requirements –4.3. Long term sustainability –No metrics defined. Description of activities If metrics defined, not always available –For instance service metrics  Availability of LFC, VOMS, SRM, FTS, CE ….  SAM information  GGUS information in text (csv) format? Final objective should be to be able to produce reports on demand – APEL interface is a good example –For the current deliverable not feasible