Difference between revisions of "UMD Provisioning"
Jump to navigation
Jump to search
Line 8: | Line 8: | ||
# [[UMD Release Process]]: That collects tested Products per Platform and Architecture (PPAs) into UMD Releases. | # [[UMD Release Process]]: That collects tested Products per Platform and Architecture (PPAs) into UMD Releases. | ||
[[Image:SW-provisioning.png|800px]] | [[Image:SW-provisioning.png|800px]] | ||
You can monitor the current status of the software provisioning process using | |||
# [[https://go.egi.eu/SoftwareProvisioningQueue Software Provisioning Queue in RT]] | |||
# [[https://go.egi.eu/SoftwareProvisioningDashboard Software Provisioning Dashboard in RT]] | |||
# [[http://repository.egi.eu EGI Software Repository]] |
Revision as of 15:09, 23 June 2011
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 |
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