...
| Drawio | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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 | Resource Lifecycle Management Interface Provides a course grain VNF level LCM interface in a template driven and cloud agnostic way | Provides:
|
| 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:
|
| MCE-5 | Placement Optimization Interface Provides real time available capacity information | Provides:
|
| MCE-6 | Cloud VIM Registration interface Expose Interface to trigger MultiCloud plugin to discover the infrastructure resource and register them to AAI | Provides:
|
...
| Interface Name | Purpose Reason For Use |
|---|---|
| SDCE-6 | To receive 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) |
| DCAEE-X | Supply Virtual Infrastructure FCAPS Events to DCAE |
| AAIAAIE-X1 | Consume the services from AAI to access infrastructure resource inventory |
...