Versions Compared

Old Version 22

changes.mady.by.user ramki krishnan

Saved on

compared with

New Version 23

changes.mady.by.user ramki krishnan

Saved on

Key

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

...

ONAP ComponentLife Cycle PhaseEnhancements
PolicyDesign

Define Distributed Cloud Infrastructure Placement Policies (Note 3)

  • Leverage Standardized Distributed Cloud Infrastructure Object Hierarchy & Capabilities from A&AI
Multi-CloudDeploy

Support Distributed Cloud Infrastructure Capability Discovery (Note 1, Note 2)

For workload instantiation, SO ↔ MC IaaS intent-based workload instantiation API to support cloud agnostic intent for Compute/Network/Storage; MC to translate cloud-agnostic intent from SO into cloud-specific placement attributes (Note 7)

A&AIDeploy

Support Standardized Distributed Cloud Infrastructure Object Hierarchy & Capability Database

  • 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
OOFDeployExecute Distributed Cloud Infrastructure Placement Policies for Optimized Service/VNF Placement across Cloud Regions (Note 4)
SODeployExtend SO↔OOF SO ↔ OOF API to support cloud agnostic intent (Note 5)

...

ONAP ComponentLife Cycle PhaseEnhancements
PolicyDesign

Define Distributed Cloud Infrastructure Network Intent Per Cloud Region (Note 1)

  • Leverage Standardized Distributed Cloud Infrastructure Object Hierarchy & Capabilities from A&AI
Multi-Cloud (MC)Deploy

MC <-> Private/Public SDN-DC (Private Cloud) or MC <-> Public Cloud – per cloud region interaction

  • Translate Cloud Agnostic intent to Cloud specific intent or imperative APIs by querying Policy
  • Return network endpoint (used for VNF placement)
SODeploy

Option 1: (SO -> MC -> Private/Public SDN-DC) -- desired

  • SO <-> MC IaaS Intent-based intra-dc network instantiation API (BesidesOne or more of Besides Network, also support Compute/Network/Storage/AnalyticsStorage as described in the previous section)

Option 2: (SO -> SDN-C -> MC → -> Private/Public SDN-DC)

  • SO <-> SDN-C interaction
    • SO uses the Generic Resource API (SDN-C NB) to SDN-C to determine the right Directed Graph to invoke
    • The Generic Resource API can be used to pass the cloud region and other cloud agnostic intent
  • SDN-C <-> MC IaaS Intent-based intra-dc network instantiation API
    • By looking up the directed graph, SDN-C calls MC with a programmable intent-based API which includes cloud region and other cloud agnostic intent

...