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 1: | Line 1: | ||
{{Tech menubar}} | {{Tech menubar}} {{SWProv menubar}} | ||
[[ | |||
{{TOC_right}} | |||
'''Unified Middleware Distribution''' is “the integrated set of software components contributed by Technology Providers and packaged for deployment as productionquality<br>services in EGI.” | |||
An overview of the provisioning efforts can be found in the [https://rt.egi.eu/rt/SA2/sa2-sw-rel-verification-metrics.xls 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. | |||
[[Image:SW-provisioning.png|800px|SW-provisioning.png]] | |||
<br> You can monitor the current status of the software provisioning process using | |||
*[http://go.egi.eu/SoftwareProvisioningQueue Software Provisioning Queue in RT] | |||
*[http://go.egi.eu/SoftwareProvisioningDashboard Software Provisioning Dashboard in RT] | |||
*[http://repository.egi.eu EGI Software Repository] | |||
==== UMD Repositories ==== | |||
*'''Untested:''' includes everything that is currently in the Unverified or In Verification State, URL: [http://repository.egi.eu/sw/untested/umd/ 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/ 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/ http://repository.egi.eu/sw/production/umd/candidate/] | |||
*'''Production''' includes everything that is released to production, URL: [http://repository.egi.eu/sw/production/umd/ http://repository.egi.eu/sw/production/umd/] | |||
<br> | |||
===== Mirroring of UMD Repositories ===== | |||
*Please find information on how to mirror UMD repos in [[MirroringUMD]] page | |||
We provide some information needed in order to mirror UMD repositories | |||
====== Communication ====== | |||
*Mailing-lists | |||
**for announcements (changes, new repos, etc): mirror-egi at egi.eu | |||
**for discussion: mirror-egi-d at egi.eu | |||
====== Repos size estimates ====== | |||
*file.txt with "du -hs /<dir_repos> | |||
====== | ====== Export License ====== | ||
Do we need something similar to http://fedoraproject.org/wiki/Infrastructure/Mirroring#Export_Compliance ? | |||
====== | ====== Mirroring ====== | ||
*Using rsync | |||
**do we have a rsync server? seems no ("rsync: failed to connect to repository.egi.eu: Connection timed out (110)") | |||
<code>rsync -vaH --exclude=pattern_to_exclude --numeric-ids --delete --delete-after --delay-updates rsync://repository.egi.eu/sw/production/umd ${LOCAL_DIR} <code></code> | |||
<code> | <code> | ||
*Using lftp | |||
**Depending on what repositories you want to mirror and the space you have available (see [[#Repos_size_estimates]] you can use something similar: | |||
***to create the mirror for the first time: | |||
* Using lftp | |||
** Depending on what repositories you want to mirror and the space you have available (see [[# | <code> lftp -c mirror --verbose --exclude 'candidate/' --exclude '1/' --exclude '2/' http://repository.egi.eu/sw/production/umd/ ${LOCAL_DIR} <code> | ||
*** to create the mirror for the first time: | |||
***to removes any local packages that no longer exist on the source, and only downloads newer package versions from the host mirror: | |||
lftp -c mirror --verbose --exclude 'candidate/' --exclude '1/' --exclude '2/' http://repository.egi.eu/sw/production/umd/ ${LOCAL_DIR} | </code> | ||
*** to removes any local packages that no longer exist on the source, and only downloads newer package versions from the host mirror: | <code><code> lftp -c mirror -–delete –-only-newer http://repository.egi.eu/sw/production/umd/ ${LOCAL_DIR} <code></code> | ||
<code> | |||
lftp -c mirror -–delete –-only-newer http://repository.egi.eu/sw/production/umd/ ${LOCAL_DIR} | [[Category:Technology]] | ||
<code> | |||
Revision as of 16:44, 10 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 |
Unified Middleware Distribution is “the integrated set of software components contributed by Technology Providers and packaged for deployment as productionquality
services in EGI.”
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
We provide some information needed in order to mirror UMD repositories
Communication
- Mailing-lists
- for announcements (changes, new repos, etc): mirror-egi at egi.eu
- for discussion: mirror-egi-d at egi.eu
Repos size estimates
- file.txt with "du -hs /<dir_repos>
Export License
Do we need something similar to http://fedoraproject.org/wiki/Infrastructure/Mirroring#Export_Compliance ?
Mirroring
- Using rsync
- do we have a rsync server? seems no ("rsync: failed to connect to repository.egi.eu: Connection timed out (110)")
rsync -vaH --exclude=pattern_to_exclude --numeric-ids --delete --delete-after --delay-updates rsync://repository.egi.eu/sw/production/umd ${LOCAL_DIR} <code>
- Using lftp
- Depending on what repositories you want to mirror and the space you have available (see #Repos_size_estimates you can use something similar:
- to create the mirror for the first time:
<code> lftp -c mirror --verbose --exclude 'candidate/' --exclude '1/' --exclude '2/' http://repository.egi.eu/sw/production/umd/ ${LOCAL_DIR} <code>
- to removes any local packages that no longer exist on the source, and only downloads newer package versions from the host mirror:
<code> lftp -c mirror -–delete –-only-newer http://repository.egi.eu/sw/production/umd/ ${LOCAL_DIR} <code>