|Technology||Software Component Delivery||Software Provisioning||UMD Middleware||Cloud Middleware Distribution||Containers Distribution||Technology Glossary|
|Middleware menu:||Home||Software Calendars||Technology Providers||UMD Release Schedule||UMD Products Overview||UMD Products ID Cards||Release and deployment process||Middleware Requirements||Next middleware release|
This wiki collects all the information concerning Middleware supported in EGI.
UMD3 and UMD4 (main middleware distribution)
Unified Middleware Distribution (UMD) is the integrated set of software components contributed by Technology Providers and packaged for deployment as production quality services in EGI.
UMD4 is the current supported UMD distribution. It supports CentOS7, SL6. Also Ubuntu 16 (Xenial) will be supported in the future, if Technology Providers require that.
UMD3 will still receive security or critical updates for SL6. UMD3/SL5 and UMD3/Debian are not supported anymore.
Support for yaim
With UMD4/CentOS7 yaim is not supported anymore as a tool to configure the distributed middleware. Instead, every product will follow its documented procedure to install, configure, test the product.
So for each product, UMD users will point to the product-specific documentation, which will provide puppet recipes, or ansible recipes, or custom scripts or even step-by-step guides (this last is true especially with very simply configurated products). Even yaim can be used as a configuration tool, and indeed you will find it distributed in the upcoming UMD4.4, but this will mean that some team (in this case the VOBOX) is using yaim to configure their products.
Why is SL6 both in UMD3 and UMD4?
The UMD3/SL6 and UMD4/SL6: the latter is a mirror of the former excluding products that are reaching or already reached end of life. If you want to install a UI, you can use both, but we advice to use UMD4/SL6.Of course dedicated documentation will be provided with the release in CentOS7.
CMD-OS and CMD-ONE (cloud middleware)
The Cloud Middleware Distribution (CMD) distributes OpenStack and OpenNebula integration components developed by Cloud Technology Providers to Resource Centres (i.e. cloud sites).
Two different distribution are available, CMD-OS for OpenStack and CMD-ONE for OpenNebula. For further details, please have a look at the Cloud Middleware Distribution wiki https://wiki.egi.eu/wiki/EGI_Cloud_Middleware_Distribution .
UMD and CMD
Regular grid components and in general all non cloud-specific components will keep going to UMD. Also clients for the user to interact with the EGI infrastructure are distributed with UMD (storage clients, cloud-related clients).
At the moment UMD4 is supported, accepting CentOS7 and SL6 packages. Ubuntu is not yet enabled.
Products in UMD major releases should have a release cycle that is compatible with the UMD one: major releases are supported with updates for at least 1 year, security for 2 years. As this doesn't happen with OpenStack related components, we created CMD for OpenStack.
CMD for OpenNebula has been created to decouple from OpenStack, having a very different release cycle.
|Description||Operating Systems supported|
|UMD4||Regular grid components and in general all non cloud-specific components will keep going to UMD. Also clients for the user to interact with the EGI infrastructure are distributed with UMD (storage clients, cloud-related clients).||CentOS7, SL6|
|CMD-OS||OpenStack integration components developed by Cloud Technology Providers to Resource Centres||CentOS7, Xenial|
|CMD-ONE||OpenNebula integration components developed by Cloud Technology Providers to Resource Centres||CentOS7|
|Software Calendars||Support Calendar, Decommissioning Calendar, Operations Calendar|
|Technology Providers list||Information about Technology Providers supporting EGI|
|Unified Middleware Distribution (UMD) release schedule||the planned release schedule for UMD major and minor releases|
|Release and deployment process||describes the EGI process to deploy new versions of deployed software and operational tools into the EGI production infrastructure|
|Middleware and Tool Requirements||existing requirements, how to submit requirements|
|Cloud Middleware Distribution||details on the CMD release cycle(still proposal)|