STATUS: Draft
Multi-Cloud:
1 High Level Component Definition and Architecteral 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
MORE functional capabilities?
I was also unsure about the registration interface, whether MC was a provider and consumer there: a provider for triggering the process, a consumer to AAI interface for inventory updates.
I didn't show redfish as its not functionally in dublin (or max a PoC)
2. MultiCloud API definitions
Multi-Cloud provides the following interfaces:
| Interface Name | Interface Definition | Interface Capabilities |
|---|---|---|
| MCE-2 | Cloud FCAPS Interface. Provides the ability to obtain cloud FCAPS data. | What are the main capabilities here - is it VES?? FCAPS data relay to DCAE VES collection |
| MCE-3 | Resource Lifecycle Management Interface Provides a course grain VNF level LCM interface | What are the main capabilities here? Template level workload LCM in a cloud agnostic way |
| MCE-4 | N/A Place holder for SDN interconnect interface | |
| MCE-5 | Atomic Resource LCM Provides a fine graned resource LCM interface at the VM level | What are the main capabilities here (instantiate, ....)? Atomic resource level workload LCM, specific to OpenStack resources. |
| MCE-6 | Placement Optimization Interface Provides real time available capacity information | What are the main capabilities here |
| MCE-7 | Cloud VIM Registration interface Infrastructure resource discovery and registration to AAI | What are the main capabilities |
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 |
|---|---|
| SDCE-6 | To recieve the cloud orchestration artifact from SDC |
| MCE-1 | Consume the services from the cloud provider. It is specific to each cloud type (by plugin approach) |
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:
- Add SDC client to retrieve the workload artifacts from SDC
- Multicloud plugin service for OpenStack StarlingX
- Multicloud plugin service for Lenovo ThinkCloud.
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