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"
| Line 9: | Line 9: | ||
The EGI Staged Rollout is a procedure by which certified updates of the supported middleware 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== | The EGI Staged Rollout is a procedure by which certified updates of the supported middleware 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. | [[Transition]] describes the procedure to be followed during the transition period until all EGI process and tools are fully in place. | ||
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 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. | ||
Revision as of 15:10, 23 March 2016
| Technology | Software Component Delivery | Software Provisioning | UMD Middleware | Cloud Middleware Distribution | Containers Distribution | Technology Glossary |
| Software Provisioning menu: | Software Provisioning Process | UMD Release Process | Quality Assurance | UMD | Staged Rollout |
Introduction
The EGI Staged Rollout is a procedure by which certified updates of the supported middleware 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!
Reminder: members of Early Adopter teams need a EGI SSO account.
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 to increase the speed at which new products or releases are available to sites 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]