Difference between revisions of "EGI Cloud Middleware Distribution products"
Jump to navigation
Jump to search
Line 11: | Line 11: | ||
= CMD products = | = CMD products = | ||
{| align="left" cellspacing="1" cellpadding="1" border="1" class="wikitable sortable" | |||
|- | |||
! scope="col" | Name | |||
! scope="col" | Technology Provider | |||
! scope="col" | Supported framework | |||
! scope="col" | Operating Systems | |||
! scope="col" | Release channels | |||
! scope="col" | Documentation | |||
! scope="col" | Verification procedure | |||
! scope="col" | Early Adopters | |||
! scope="col" | Support Calendar | |||
! scope="col" | Last update for information | |||
|- | |||
|} |
Revision as of 13:34, 23 May 2016
What is needed from Technology Providers (TP) to release in CMD is:
- Last update of the information (this is needed to check how fresh the information are)
- Support calendar for the major releases currently supported (i.e. end of support, end of security support...)
- Preferred release channels (repository? AppDB?) with clear endpoints
- which cloud frameworks (OpenStack/OpenNebula/Synnefo) are supported
- which operating systems supported
- documentation about the installation, configuration
- puppet/ansible profiles or scripts or any kind of automated configuration profile available for verification
- a list of possible Early Adopters to contact to handle the Staged Rollout phase for each product
CMD products
Name | Technology Provider | Supported framework | Operating Systems | Release channels | Documentation | Verification procedure | Early Adopters | Support Calendar | Last update for information |
---|