Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary: Edge Scoping 

Distributed Edge Cloud Infrastructure Object Hierarchy (Stretch Goal)

Value:

  • Fine grained resource management & analytics for Distributed Edge Clouds

...


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyMULTICLOUD-153


ONAP ComponentLife Cycle PhaseEnhancements
PolicyDesign

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-CloudDeploy

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&AIDeploy

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
OOFDeploy

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 Mechanism

SODeploy

Extend SO ↔ OOF API to support cloud agnostic intent (Note 5)

Extend SO ↔ MC API to support cloud agnostic intent (Note 6)

...

Gliffy Diagram
size1200
nameCloud Agnostic Intent Execution Workflow
pagePin27

...



...

Cloud

...

Cloud Resource Partitioning for Differentiated QoS (Combined with previous)

...

  • Edge Infrastructure Analytics complementing 5G VNF Analytics

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyMULTICLOUD-254

ONAP, as in R2, collects the statistics/alarms/events from workloads (VMs) and take any close loop control actions such as Heal a process, scale-out, restart etc.. In R3, infrastructure related statistics/alarms/events will be collected, generate actionable insights and take life cycle actions on the workloads.  Infrastructure statistics normally include performance counters, NIC counters, IPMI information on per physical server node basis.  To reduce the load on the ONAP, it is necessary that aggregated (summarized) information is sent to the ONAP from edge-clouds. 

...