WLCG Operations Coordination Team Goals WLCG will evolve

  • Slides: 5
Download presentation
WLCG Operations Coordination Team Goals • WLCG will evolve rapid over the next three

WLCG Operations Coordination Team Goals • WLCG will evolve rapid over the next three years, by the end of LS 1 we should be able to operate in a “Computing as a service model” but only if we are willing to evolve – Operations team will coordinate the stable operations and help commission and coordinate the technical transition within the guidance and direction of the WLCG-MB, the service and capacity providers, and the experimental community – Seeks to address needs identified in the WLCG Service Coordination recommendations (R 1) + Commissioning (R 2) of OPS TEG Maria Girone, WLCG MB, 19 June 2012 1

WLCG Operations Coordination Team – Roles & Methods • Interacts with other WGs, sites

WLCG Operations Coordination Team – Roles & Methods • Interacts with other WGs, sites & experiments – Via permanent representation of selected team members • Relates to existing structures such as daily OPS • Re-task WLCG T 1 SCM as principle communication / coordination meeting • Key body: core members + targeted experts when required – Need representation / knowledge of sites, experiments and services • Validates and commissions new services and new versions of existing ones • Complemented by shorter-term WGs to address specific deployment / decommissioning issues (-WMS, FTS 3, glexec, …) – Coordinates work-plan among sites – WGs may be external in some cases, e. g. data federation, networking • Supplement with smaller “expert” meetings to prepare agenda, recommendations and technical follow-up • Schedule driven by key events, e. g. LS 1 / “ 2015” Maria Girone, WLCG MB, 19 June 2012 2

Backup Slides

Backup Slides

Computing as a Service • Would like to arrive at a point where –

Computing as a Service • Would like to arrive at a point where – A small number of well-defined common services would be needed per site; – Installing, configuring and upgrading these would be “trivial” – All services would comply to standards, e. g. for error messages, monitoring; – Services would be resilient to glitches and highly available; – In case of load (or unexpected “user behavior”) they would react gracefully; – In case of problems, diagnosis and remedy should be straightforward and rapid. • A point where sites provide a defined service and experiments use it – Increased expectations on the stability and quality of the service, but lower expectations on the need for customization and interaction Maria Girone, WLCG MB, 19 June 2012 4

Long-Term Recommendations: Operations • R 1: WLCG Service Coordination: improve the computing service(s) provided

Long-Term Recommendations: Operations • R 1: WLCG Service Coordination: improve the computing service(s) provided by the sites – Establish a coordination team with contributions from experiments, sites, and projects. Persistent effort. • Monitors and directs service commissioning effort – Address specific Tier-2 communication needs • Dedicated service coordination meetings – Evolve to “Computing as a Service at Tier-2 s” • less experiment-specific services and interactions • organize with EGI, NDGF and OSG common site administrator training • R 2: WLCG Service Commissioning: establish a core team of experts (from sites and experiments) to validate, commission and troubleshoot services Maria Girone, WLCG MB, 19 June 2012 5