EGI Cloud Middleware Distribution

From EGIWiki
Revision as of 13:55, 30 May 2016 by Spinoso (talk | contribs)
Jump to: navigation, search
CMD menu: Overview Products Process Release schedule


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 on the cloud distributions 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 cloud components (BDII, SSM, VMCatcher...)
  • regular grid components (in current UMD3/UMD4)

Distributions

Two-distros.png
  • 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
  • + 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