WLCG Technical Evolution Group: Operations and Tools Maria Girone & Jeff Templon GDB 12 th October 2011, CERN

Large spectrum of topics in charge – Monitoring, (SAM, Nagios, etc.), metrics, and analysis of these data – Support tools (APEL, GGUS, etc.) – Underlying services (ActiveMQ, BDII, etc.) – Application software management (e.g. cernvmfs) – Operational requirements on middleware – Configuration management – Deployment management – Middleware distribution management Areas of Work GDB, October 20112

The work should: Document a strategy for evolution of the technical implementation of the WLCG distributed computing infrastructure. This strategy should provide a clear statement of needs for WLCG, which can also be used to provide input to any external middleware and infrastructure projects. The work should, in each technical area, take into account the current understanding of: Experiment and site needs in the light of experience with real data, operational needs (effort, functionality, security, etc.), and constraints; Lessons learned over several years in terms of deployability of software; Evolution of technology over the last several years; Partnership and capabilities of the various middleware providers. It should also consider issues of: Long term support and sustainability of the solutions; Achieving commonalities between experiments where possible; Achieving commonalities across all WLCG supporting infrastructures (EGI-related, OSG, NDGF, etc). Deliverables Assessment of the current situation with middleware, operations, and support structure. Strategy document setting out a plan and needs for the next 2-5 years. GDB, October Mandate

The work should: Document a strategy for evolution of the technical implementation of the WLCG distributed computing infrastructure. This strategy should provide a clear statement of needs for WLCG, which can also be used to provide input to any external middleware and infrastructure projects. The work should, in each technical area, take into account the current understanding of: Experiment and site needs in the light of experience with real data, operational needs (effort, functionality, security, etc.), and constraints; Lessons learned over several years in terms of deployability of software; Evolution of technology over the last several years; Partnership and capabilities of the various middleware providers. It should also consider issues of: Long term support and sustainability of the solutions; Achieving commonalities between experiments where possible; Achieving commonalities across all WLCG supporting infrastructures (EGI-related, OSG, NDGF, etc). Deliverables Assessment of the current situation with middleware, operations, and support structure. Strategy document setting out a plan and needs for the next 2-5 years. GDB, October Where we will start

When – Kick-off planned Monday 17 th October, 15:30 CET! – Fortnightly phone meeting – Likely need F2F meetings E.g. for Deliverable Writing – Workshops for second phase “the future” Plan to use subgroups (with “grand unification” at F2F) GDB, October Organization

24 suggested names given to us Will survey these people to determine if we have the right mix experiments / sites Probably will need a few more site people (esp. T2 and higher!) – send suggestions to us. GDB, October Membership