Page Status: Updated for Istanbul -
Component Status: Pending PTL updates and ArchCom Review
Last Reviewed on:
Certified by:
MC Multi-Cloud:
High Level Component Definition and Architectural Relationships
The multi-cloud function provides mediation capabilities to connect to different infrastructure providers.
- Adapt ONAP to VM based infrastructure such as openstack,Azure
- Adapt ONAP to Container Orchestration Engine, such as K8S
- Discovery and registration of resource information.
- Relay FCAPS data from infrastructure to DCAE
2. MultiCloud API definitions
Multi-Cloud provides the following interfaces:
Interface Name | Interface Definition | Interface Capabilities | API Spec (Swagger) |
---|---|---|---|
MCE-2 | Resource Lifecycle Management Interface Provides a course grain VNF level LCM interface in a template driven and cloud agnostic way | Provides:
| https://docs.onap.org/projects/onap-multicloud-framework/en/latest/MultiCloud-APIv1-Specification.html |
MCE-3 | N/A Place holder for SDN interconnect interface | Envisaged Future Capability | |
MCE-4 | Atomic Resource LCM Provides a fine graned resource LCM interface at the VM level. This is an atomic resource level workload LCM (specific to openstack resources) | Provides:
| https://docs.onap.org/projects/onap-multicloud-framework/en/latest/MultiCloud-APIv1-Specification.html |
MCE-5 | Placement Optimization Interface Provides real time available capacity information | Provides:
| https://docs.onap.org/projects/onap-multicloud-framework/en/latest/MultiCloud-APIv1-Specification.html |
MCE-6 | Cloud VIM Registration interface Expose Interface to trigger MultiCloud plugin to discover the infrastructure resource and register them to AAI | Provides:
| https://docs.onap.org/projects/onap-multicloud-framework/en/latest/MultiCloud-APIv1-Specification.html |
MCE-7 | CNF Lifecycle Management Interface Provides a course grain CNF level LCM interface for k8s workloads based on helm resource templating format. The interface differs from MCE-2 because of the different modeling applied for CNFs in comparison to VNFs - RB (Resource Bundle) concept which represents helm package encapsulation. | Provides:
| MultiCloud K8s-Plugin-service API |
Note: xxxI interface is a Component internal interface. xxxxE interface is a component external interface
The current API documents can be found at: https://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html
MultiCloud consumes the following Interfaces:
Interface Name | Purpose Reason For Use | API Spec (Swagger) |
---|---|---|
SDCE-6 | To receive the cloud orchestration artifact from SDC | SDC API |
MCE-1 | Consume the services from the cloud provider. It is specific to each cloud type (by plugin approach) | https://docs.openstack.org/pike/api/ |
DCAEE-X | Supply Virtual Infrastructure FCAPS Events to DCAE | https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/apis/ves.html |
AAIE-1 | Consume the services from AAI to access infrastructure resource inventory | https://docs.onap.org/projects/onap-aai-aai-common/en/latest/platform/offeredapis.html |
3. Component Description:
A more detailed figure and description of the component.
<< For later inclusion >>
4. known system limitations
Runtime: to be filled in
5. Used Models
Multi-Cloud uses the following models:
- please fill in (and references if possible)
- << include model that you recieve from SDC >>
- << Include the model that you configure in the policy >>
6. System Deployment Architecture
Multicloud consists of X containers:
- Do you have a figure here that?
7. New Capabilities in this Release
This release, Multi-Cloud adds the following Capabilities:
- Enhance MultiCloud k8s to support CNF orchestration
8. References
- Multicloud interface specification: https://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html
- MultiCloud Architecture: https://docs.onap.org/en/casablanca/submodules/multicloud/framework.git/docs/MultiCloud-Architecture.html