The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "EGI Cloud Middleware Distribution"
Jump to navigation
Jump to search
(Created page with "== Cloud Middleware Distribution == A new distribution, called Cloud Middleware Distribution (CMD), will be created: * it will follow the OpenStack release cycle (6 months) * ...") |
|||
| Line 8: | Line 8: | ||
* every CMD major release will stick to a specific OpenStack release, for instance: | * every CMD major release will stick to a specific OpenStack release, for instance: | ||
CMD1->Kilo | ** CMD1->Kilo | ||
CMD2->Liberty | ** CMD2->Liberty | ||
CMD3->(Mitaka) | ** CMD3->(Mitaka) | ||
* OTOH the OpenStack version does not really matter to CMD; the OS supported does (for path naming etc) | * OTOH the OpenStack version does not really matter to CMD; the OS supported does (for path naming etc) | ||
Revision as of 17:34, 23 March 2016
Cloud Middleware Distribution
A new distribution, called Cloud Middleware Distribution (CMD), will be created:
- it will follow the OpenStack release cycle (6 months)
- CMD is just a new distribution, like UMD, starting from major release number 1, going in parallel with UMD (used for separated grid stuff with bigger release cycles)
- 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
- every CMD major release will stick to a specific OpenStack release, for instance:
- CMD1->Kilo
- CMD2->Liberty
- CMD3->(Mitaka)
- OTOH the OpenStack version does not really matter to CMD; the OS supported does (for path naming etc)
- CMD1 will support CentOS7 and Ubuntu 14.04 LTS
- all the products must be available both as CentOS7 and Ubuntu packages
- OpenNebula tools can be hosted by CMD, using the latest major release available
- 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
- two or more versions of CMD will be distributed in parallel, following the need of sites to stick with their installations
- after creating the first CMD1 we will use the experience to create a procedure to create the next version of CMD to make it straightforward every 6 months