Difference between revisions of "EGI Cloud Middleware Distribution"

From EGIWiki
Jump to: navigation, search
([D] Three repositories, using UMD for commons)
(First release already published)
 
(47 intermediate revisions by one other user not shown)
Line 1: Line 1:
== Cloud Middleware Distribution ==
+
{{Template:Tech menubar}} {{CMD_Menu}} {{TOC_right}}
  
One or more new distributions, called Cloud Middleware Distributions (CMD), will be created and managed. 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).
+
== Introduction ==
  
The new cloud distributions will be used to distribute OpenStack and OpenNebula integration components (not the framework themselves). '''All the products must be available both as CentOS7 and Ubuntu packages'''. Two or more versions of the same CMD distribution will be distributed in parallel, following the need of sites to stick with their installations.
+
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, SR, etc. will be allowed and performed as well on the cloud distributions with no development needed on the repository side.
+
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.
+
* CMD-OS (OpenStack)
 +
* CMD-ONE (OpenNebula)
  
Components can be classified as:  
+
Components are included as follows:  
  
* OpenStack specific components
+
* OpenStack specific components -> CMD-OS
* OpenNebula specific components
+
* OpenNebula specific components -> CMD-ONE
* common components (BDII, SSM, VMCatcher...)
+
* common cloud components (BDII, SSM, VMCatcher...) -> all CMD-*
  
Different granularities are possible when designing the set of the distributions, some proposals are shown below.  
+
[[File:two-distros.png|800px|center]]
  
=== [A] Unique repository ===
+
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.
  
* one unique CMD distribution will handle all the three kinds of components
+
'''At the moment all the products in CMD must be available both as CentOS7 and Ubuntu Xenial packages'''.
* the unique CMD will follow the OpenStack release cycle (6 months) and the OpenNebula major release cycle (years)
 
* every CMD major release will stick to a specific OpenStack release, while the OpenNebula components will be reincluded in a newer distribution when decommissioning of a specific release is needed
 
  
** CMD1 Liberty+ONE5
+
'''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.
** CMD2 Mitaka+ONE5
 
** ...
 
  
Comments:
+
== Including your products into CMD ==
  
* - ONE support would need to migrate their packages to the new CMD about every 6 months following the OpenStack EOLs without real need but the fact that OpenStack is migrating to a new major
+
In order to include your products in CMD, you need to:
* - OpenNebula sites should be asked to upgrade to a new major release (OpenStack-driven) without real changes for them, just because from time to time a release needs to be decommissioned
 
  
=== [B] Two repositories  ===
+
# 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, providing all the needed related information
 +
# start the technical inclusion process, named Software Provisioning Process
  
*two CMD distributions, one for OpenStack (CMD-OS) and one for OpenNebula (CMD-ONE), will handle the respective components and release cycles (6-months and years)
+
Please follow the instructions below to do so.
*common components will be included in both the distributions
 
*every CMD major release will stick to a specific OpenStack release or OpenNebula release, for instance
 
  
**CMD-OS 1 (Liberty)
+
=== Join URT as Technology Provider ===
**CMD-ONE 1 (ONE5)
 
**CMD-OS 2 (Mitaka)
 
**...
 
  
Comments:
+
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.
  
* + components follow the natural release cycle of the CMF
+
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].
* + easy for the site, one repo and ready to go
 
* - common packages are duplicated into each CMF-related distribution
 
  
=== [C] Three repositories ===
+
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.
  
* three CMD distributions, one for OpenStack (CMD-OS), one for OpenNebula (CMD-ONE), one for the common components, will handle the respective components and release cycles
+
In order to join as a Technology Provider, or to add a new product to the release, the Technology Provider needs to:
* every CMD major release will still stick to a specific OpenStack release or OpenNebula release, for instance
 
  
** CMD-OS 1 (Liberty)
+
* get an [https://www.egi.eu/sso/ EGI SSO] if you don't have one
** CMD-ONE 1 (ONE5)
+
* send an email to operations at egi.eu, asking to be added to the URT group; in the email, please include the following details:
** CMD-common 1
+
** '''Name''' of the Technology provider
** CMD-OS 2 (Mitaka)
+
** '''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)
  
Comments:
+
The Technology Provider will be added to the [https://wiki.egi.eu/wiki/Technology_Providers Technology Provider wiki page].
* + avoid duplicating common packages
 
* + if issues arise with a common distribution, we can always switch to [B] and dismiss the common distribution
 
* - if one project evolves faster than the other, supporting backward compatibility with the slower one could be an issue
 
* - can bring to dependency problems
 
  
=== [D] Three repositories, using UMD for commons ===  
+
=== Add your products to CMD ===
  
* three CMD distributions, one for OpenStack (CMD-OS), one for OpenNebula (CMD-ONE), and UMD4 for the common components, will handle the respective components and release cycles
+
For each product to be included in CMD, the Technology Provider is asked to:
* every CMD major release will still stick to a specific OpenStack release or OpenNebula release, for instance
 
  
** CMD-OS 1 (Liberty)
+
* provide a complete [https://wiki.egi.eu/wiki/EGI_Cloud_Middleware_Distribution_products 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
** CMD-ONE 1 (ONE5)
+
* create GGUS Support Unit to receive and handle incidents (define [[FAQ GGUS-QoS-Levels|level of quality of support]])
** UMD4 (common)
+
* agree on [https://documents.egi.eu/document/2282 Technical Provider Underpinning Agreement] (TP UA) with EGI.eu, for a single product or for a group of products
** CMD-OS 2 (Mitaka)
 
** ...
 
  
Comments:
+
For each of the steps above, please ask for help to '''operations at egi.eu'''.
* + avoid duplicating common packages
+
 
* + handle automatically complex dependencies that might be brought by grid-related components
+
=== Software Provisioning Process ===
* + if issues arise with a common distribution, we can always switch to [B] and dismiss the common distribution (i.e. make a new UMD major without the commons)
+
 
* - if one project evolves faster than the other, supporting backward compatibility with the slower one could be an issue
+
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].
* - UMD4 sticks to grid components and their release cycle, which may diverge from the cloud-specific ones
+
 
* - can bring to dependency problems
+
=== 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

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