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.
Difference between revisions of "UMD Provisioning"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
{{TOC_right}} | {{TOC_right}} | ||
EGI's UMD Provisioning activity governs and executes two main processes: | |||
# Software Provisioning: 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. | |||
[[Image:SW-provisioning.png|800px]] | [[Image:SW-provisioning.png|800px]] | ||
Revision as of 15:40, 18 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: 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.
