Release and deployment process Working Group Łukasz Skitał Central European ROC

Introduction Objective: Timely deployment of new release in the regions Planning Seamless deployment at sites CERN, 19-20/06/2006

Deployment process planning Deployment PLAN SA1 (local cert.) SA1 (1st line support) (certification) SA3 Bugs submited next cycle deployment deployment (applic.) NA4 planning Experience “log” (to share among ROCs) RC admins RC admins Deployment PLAN (to share among ROCs) (release + docs) SA3 CERN, 19-20/06/2006

Topics to be discussed with SA3 Requirements from regional certification of middleware releases TSA1.2.2 and TSA1.1.2 Pre-production service site How can we divide work between them? PPS for earlier phases of releases, beta-versions Without central coordination: Regional certification for Release Candidate installation, stress testing, scalability testing? Contact in SA3 (was Laurence Field) Certification report form – what’s required for SA3 Scope of testing (services, functionality – to be discussed) Documentation/procedures Bug submission (how to do that? Savannah or GGUS) Bug mgmt (priotities, status) Release update plans (timetable, bugs be fixed) Detailed description of newly-introduced services (why are they here, who will need to install it) CERN, 19-20/06/2006

Topics to be discussed with VOs Topics to be discussed with VOs (NA4) Requirements for deployment planning Scheduled VO activites which should not be interrupted by the upgrade to new mw release Functionality at CIC portal for announcing data challenges: https://cic.in2p3.fr/index.php?id=vo&subid=vo_activity&js_status=2 (only biomed VO used that so far) Expected from a site supporting the VO: Software e.g. MPICH Services e.g FTS Middleware components, e.g VO BOX CERN, 19-20/06/2006