UMD Provisioning

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.”

Minimal requirements

1. 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
   • Provide (regular) info on where to find the packages and their updates
     
2. Documentation references
   • installation & configuration guides, release notes
     
3. Support calendar
   
   • Which releases, versions, are going to be released in UMD and their lifetime
     
4. Support through GGUS
   • declare the support level and the SU: https://wiki.egi.eu/wiki/FAQ_GGUS-QoS-Levels
     
5. 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:

1. Software Provisioning Process: That handles software delivery from Technology Providers, Quality Assurance and Reporting.
2. 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

• Software Provisioning Queue in RT
• Software Provisioning Dashboard in RT
• 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/
• 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>