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.
Software release and deployment process
Revision as of 14:52, 10 December 2012 by Krakow (talk | contribs) (Created page with "{{Template:Op menubar}} {{TOC_right}} Category:Middleware This section describes the EGI process to deploy new versions of deployed software and operational tools into the ...")
| Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
This section describes the EGI process to deploy new versions of deployed software and operational tools into the EGI production infrastructure.
Software Provisioning
- EGI Software Provisioning
- ÍMPORTANT. Software Provisioning Dashboard showing by category products still to be verified, under verification, in staged rollout, and ready for being included in the next UMD release
Software Deployment
- Learn about Staged Rollout
- Staged Rollout workflow
- Staged Rollout managers:
- ARC: Christian Ulrik Soettrup
- gLite: Mario David
- GLOBUS: Mario David
- UNICORE: Mathilde Romberg
- SAM: Daniele Cesini
- Early Adopters:
- Early Adopters
- Distribution of Early Adopters per component
- NO_EA List of products without EA, they will not be submitted to the UMD SW provisioning]
- Software Provisioning Dashboard
- EGI IGTF Release Process
- WMS service versions monitoring (from Glue1.3 - TopBDII): WMS_Monitor
- CE's service versions monitoring (from Glue1.3 - TopBDII): CE_Monitor