Page Status: Copied from R6 - Mar, 22, 2020
Component Status: Pending PTL Updates and ArchCom Review
...
MC Multi-Cloud:
...
High Level Component Definition and Architectural Relationships
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| 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 |
| AAIE-1 | Consume the services from AAI to access infrastructure resource inventory |
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:
...
draw.io Diagram border true viewerToolbar true fitWindow false diagramName CLAMP runtime architectrue simpleViewer false width diagramWidth 821 revision 1
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
...