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 64: Line 64:
* [http://glite.cern.ch gLite pages] at CERN
* [http://glite.cern.ch gLite pages] at CERN
----
----
Go to [[Middleware#Software_release_and_deployment_process Software Release and Deployment Process]]
Go to [[Middleware#Software_release_and_deployment_process|Software Release and Deployment Process]]

Revision as of 10:27, 1 March 2011

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!

Instructions for the transition period

Transition describes the procedure to be followed during the transition period until all EGI process and tools are fully in place.

Note: this procedure will be decomissioned when a new process (under definition) is ready for deployment.

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

External links


Go to Software Release and Deployment Process