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
Minimal requirements
Software Provisioning
| Line 55: | Line 55: | ||
===== Mirroring of UMD Repositories ===== | ===== Mirroring of UMD Repositories ===== | ||
*Please find information on how to mirror UMD repos in [[MirroringUMD]] page | * Please find information on how to mirror UMD repos in [[MirroringUMD]] page | ||
[[Category:Technology]] | [[Category:Technology]] | ||
Revision as of 10:07, 14 December 2014
| Technology | Software Component Delivery | Software Provisioning | UMD Middleware | Cloud Middleware Distribution | Containers Distribution | Technology Glossary |
| Software Provisioning menu: | Software Provisioning Process | UMD Release Process | Quality Assurance | UMD | Staged Rollout |
 This page is under construction.
|
Unified Middleware Distribution is “the integrated set of software components contributed by Technology Providers and packaged for deployment as productionquality
services in EGI.”
Minimal requirements
- Components/products formats & release channels
- Formats:
- rpms for SL5 & SL6, and debs for Debian6
- packages should have dependencies on packages provided by the respective OS and EPEL
(for Fedora/SL family) - any other external dependencies should be also provided
- rpms for SL5 & SL6, and debs for Debian6
- Provide (regular) info on where to find the packages and their updates
- Formats:
- Documentation references
- installation & configuration guides, release notes
- installation & configuration guides, release notes
- Support calendar
- Which releases, versions, are going to be released in UMD and their lifetime
- Which releases, versions, are going to be released in UMD and their lifetime
- Support through GGUS
- declare the support level and the SU: https://wiki.egi.eu/wiki/FAQ_GGUS-QoS-Levels
- declare the support level and the SU: https://wiki.egi.eu/wiki/FAQ_GGUS-QoS-Levels
- Early Adopters
- volunteer sites willing to do the first install/exposure of new versions in a productio environment
Software Provisioning
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
UMD Repositories
- Untested: includes everything that is currently in the Unverified or In Verification State, URL: http://repository.egi.eu/sw/untested/umd/
- Testing: includes everything that is currently in the Stage Rollout or UMD-Store State, URL: http://repository.egi.eu/sw/testing/umd/
- Release Candidate: includes releases that are about to be published, URL: http://repository.egi.eu/sw/production/umd/candidate/
- Production includes everything that is released to production, URL: http://repository.egi.eu/sw/production/umd/
Mirroring of UMD Repositories
- Please find information on how to mirror UMD repos in MirroringUMD page