EGI Core activities:2013-bidding Staged Rollout

From EGIWiki
Jump to: navigation, search
Main operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security

EGI Core services menu: Services PHASE I Services PHASE II Services PHASE III Bids Payments Travel procedure Performance

Go back to the EGI Core Activities Bidding page.

Go back to the Core EGI activity list.

  • Service name: Staged rollout
  • Service category: Software
  • Service type: Coordination


The Staged Rollout is a procedure by which certified updates of the supported middleware are first tested by Early Adopter (EA) sites before being made available to all sites through the production repositories. This procedure permits to test an update in a production environment that exposes the product to more heterogeneous use cases than the certification and verification phase. This allows the discovery of potential issues and potentially to add mitigation information to the UMD release notes.

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.


This activity is responsible for the coordination of the Early Adopters activity, namely assign and monitor the progress of each individual product and corresponding EA teams, collect and analyze the reports provided by the EA team and in case of issues found make sure that relevant information is properly handled.

Another important activity is the constant scouting for new early teams and problems in the UMD products both in terms of security and maintenance.


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.

Together with those activities it also includes to:

  • maintenance of the EA tables;
  • Contribute in handling the PPAs advancement in the software provisioning process.

Service level targets

EA teams must receive support, for questions related to the SR process, during working hours and for emergency releases.