Page History

...

ONAP Component	Life Cycle Phase	Enhancements
Policy	Design	Define Distributed Cloud Infrastructure Service Placement Policies (Note 3) – No enhancement needed to Policy Framework Leverage Standardized Distributed Cloud Infrastructure Object Hierarchy & Capabilities from A&AI
Multi-Cloud	Deploy	Support Distributed Cloud Infrastructure Capability Discovery (Note 1, Note 2) IaaS intent-based framework to support cloud agnostic intent for Compute/Network/Storage Note 7 "Example" Note 8 "Execution Workflow" MC <-> Private/Public SDN-DC per Cloud region (Networking Workflow, Ref. 2)
A&AI	Deploy	Support Standardized Distributed Cloud Infrastructure Object Hierarchy & Capability Database (Ref. 1) Loose coupling between HW objects (private cloud) and SW objects (private and public clouds) Includes Standardized Capabilities across clouds & Capabilities unique to certain clouds Note: Multi-Cloud Distributed Cloud Infrastructure Capability Discovery process will populate the aforementioned database
OOF	Deploy	Execute Distributed Cloud Infrastructure Placement Policies for Optimized Service/VNF Placement across Cloud Regions (Note 4) OOF ↔ MC Runtime Check API (Note 8 "Execution Workflow") Resource Reservation Mechanism3, Note 4)
SO	Deploy	Extend SO ↔ OOF API to support cloud agnostic intent data opaque to SO (Note 5) Extend SO ↔ MC API to support cloud agnostic intent data opaque to SO (Note 6)

Assumption for Policy, SO, OOF:

...

For the 5G Service/VNF placement example in Note 3
- OOF will pass the Physical DC End Point to SO as a cloud agnostic intentopaque data

Note 6:

For the 5G Service/VNF placement example in Note 3
- SO passes the Physical DC End Point to Multi-Cloud as a cloud agnostic intentopaque data, besides the Cloud Region

...

ONAP Component	Life Cycle Phase	Enhancements
Policy	Design	Configuration Policies for Guaranteed, Burstable & Best Effort Cloud Infrastructure Resource Slices (this will apply to VMs/Containers also) Placement Policies for Resource Slices Higher (programmable) weight to Cloud Region which supports all three types of resource slices vs only two types of resource slices (Guaranteed/Best Effort)
Multi-Cloud	Deploy	Resource Slice Capability Discovery
A&AI	Deploy	Resource Slice Capability per Cloud Region Guaranteed/Burstable/Best Effort Resource Slice Type Guaranteed/Burstable/Best Effort
OOF	Deploy	Execute Resource Slice Placement Policies for Optimized Service/VNF Placement across Cloud Regions

Aggregated Infrastructure Telemetry Streams (Casablanca MVP - Infrastructure Telemetry Aggregation as part of ONAP Central Multi-Cloud)

Value

...

ONAP Component	Life cycle phase	Activities
AAI and ESR	Deploy & Run time	Add/Modify/Delete recording and alerting rules
AAI and ESR	Run time	Add/Modify/Delete Edge-cloud information
Multi-Cloud	Run time	Get Edge information from A&AI whenever Edge-Cloud is added or removed. Prepare to wait for information from that Edge-cloud Receive information from edge-cloud and put it in the time series DB. Summation based on recording & alerting rules Export information to DCAE via DMAPP or VES

...

Value

ONAP Component	Life cycle phase	Enhancements
OOM - ONAP Central	Deploy	Separate ONAP-edge Instance per 'edge domain', (ie., separate from onap-central instance, of course) Note: Independent of any Edge CP's Orchestration components. SP uses a central-OOM with a 'policy' for deployment of an onap-edge instance, e.g., xyz edge provider with abc components, etc. However, onap-edge instance can be 'lighter weight' with subset of components needed (per MVP discussed below) Desirable to managed as a separate K8s cluster (ie., separate from onap-central instance, of course) and, only for onap-edge use, ie., don't use for other 'workloads' like network apps or 3rd party apps Central OOM to deploy the following ONAP edge instance DMaaP with mirror capability

...

Jira

...