EGI Core activities:2013-bidding Software provisioning infrastructure

From EGIWiki
Jump to: navigation, search
Main operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security

EGI Core services menu: Services PHASE I Services PHASE II Services PHASE III Bids Payments Travel procedure Performance


Go back to the EGI Core Activities Bidding page.

Go back to the Core EGI activity list.


The software provisioning infrastructure provides the technical tools to support the UMD release process from pulling packages from the developers repositories to the build of a release.

Technical description

The software provisioning infrastructure is composed by the following components:

Note: the architecture of the internal components is not mandatory, but the services provided must be equivalent.

The software provisioning infrastructure must support multiple operating system (SL based, and Debian based) and major releases (at least two major releases).


The task must operate all the technical services described before:

The task must support the UMD release creation, creating the release candidates and the actual releases.
Release candidates must be tested for the installation of all the components, new and already available in the repositories. The test, possibly automated, must be able to generate a report in few hours (less than one working day, possibly 2-4 hours).


The infrastructure must be adapted to the evolution of EGI infrastructure to support:

Service level targets


The activity must provide support through the dedicated GGUS support unit, during working hours


UMD repositories and web front-end, as well as the community repository, must have 90% availability and reliability on a monthly base. The other components used by the UMD team only must have 75% availability and 90% reliability during working hours.

Load Balancing and high availaiblity configuration (between two or more servers) is required in order to handle the load on the repositories and the front-end service.

Personal tools