Release and deployment process Working Group

1
Release and deployment processWorking Group

• Lukasz Skital
• Central European ROC

2
Introduction

• Objective
• Timely deployment of new release in the regions
• Planning
• Seamless deployment at sites

3
Deployment process
SA1 (local cert.)
SA1 (1st line support)
(certification) SA3
Bugs submited
next cycle
deployment
deployment
planning
(applic.) NA4
Experience log (to share among ROCs)
RC admins
RC admins
Deployment PLAN (to share among ROCs)
(release docs) SA3
4
Topics to be discussed with SA3

• 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 whats 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)

5
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?idvos
  ubidvo_activityjs_status2 (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