Versions Compared

Key

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

...

References: https://wiki.onap.org/download/attachments/28379482/ONAP-mc-sdn-v2.pptx?api=v2https://wiki.onap.org/download/attachments/11928197/ONAP-mc-sdn.pdf?version=1&modificationDate=1506518708000&api=v2

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 – 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 (Besides Network, also support Compute/Storage as described in the previous section
)

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

SO <-> SDN-C interactionSO 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 APIBy looking up the directed graph, SDN-C calls MC with a programmable intent-based API which includes cloud region and other cloud agnostic intent


    Note 1:

    • Cloud Agnostic Intent-based API example 1
      • Intent: High Performance intra-DC data plane networking with no Host CPU usage
      • Realization Possibilities
        • Overlay in SmartNIC
        • Gateway in SmartNIC
        • Overlay in ToR
        • Gateway in a ToR
        • Gateway in a HW appliance
      • Realizations which are fixed
        • Underlay maps to ToR/Network Fabric
        • No CPU usage for data plane networking maps to VMs/Containers with SR-IOV support
    • Cloud Agnostic Intent-based API example 2
      • Intent: High Performance intra-DC data plane networking
      • Realization Possibilities
        • Overlay in DPDK-based switch/router
        • Gateway in DPDK-based switch/router
        • Overlay in ToR
        • Gateway in ToR
        • Gateway in a HW appliance
      • Realizations which are fixed
        • Underlay maps to ToR/Network Fabric
        • HW-assisted data plane maps to VMs/Containers with SR-IOV support 

    Cloud Infrastructure Impact

    ...

    – Resource Partitioning 

    Edge Automation Requirement:

    ...

    ONAP ComponentLife Cycle PhaseEnhancements
    PolicyDesign

    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)

    Network Slice Allocation across several Clouds

    • Allocate a contiguous network slice for extreme mobile broadband (ref. 1) with a max. latency of 10ms
      • Maps to Burstable Resource Slice in the infrastructure with min./max. of CPU, Memory etc.
    Multi-CloudDeployResource Slice Capability Discovery
    A&AIDeploy

    Resource Slice Capability per Cloud Region

    • Guaranteed/Burstable/Best Effort

    Resource Slice Type

    • Guaranteed/Burstable/Best Effort
    OOFDeploy

    Execute Resource Slice Placement Policies for Optimized Service/VNF Placement across Cloud Regions

    ...


    Aggregated Telemetry Streams

    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. 

    ...