Versions Compared

Key

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

...

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 etc.) and other ONAP components for resiliency.
  • Verizon -
  • Vodafone - ?
  • Reliance Jio - ?

Edge and Central Providers are different

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

Priority - High?

Rationale - Same as above.

Participant Operator Priority

  • AT&T - ?
  • Verizon - ?
  • Vodafone - ?
  • Reliance Jio - ?

    Managed Workloads

    • Managed workload instantiation is always started by ONAP Central components 
      • If "Edge using certain ONAP management workload functions as an Offload" as described in the previous table, the corresponding workload LCM functions will be taken care of by offloaded ONAP management components 

    ...