1 / 8

Deployment Introduction

On September 14, 2004, David Kelsey introduced the aims and agenda for the GridPP2 Deployment at an open meeting in Liverpool. The session served as a formal kickoff for GridPP's deployment activities, involving various stakeholders, including the DTEAM and Technical Board (DB). Key topics included fabric management, metrics, deployment plans, and the establishment of the GridPP Deployment Board to oversee execution and discuss technical issues. The board will facilitate coordination between Tier1 and Tier2, and ensure integration of tech developments.

cody-donaldson
Télécharger la présentation

Deployment 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 Introduction David Kelsey GridPP11, Liverpool 14 Sep 2004 d.p.kelsey@rl.ac.uk

  2. Aims and Agenda • Aims • Open meeting for GridPP deployment • DTEAM, DB and others • Kick-start GridPP2 Deployment (Board) • First formal meeting (DB) on 29th October (RAL) • Launch the DTEAM • Agenda today (30 minute slots) • Introduction (DPK) and Communication (JC) • Fabric Management (ST) • Metrics (JC) • Deployment plans (JC) • Lots of time for discussion GridPP Deployment Board

  3. Deployment Board • Replaces GridPP1 Technical Board • Mandate • Determine and oversee execution of tech plan • Report to 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 Deployment Board

  4. DB members • Production Manager • Tier1/A Manager • 4 T2 Technical Coordinators • HEP SYSMAN chair • CERN T0/Deployment • Applications Area Coordinator • Middleware Area Coordinator • Technical experts (invited by DB chair) • UK NGS • EGEE/Ireland • DB chair ~18 people GridPP Deployment Board

  5. DB meetings • Quarterly • Scheduled to happen after the UB meeting • Review progress during last quarter • q reports, metrics, milestones, deliverables • Consider and prioritise future plans • Short term and longer term • Discuss technical issues (see mandate) • Once per year (Feb meeting) • More detailed review of complete year GridPP Deployment Board

  6. Deployment Team • GridPP DTEAM • Builds on the regular TB-support meetings • JC (Production Manager) – leads the team • More details from JC GridPP Deployment Board

  7. Notes • The GridPP DTEAM - where the action is! • Make and execute plans • Discuss and fix technical issues • Meet regularly (how often?) • DB will take more of an overview • But is still a “technical” body • Can be consulted when DTEAM is stuck! • Two new mail lists • GridPP-DB@jiscmail • GridPP-DTEAM@jiscmail GridPP Deployment Board

  8. DB relations LCG/EGEE/CERNT0 PMB UK NGS DB UB GridPP DTEAM M/S/N APPS T1AB T2B GridPP Deployment Board

More Related