EGI-InSPIRE:MS108 Staged Rollout

From EGIWiki
(Redirected from MS108 Staged Rollout)
Jump to: navigation, search
EGI Inspire Main page




Notes to contributors

Assessment: (Provide an assessment of the delivery of services over the past year from a managerial perspective; highlight positive areas and areas for improvement; do not include future plans; text should be roughly 1-2 paragraphs)

Score: (assign a numerical score from 1 to 5 with a succinct explanation of what needs to be improved to increase your score – remove numerical description references upon completion) 1 = An unacceptable level of service was delivered

2 = A level of service that was below expectations was delivered

3 = An acceptable service level has been delivered

4 = A level of service that exceeded expectations was delivered, but there is scope for even further improvement

5 = An excellent service has been delivered that should be considered as best practice


Table 4: EGI Global task assessment:Staged rollout
# Name Assessment Score How to Improve
# Staged rollout Task inherited from EGEE III. Already existing pool of Early Adopter sites. During the reporting period there was an increase of this pool that covers, presently, all gLite, ARC and most of Unicore and Globus components, as well as Operational Tools (SAM framework and Nagios probes). Only the gLite components and SAM/Nagios are going through the staged rollout test.

From the managerial point of view: the task leader is coordinating the staged rollout of gLite components. It has an active role in the discussions and definition of the Software Release Workflow in conjunction with SA2. A gradual transition from the EGEE III legacy procedures to the new procedures is underway, but obliges additional effort while using both of them. There are expert coordinators for each type of Software (or Middleware), though only gLite and Operational Tools are active.

3 Have the full EGI SW Release workflow in place, and get all involved parties using it.

For each component, to have several early adopter sites in order to cover: redundancy, heterogeneity (more then one deployment scenario, different supported VOs and applications workflows).

To have schedules of the next releases in advance, and their content/components, as well as an overview of bug fixes and new features.