Difference between revisions of "UMD Provisioning"
Jump to navigation
Jump to search
Line 17: | Line 17: | ||
* [http://go.egi.eu/SoftwareProvisioningDashboard Software Provisioning Dashboard in RT] | * [http://go.egi.eu/SoftwareProvisioningDashboard Software Provisioning Dashboard in RT] | ||
* [http://repository.egi.eu EGI Software Repository] | * [http://repository.egi.eu EGI Software Repository] | ||
==== A proposal for changes to the Provisioning workflow ==== | |||
StagedRollout (TSA1.3) drafted a proposal on how to change the UMD Provisioning workflow. | |||
The proposal and related discussions are documented [[UMD:Provisioning:Proposal_SR | here]]. |
Revision as of 13:51, 9 February 2012
Technology | Software Component Delivery | Software Provisioning | UMD Middleware | Cloud Middleware Distribution | Containers Distribution | Technology Glossary |
UMD Provisioning | | Software Provisioning Process | | UMD Release Process | | Software Provisioning Release descriptor tool | | Glossary |
An overview of the provisioning efforts can be found in the SA2 provisioning metrics spreadsheet. The information is updated daily.
EGI's UMD Provisioning activity governs and executes two main processes:
- Software Provisioning Process: That handles software delivery from Technology Providers, Quality Assurance and Reporting.
- UMD Release Process: That collects tested Products per Platform and Architecture (PPAs) into UMD Releases.
You can monitor the current status of the software provisioning process using
A proposal for changes to the Provisioning workflow
StagedRollout (TSA1.3) drafted a proposal on how to change the UMD Provisioning workflow.
The proposal and related discussions are documented here.