Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Staged Rollout"

From EGIWiki
Jump to navigation Jump to search
Line 48: Line 48:
== Collaboration between EGI and WLCG  ==
== Collaboration between EGI and WLCG  ==


EGI received an expression of interest from WLCG to integrate the WLCG Middleware Readiness  working group. The main goal of this group it's to improve both the quality of the middle-ware products that are available to the WLCG sites. This could be achieved by finding ways to improve the communication between both communities at the level of Middleware deployment with clear beneficts to both communities.
EGI received an expression of interest from WLCG to integrate the WLCG Middleware Readiness  working group. The main goal of this group it's not only to improve the quality of the middle-ware products available to the WLCG sites but also increasing the speed at which new products or releases are available to then while avoiding the duplication of effort. This could be achieved by sharing experiences and improving the communication channels of both communities.


   
   
deployment. The beneficts of this coordination will be a faster way to  provide to sites
quality software while avoiding the duplication of effort.
collaborate in the test of new versions of EGI deployed middleware. The aim is to have early adopter sites that are in WLCG, to include some of the services under test with ATLAS and CMS workflows.
EGI have their Staged Roll-out process that middleware products and updates have to pass before making it into the Unified Middleware Distribution (UMD) that sites can pick products from. This process certainly helps improving the quality of the products that are available from the UMD, but does not ensure they will work fine for the LHC experiments served by a particular site. Furthermore, many sites take middleware from other repositories, in particular to get important updates faster.
The work, discussions, meetings, technical information will be handled in this wiki page: [[https://twiki.cern.ch/twiki/bin/view/LCG/MiddlewareReadiness WLCG Middleware Readiness]]
The work, discussions, meetings, technical information will be handled in this wiki page: [[https://twiki.cern.ch/twiki/bin/view/LCG/MiddlewareReadiness WLCG Middleware Readiness]]



Revision as of 15:07, 8 April 2014

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Introduction

The EGI Staged Rollout is a procedure by which certified updates of the supported middleware (e.g. gLite) are first released to and tested by Early Adopter sites before being made available to all sites through the production repositories. This procedure permits testing an update in a production environment that also is more heterogeneous than what is possible during the certification and verification phases. It allows for potential issues with an update to be discovered at a small scale and potential workarounds to be added to the release notes. In some cases an update may even be rejected. The Staged Rollout serves to increase the confidence in the quality of the updates that pass, such that the vast majority of the sites should experience smooth updates. Sites are invited to participate in the Staged Rollout for services that they have a particular interest in, with the proviso that they may need to debug issues with a particular update and in any case should report their findings. Such participation can be of great value to the production infrastructure and is appreciated!

Grid Operations Meeting

Agenda and minutes GridOpsMeeting

Staged Rollout procedures and workflow

The page Staged-rollout-procedures contains the procedures and workflow during the staged rollout phase. It is still subject to updates and some of the technical implementations in the RT queue staged-rollout will be done soon.

The wiki description follows closely the document: https://documents.egi.eu/secure/ShowDocument?docid=260

Early Adopter teams should try to follow the described procedures, and give feedback for improvements.

Early Adopters

Mailing lists of Early Adopters

  • Group of ARC EA teams: early-adopters-arc<AT>mailman.egi.eu
  • Group of Globus EA teams: early-adopters-globus<AT>mailman.egi.eu
  • Group of gLite EA teams: early-adopters-glite<AT>mailman.egi.eu
  • Group of Operational Tools EA teams: early-adopters-opstools<AT>mailman.egi.eu
  • Group of UNICORE EA teams: early-adopters-unicore<AT>mailman.egi.eu

Reminder: members of Early Adopter teams need a EGI SSO account.

Old table of Early Adopters and Components

Tools

Collaboration between EGI and WLCG

EGI received an expression of interest from WLCG to integrate the WLCG Middleware Readiness working group. The main goal of this group it's not only to improve the quality of the middle-ware products available to the WLCG sites but also increasing the speed at which new products or releases are available to then while avoiding the duplication of effort. This could be achieved by sharing experiences and improving the communication channels of both communities.


The work, discussions, meetings, technical information will be handled in this wiki page: [WLCG Middleware Readiness]



Go to Software Release and Deployment Process