The EGI Software Repository provides a unified point of access for the Grid and Cloud Middleware Distributions, the Community Repositories and the operational tools used throughout the EGI Infrastructure.
- UMD repositories
The Unified Middleware Distribution (UMD) is an integrated set of software components contributed by Technology Providers and packaged for deployment as production quality services in EGI. You may find the UMD release schedule here. For more information on supported systems and setup instructions, please refer to the dedicated page of the latest major release
- CMD repositories
The Cloud Middleware Distribution (CMD) contains OpenStack and OpenNebula integration components developed by Cloud Technology Providers. Two different distributions are available, CMD-OS for OpenStack and CMD-ONE for OpenNebula. For further details, please have a look at the EGI Cloud Middleware Distribution wiki. For more information on supported systems and setup instructions, please refer to the CMD-OS and CMD-ONE dedicated pages of the latest major release.
- UMD/CMD Quality Assurance
UMD and CMD packages that are production-grade and have undergone through a quality assurance process may be found under the respective “production” repositories. Sites willing to install cutting-edge software may use the testing repositories, which contain products scheduled for the next UMD/CMD release and which have successfully passed the 1st stage of verification process, or even the untested repositories which contain products as received from the Technology Providers and which have not undergone any verification or certification process, yet.
- Community repositories
The Community repositories contain community-driven software and products managed through the EGI Applications Database and released through the EGI Software Repository. Two special cases of community repositories are the Preview repository and the Third-party repository.
- Preview repository
The aim of the Preview community repository is to make the updates of middleware products available from a single endpoint, as soon as they are released by Technology Providers. These are the same updates that will also undergo the usual UMD verification and staged rollout processes, which require several weeks to be completed. Through the Preview repository, resource center administrators can avoid the wait and apply the updates on their machines as soon as they are announced. Our plan is to release the Preview updates on a monthly basis, after having gathered the relevant information by the product teams. For more details, you may also refer to its dedicated pages in the EGI Applications Database and the EGI wiki. Please note that EGI provides the preview repository without any additional quality assurance process, and that its products are released as they are provided by the product team. EGI recommends the use of the UMD repositories, which contain software verified through the quality assurance process of UMD.
- Third-party repository
The Third-party community repository contains software not distributed through UMD and managed by third party providers. For more details and instructions, please refer to its dedicated page in the EGI Applications Database.
- Tools
Apart from the UMD/CMD and community repositories, the EGI Software Repository also provides access to tools used internally by the infrastructure, such as the trust anchor and service availability monitoring.
- EGI Core Trust Anchor Distribution
The trust anchor repository contains packages for a a common set of trust anchors, which all sites in EGI should install, in order to ensure interoperability within and outside of EGI. Details may be found on the dedicated wiki page.
- EGI InSPIRE Service Availability Monitoring (SAM) framework
The SAM repository contains packages for monitoring probes based on Nagios and ActiveMQ. These probes are obsolete, as they have been superseded by the ARGO Monitoring engine and are provided for reference only.
