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 "EGI Core activities:2013-bidding Staged Rollout"
(Created page with "'''Go back to the activity list.''' * Service name: Staged rollout * Service category: Software * Service type: Coordination = Technical description =...") |
|||
| Line 4: | Line 4: | ||
* Service category: Software | * Service category: Software | ||
* Service type: Coordination | * Service type: Coordination | ||
= Introduction = | |||
The Staged Rollout is a procedure by which certified updates of the supported middleware are first released to and tested by Early Adopter (EA) 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. This allows the discovery of potential issues with an update allowing potential workarounds to be added to the release notes. The Staged Rollout increases the confidence in the quality of the updates that pass, such that the vast majority of the sites should experience smooth updates. | |||
= Technical description = | = Technical description = | ||
Revision as of 12:43, 3 July 2013
Go back to the activity list.
- Service name: Staged rollout
- Service category: Software
- Service type: Coordination
Introduction
The Staged Rollout is a procedure by which certified updates of the supported middleware are first released to and tested by Early Adopter (EA) 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. This allows the discovery of potential issues with an update allowing potential workarounds to be added to the release notes. The Staged Rollout increases the confidence in the quality of the updates that pass, such that the vast majority of the sites should experience smooth updates.
Technical description
Staged Rollout is performed by Early Adopter (EA) sites who volunteer to deploy products fulfilling the acceptance criteria in the production infrastructure, exposing them to real users and real use cases.
Coordination
The activity must coordinate the EAs activity, maintaining the EA tables, scouting for new teams, assigning the products to the EAs and retrieving the reports generated during staged rollout. Contribute in handling the PPAs advancement in the software provisioning process.
Operation
This task is also responsible for producing and maintaining the UMD release notes and known issues wiki pages. The task leader must participate the periodic EGI Operations meetings and report about the status of the UMD releases.
Service level targets
EA teams must receive support, for questions related to the SR process, during working hours.