Versions Compared

Old Version 43

changes.mady.by.user Srinivasa Addepalli

Saved on

compared with

New Version 44

changes.mady.by.user Vijay Venkatesh Kumar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected few typos

...

  • Management Workloads
    • Currently, Multiple Orchestrators for Management Workloads (SDC, SO, OOF etc.). 
      • ONAP Central Management   – OOM
      • Analytics Central/Distributed Management   – DCAE (ONAP, SP internal, Third Party)
    • There is an opportunity to get some alignment across multiple orchestrators which will be greatly beneficial especially in Distributed Edge environment
  • Managed Workloads (SDC, SO, OOF etc)
    • Fully Support for containerized network functions (work in progress)
    • Support for non-network functions (VM and Container based), e.g. vProbe, Automation Apps

...

Deployment Model

Edge using certain ONAP management workload functions as an Offload



DescriptionArchitecture Near-term Priority

Edge and Central Provider are same

  • Allows ONAP Central Controller function to install ONAP SW components (purely ONAP mgmt. based or 3rd party integrated with ONAP mgmt.).
  • This also supports ONAP specific K8S cluster installation.

Priority - ?

Rationale:

  • Analytics and closed loop offloads are key edge use cases.

Note: Analytics is currently addressed by a Distributed DCAE Orchestrator based on Cloudify.

Participant Operator Priority

  • AT&T - High; To distribute Analytics (DCAE DCAE services (Analytics, collectors etc.) and other ONAP components for resiliency.
  • Verizon -
  • Vodafone -

Edge and Central Providers are different

  • Use Existing VPCs (VPC creation out of scope for ONAP)
  • Rest - Same as above.

Same as above.

...