Difference between revisions of "UMD Provisioning"
Jump to navigation
Jump to search
Line 5: | Line 5: | ||
EGI's UMD Provisioning activity governs and executes two main processes: | EGI's UMD Provisioning activity governs and executes two main processes: | ||
# [[Software Provisioning]]: That handles software delivery from Technology Providers, Quality Assurance and Reporting. | # [[Software Provisioning Process]]: That handles software delivery from Technology Providers, Quality Assurance and Reporting. | ||
# [[UMD Release Building]]: That collects tested Products per Platform and Architecture (PPAs) into UMD Releases. | # [[UMD Release Building]]: That collects tested Products per Platform and Architecture (PPAs) into UMD Releases. | ||
[[Image:SW-provisioning.png|800px]] | [[Image:SW-provisioning.png|800px]] |
Revision as of 16:16, 23 March 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 Building: That collects tested Products per Platform and Architecture (PPAs) into UMD Releases.