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 Dublin, i.e. the functional enhancements.

  • Add SDC client to retrieve of workload artifacts from SDC
  • MultiCloud Plugin service for OpenStack StarlingX
  • MultiCloud Plugin service for Lenovo ThinkCloud

New or modified interfaces

  • Updates infra_workload API (backward compatible) to allow SO orchestrate k8s workload and azure workload
  • Update capacity_check API (backward compatible) to report capacity information on Available Zone level in favor of F-GPS requirement.
  • New API to update instantiated workload into AAI: POST /infra_workload/{workload_id}

If they are modified, are the backwards compatible?

Yes

Interface naming (point to an example)


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.

Listing of new or impacted models used by the project (for information only).

N/A


ARC Multi-Cloud Component Description - Dublin


  • No labels