EGI Cloud Middleware Distribution
|CMD menu:||Overview||Products||Process||Release schedule|
Cloud Middleware Distribution (CMD)
CMD aims at distributing OpenStack and OpenNebula integration components (not the framework themselves).
No changes have been requested to the regular UMD workflow, so verifications, Staged-Rollout, etc. will be allowed and performed as well on the cloud distributions with no development needed on the repository side. No changes are needed to create a new distribution; composer has been built to support several distributions, but never used so it has just to be tested. Each distribution, just like UMD, will start from major release number 1, going in parallel with UMD (already used for separated grid products).
After creating the first CMD release we will use the experience to create a straightforward procedure to create the next major/minor versions.
Two platforms will be supported:
As a consequence, two distributions will be created:
- CMD-OS (OpenStack)
- CMD-ONE (OpenNebula)
Components will be included as follows:
- OpenStack specific components -> CMD-OS
- OpenNebula specific components -> CMD-ONE
- common cloud components (BDII, SSM, VMCatcher...) -> all CMD-*
- regular grid components (in current UMD3/UMD4) -> usual UMD
The two CMD distributions, one for OpenStack (CMD-OS) and one for OpenNebula (CMD-ONE), will handle the respective release cycles:
- 6-months for OpenStack, see http://releases.openstack.org/
- years for OpenNebula, see http://opennebula.org/software/release/
Every CMD major release will stick to a specific OpenStack release or OpenNebula release, for instance:
- CMD-OS 1 (Liberty)
- CMD-ONE 1 (ONE5)
- CMD-OS 2 (Mitaka)
So for OpenStack for instance, two or more major versions of the same CMD distribution will be distributed in parallel, following the need of sites to stick with their installations. Decommissioning will respectively follow OpenStack and OpenNebula as well.
All the products must be available both as CentOS7 and Ubuntu packages.
- + components follow the natural release cycle of the CMF
- + easy for the site, one repo and ready to go
- + coherency in dependencies is guaranteed because all the packages are put together
- + easier and less error-prone for the release manager
- + if at some point a common package is not common anymore and used only by one fo the two frameworks, or frequent updates are related only to one of the two frameworks, updates are made only on the specific distribution
- - common packages are duplicated into each CMF-related distribution
Including your products into CMD
In order to include your products in CMD, you first need to be included in the UMD Release Team (URT) as a Technology Provider.
URT is a coordination group, under the EGI Operations umbrella. The goal of URT is to continue some of the coordination activities carried out by the Europan middleware projects, keep the communications active between product teams and to open a communication channel between the EGI and the middleware developers.
Technology Providers share a common mailing list (urt-discuss) and follow the UMD Release Team meetings.
Please check if you are already a member of the URT giving a look at the Technology Provider wiki page. In order to join as a Technology Provider, or to add a new product to the release, the Technology Provider needs to:
- get an EGI SSO if you don't have one
- send an email to operations at egi.eu, asking to be added to the URT group; in the email, please include the following details:
- Name of the Technology provider
- Products you want to include and to support, with their description
- Name and contact details of the Team Leader
- Other contacts (support email address, web site address, representative at the URT meeting)
The Technology Provider will be added to the Technology Provider wiki page.
For each product to be included in CMD, the Technology Provider is asked to:
- provide a complete Product ID Card, which will be used to contact the Technology Provider in case of requests for information, security related events/issues, proposals, and any other issues
- create GGUS Support Unit to receive and handle incidents (define level of quality of support)
- agree on Technical Provider Underpinning Agreement (TP UA) with EGI.eu, for a single product or for a group of products
For each of the steps above, please ask for help to operations at egi.eu.
If you need details on the EGI Software Provisioning process, please find them at the following link: https://wiki.egi.eu/wiki/EGI_Software_Component_Delivery
If you need information or details on CMD, please write to operations at egi.eu.
- infrastructure readiness: frontend to be adapted, backend+RT are OK
- Verification: a proposal will be made on how to make it in the CMD context just like we do in UMD, IFCA will provide resources for the OpenStack platform and CESGA for the OpenNebula; wiki to be filled
- Staged-Rollout process: wiki to be filled
- Products https://wiki.egi.eu/wiki/EGI_Cloud_Middleware_Distribution_products to be filled
- XMLs to be created
- First release scheduled by end of September 2016