Difference between revisions of "Staged Rollout"
Line 17: | Line 17: | ||
update and in any case should report their findings. Such participation | update and in any case should report their findings. Such participation | ||
can be of great value to the production infrastructure and is appreciated! | can be of great value to the production infrastructure and is appreciated! | ||
[http://glite.cern.ch] | |||
== Instructions for the transition period == | == Instructions for the transition period == |
Revision as of 12:22, 21 January 2011
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.
Early Adopters
- List of Early Adopters: software components and the corresponding Early Adopters
- List of Components: components with the corresponding number of Early Adopters. Note: please consult this list when applying to participate to the Staged Rollout of one or more components.
- Simple report templates for the staged rollout: https://documents.egi.eu/public/ShowDocument?docid=254
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: administrators of Early Adopter sites need a EGI SSO account.
Tools
EGI Single Sign On (SSO) | RT | UMD repositories
External links
- gLite workplan at savannah: [https://savannah.cern.ch/task/?group=jra1workplan]