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.
Fedcloud-tf:CMF Differences
Jump to navigation
Jump to search
Differences in CMF-side Capabilities and Implementations
This is work in progress, a page that should catalogue differences between different cloud management frameworks used in FedCloud with respect to the implementation of features through OCCI.
| Feature / Problem | OpenNebula / rOCCI specifics | OpenStack / OOI specifics | Synnefo specifics | AWS / rOCCI specifics |
|---|---|---|---|---|
| Selecting default network: connecting Compute resources to networks on creation in case no Network Link is specified. | In case just one Network is applicable, OOI picks it and creates the link. Otherwise a link must be specified. | |||
| Treatment of the PUBLIC Network | PUBLIC Network does not actually exist in OpenStack. There is a plan to create it automagically on request when creating Compute resources that want to link with it. | |||
| Inline links (NetworkInterface): The creation of links to Network resources inline with the creation of a Compute instance. Different CMFs behave differently if there are more | ||||
| Linking existing resources (NetworkInterface): linking Compute and Network instances during their lifetime. | Not supported by AWS at all. Linking is only possible on VM creation. |