Difference between revisions of "EGI Cloud Middleware Distribution"

From EGIWiki
Jump to: navigation, search
([A] Unique repository)
m (typoes &, punctoes)
Line 5: Line 5:
 
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.  
 
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.  
  
No changes have been requested to the regular UMD workflow, so verifications, SR etc will be allowed and performed as well with no deveopment needed on the repository side.  
+
No changes have been requested to the regular UMD workflow, so verifications, SR, etc. will be allowed and performed as well with no development needed on the repository side.  
  
 
After creating the first CMD release we will use the experience to create a straightforward procedure to create the next major/minor versions.  
 
After creating the first CMD release we will use the experience to create a straightforward procedure to create the next major/minor versions.  

Revision as of 12:43, 19 April 2016

Cloud Middleware Distribution

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).

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.

No changes have been requested to the regular UMD workflow, so verifications, SR, etc. will be allowed and performed as well with no development needed on the repository side.

After creating the first CMD release we will use the experience to create a straightforward procedure to create the next major/minor versions.

Components can be classified as:

  • OpenStack specific components
  • OpenNebula specific components
  • common components (BDII, SSM, VMCatcher...)

Different granularities are possible when designing the set of the distributions, some proposals are shown below.

[A] Unique repository

  • one unique CMD distribution will handle all the three kinds of components
  • 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
    • CMD2 Mitaka+ONE5
    • ...

Comments:

  • 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

[B] Two repositories

  • 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)
  • 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)
    • CMD-ONE 1 (ONE5)
    • CMD-OS 2 (Mitaka)
    • ...

Comments:

  • components follow the natural release cycle of the CMF
  • common components are not so many, so they can be included in the two distributions with little effort

[C] Three repositories

  • 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
  • every CMD major release will still stick to a specific OpenStack release or OpenNebula release, for instance
    • CMD-OS 1 (Liberty)
    • CMD-ONE 1 (ONE5)
    • CMD-common 1
    • CMD-OS 2 (Mitaka)
    • ...

Comments:

  • CMD-common release cycle and OS distribution may diverge from the cloud-specific ones

[D] Three repositories, using UMD for commons

  • 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
  • every CMD major release will still stick to a specific OpenStack release or OpenNebula release, for instance
    • CMD-OS 1 (Liberty)
    • CMD-ONE 1 (ONE5)
    • UMD4 (common)
    • CMD-OS 2 (Mitaka)
    • ...

Comments:

  • UMD4 sticks to grid components and their release cycle, which may diverge from the cloud-specific ones