Brief Project Overview (brief as it should be known)
- MultiCloud project is to adapt ONAP orchestration workflow to different infrastructures providers including but not limited to OpenStack and its different distributions, public and private clouds, and COE (Container Orchestration Engine, e.g. kubernetes), CDI (composible Disaggregate Infrastructures), etc. by providing a mediation layer between ONAP and underlying infrastructures.
- It enables the discovery and registration of infrastructure resource information into ONAP to support optimized homing and placement.
- It relays FCAPS from infrastructure to ONAP as part of control loop .
New component capabilities for Frankfurt, i.e. the functional enhancements.
- N/A
New or modified interfaces
- N/A
If they are modified, are the backwards compatible?
Yes
Interface naming (point to an example)
- POST /api/multicloud/v1/capacity_check ( https://gerrit.onap.org/r/#/c/78634/5/docs/specs/multicloud_resource_capacity_check.rst )
- POST /api/multicloud/v1/{cloud-owner}/{cloud-region-id}/infra_workload (https://gerrit.onap.org/r/#/c/75851/6/docs/specs/multicloud_infra_workload.rst )
- POST /api/multicloud/v1/{cloud-owner}/{cloud-region-id}/infra_workload/{workload-id} (Proposal for generic AAI Workload Update (aka heatbridge))
Reference to the interfaces.
The New and Modified API will be updated here: https://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html
What are the system limits?
N/A
Involved use cases, architectural capabilities or functional requirements.
- CCVPN
- vFW/vDNS
- vCPE
Listing of new or impacted models used by the project (for information only).
N/A
ARC Multi-Cloud Component Description - Dublin
...