1 / 10

Deployment Board Introduction

This document outlines the inaugural meeting of the GridPP Deployment Board, held on October 29, 2004. Key objectives included defining the board's role, individual responsibilities, and reviewing past achievements, deployment challenges, and future plans. The board aims to oversee technical execution and ensure integration of developments across various collaborations including CERN and UK NGS. The report also addresses communication strategies and relationships with related projects. Regular quarterly meetings are established to monitor progress and prioritize team activities.

alika-porter
Télécharger la présentation

Deployment Board Introduction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Deployment BoardIntroduction David Kelsey 29 Oct 2004 d.p.kelsey@rl.ac.uk

  2. Agenda • Morning • Objectives • Introduction • Review of past (the most recent quarter) • Current deployment issues • Afternoon • Reports from related projects • Deployment Team plans • Future plans and priorities • Plans for next meeting (annual review) • AOB GridPP DB Intro

  3. Today’s Objectives • First meeting of the new Deployment Board • Understand and agree its role • Identify individual responsibilities • Agreed inputs and outputs of the DB • Clear record of GridPP deployment plans and issues • Understand how middleware and applications development will impact deployment activities • Understand how CERN, UK NGS, Grid Ireland, EGEE and LCG developments will impact deployment activities • Agreed list of priorities for the deployment team GridPP DB Intro

  4. Deployment Board • Replaces GridPP1 Technical Board • Prototype to Production • Mandate (primarily a technical body) • Determine and oversee execution of technical plan • Report to GridPP PMB • Ensure GridPP-wide issues discussed/solved • Provide forum for tech info exchange • Oversee deployment and use of GridPP h/w • Tier1 – Tier2 coordination/liaison • Ensure integration of external tech developments GridPP DB Intro

  5. DB members • Production Manager Jeremy Coles (RAL) • (acts as Deputy Chair) • Tier1/A Manager Andrew Sansum (RAL) • 4 Tier 2 Technical Coordinators • London Owen Maroney (Imperial) • North Grid Alessandra Forti (Manchester) • Scot Grid Fraser Speirs (Glasgow) • South Grid Rhys Newman (Oxford) • UK HEP SYSMAN chair Pete Gronbech (Oxford) • CERN T0/Deployment David Smith (CERN) • Applications Area Coordinator Roger Jones (Lancaster) • Middleware Area Coordinator Robin Middleton (RAL) GridPP DB Intro

  6. DB Members (2) • Technical experts (invited by DB chair) • Stephen Burke (RAL) LHC deployment • Dave Colling (Imperial) Workload Management • Steve Fisher (RAL) Info&Monitoring • Andrew McNab (Manchester) Security • Robin Tasker (DL) Networking • Steve Traylen (RAL) Deployment • UK NGSStephen Pickles (Manchester) • EGEE/Grid IrelandJohn Walsh (Dublin) • DB chairDPK • A total of some 20 people GridPP DB Intro

  7. DB tasks • Meet Quarterly • Review progress during last quarter • q reports, logbooks, metrics, milestones, deliverables, current status • Consider and prioritise future plans • Short term and longer term • Discuss technical issues (and resolve?) • Once per year (Feb meeting – 2 days?) • More detailed review of complete year GridPP DB Intro

  8. Deployment Team • The GridPP DTEAM • Builds on the regular “TB-support” meetings • JC (Production Manager) – leads the team • Where the action is! • Make and execute plans • Discuss and fix technical issues • Meet regularly • DB will take a more formal overview • But is still a “technical” body • Can be consulted when DTEAM is stuck! GridPP DB Intro

  9. Communication • Two new mail lists • GridPP-DB@jiscmail • GridPP-DTEAM@jiscmail • Mail list attributes • Web pages • http://www.gridpp.ac.uk/db/ • Public unless we identify a need for a private area • We need to discuss how to develop the deployment area web (infrastructure) GridPP DB Intro

  10. DB relations LCG/EGEE/CERNT0 PMB UK NGS & Grid Ireland DB UB GridPP DTEAM M/S/N APPS T1AB T2B GridPP DB Intro

More Related