Difference between revisions of "EGI Cloud Middleware Distribution"

From EGIWiki
Jump to: navigation, search
(Including your products into CMD)
(First release already published)
 
(17 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{CMD_Menu}} {{TOC_right}}
+
{{Template:Tech menubar}} {{CMD_Menu}} {{TOC_right}}
  
== Cloud Middleware Distribution (CMD) ==
+
== Introduction ==
  
CMD aims at '''distributing OpenStack and OpenNebula integration components''' (not the framework themselves).
+
CMD (Cloud Middleware Distribution) aims at distributing:
 +
* '''OpenStack and OpenNebula integration components''' (not the framework themselves),
 +
* products that are more in general deployed on top of OpenStack/OpenNebula
 +
* other products that enhance the IaaS layer of the federated cloud, even if they’re not directly dependent on OpenStack/OpenNebula
  
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).
+
CMD supports OpenStack and OpenNebula, through two different distributions:  
 
 
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:
 
 
 
* OpenStack
 
* OpenNebula
 
 
 
As a consequence, two distributions will be created:  
 
  
 
* CMD-OS (OpenStack)
 
* CMD-OS (OpenStack)
 
* CMD-ONE (OpenNebula)
 
* CMD-ONE (OpenNebula)
  
Components will be included as follows:  
+
Components are included as follows:  
  
 
* OpenStack specific components -> CMD-OS
 
* OpenStack specific components -> CMD-OS
 
* OpenNebula specific components -> CMD-ONE
 
* OpenNebula specific components -> CMD-ONE
 
* common cloud components (BDII, SSM, VMCatcher...) -> all CMD-*
 
* common cloud components (BDII, SSM, VMCatcher...) -> all CMD-*
* regular grid components (in current UMD3/UMD4) -> usual UMD
 
  
 
[[File:two-distros.png|800px|center]]
 
[[File:two-distros.png|800px|center]]
  
The two CMD distributions, one for OpenStack (CMD-OS) and one for OpenNebula (CMD-ONE), will handle the respective '''release cycles''':  
+
Every CMD major release will stick to a specific OpenStack release or OpenNebula release and handle the respective '''release cycles'''. Please have a look at the [https://wiki.egi.eu/wiki/EGI_Cloud_Middleware_Distribution_schedule CMD release schedule] for more information.
  
* 6-months for OpenStack, see http://releases.openstack.org/
+
'''At the moment all the products in CMD must be available both as CentOS7 and Ubuntu Xenial packages'''.
* 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:  
+
'''NOTICE''': ''Regular grid components and in general all non cloud-specific components will keep going to UMD''. 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.
 
 
**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'''.  
 
 
 
Comments:
 
 
 
* + 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 ==
 
== Including your products into CMD ==
Line 58: Line 32:
  
 
# join [https://wiki.egi.eu/wiki/URT UMD Release Team (URT)] as a [https://wiki.egi.eu/wiki/Technology_Providers Technology Provider]
 
# join [https://wiki.egi.eu/wiki/URT UMD Release Team (URT)] as a [https://wiki.egi.eu/wiki/Technology_Providers Technology Provider]
# add your products to CMD
+
# add your products to CMD, providing all the needed related information
 +
# start the technical inclusion process, named Software Provisioning Process
  
 
Please follow the instructions below to do so.
 
Please follow the instructions below to do so.
Line 68: Line 43:
 
Technology Providers share a [https://mailman.egi.eu/mailman/listinfo/urt-discuss common mailing list (urt-discuss)] and follow the [https://wiki.egi.eu/wiki/URT_meetings_agendas UMD Release Team meetings].  
 
Technology Providers share a [https://mailman.egi.eu/mailman/listinfo/urt-discuss common mailing list (urt-discuss)] and follow the [https://wiki.egi.eu/wiki/URT_meetings_agendas UMD Release Team meetings].  
  
Please check if you are already a member of the URT giving a look at the [https://wiki.egi.eu/wiki/Technology_Providers Technology Provider wiki page]. If so, you can skip to [[Add your products to CMD]]
+
Please check if you are already a member of the URT giving a look at the [https://wiki.egi.eu/wiki/Technology_Providers Technology Provider wiki page]. If so, you can skip to the next section.
  
 
In order to join as a Technology Provider, or to add a new product to the release, the Technology Provider needs to:  
 
In order to join as a Technology Provider, or to add a new product to the release, the Technology Provider needs to:  
Line 79: Line 54:
 
** Other contacts (support email address, web site address, representative at the URT meeting)  
 
** Other contacts (support email address, web site address, representative at the URT meeting)  
  
The Technology Provider will be added to the [https://wiki.egi.eu/wiki/Technology_Providers Technology Provider wiki page].  
+
The Technology Provider will be added to the [https://wiki.egi.eu/wiki/Technology_Providers Technology Provider wiki page].
  
 
=== Add your products to CMD ===
 
=== Add your products to CMD ===
Line 90: Line 65:
  
 
For each of the steps above, please ask for help to '''operations at egi.eu'''.  
 
For each of the steps above, please ask for help to '''operations at egi.eu'''.  
 +
 +
=== Software Provisioning Process ===
 +
 +
After performing the steps above, your product can be added to CMD releases following the [https://wiki.egi.eu/wiki/EGI_Cloud_Middleware_Distribution_process middleware distribution process].
  
 
=== More information ===
 
=== More information ===
Line 99: Line 78:
 
If you need information or details on CMD, please write to operations at egi.eu.  
 
If you need information or details on CMD, please write to operations at egi.eu.  
  
== Plans ==
+
== Plans and roadmaps ==
  
 
* infrastructure readiness: frontend to be adapted, backend+RT are OK
 
* infrastructure readiness: frontend to be adapted, backend+RT are OK
Line 106: Line 85:
 
* Products https://wiki.egi.eu/wiki/EGI_Cloud_Middleware_Distribution_products to be filled
 
* Products https://wiki.egi.eu/wiki/EGI_Cloud_Middleware_Distribution_products to be filled
 
* XMLs to be created
 
* XMLs to be created
* First release scheduled '''by end of September 2016'''
 

Latest revision as of 09:18, 4 February 2019

Technology Software Component Delivery Software Provisioning UMD Middleware Cloud Middleware Distribution Containers Distribution Technology Glossary


CMD menu: Overview Products Process Release schedule


Introduction

CMD (Cloud Middleware Distribution) aims at distributing:

  • OpenStack and OpenNebula integration components (not the framework themselves),
  • products that are more in general deployed on top of OpenStack/OpenNebula
  • other products that enhance the IaaS layer of the federated cloud, even if they’re not directly dependent on OpenStack/OpenNebula

CMD supports OpenStack and OpenNebula, through two different distributions:

  • CMD-OS (OpenStack)
  • CMD-ONE (OpenNebula)

Components are included as follows:

  • OpenStack specific components -> CMD-OS
  • OpenNebula specific components -> CMD-ONE
  • common cloud components (BDII, SSM, VMCatcher...) -> all CMD-*
Two-distros.png

Every CMD major release will stick to a specific OpenStack release or OpenNebula release and handle the respective release cycles. Please have a look at the CMD release schedule for more information.

At the moment all the products in CMD must be available both as CentOS7 and Ubuntu Xenial packages.

NOTICE: Regular grid components and in general all non cloud-specific components will keep going to UMD. 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.

Including your products into CMD

In order to include your products in CMD, you need to:

  1. join UMD Release Team (URT) as a Technology Provider
  2. add your products to CMD, providing all the needed related information
  3. start the technical inclusion process, named Software Provisioning Process

Please follow the instructions below to do so.

Join URT as 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. If so, you can skip to the next section.

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.

Add your products to CMD

For each product to be included in CMD, the Technology Provider is asked to:

For each of the steps above, please ask for help to operations at egi.eu.

Software Provisioning Process

After performing the steps above, your product can be added to CMD releases following the middleware distribution process.

More information

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

Contacts

If you need information or details on CMD, please write to operations at egi.eu.

Plans and roadmaps

  • 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