Versions Compared

Old Version 18

changes.mady.by.user Xin Miao

Saved on

compared with

New Version 19

changes.mady.by.user ramki krishnan

Saved on

Key

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

...

ramki krishnan , Srinivasa Addepalli, Vimal Begwani, Mike Elliott, Vijay Venkatesh Kumar , Avi Chapnick , Borislav Glozman , Fernando Oliveira , Tal Liron , Margaret Chiosi , ravi rao , Raghu Ranganathan , Michael O'Brien , Xin Miao , Simone Mangiante <simone.mangiante@vodafone.com>

Others – please add yourself if you are interested

...

Outcome of Edge Automation Discussions on 01/16/2019:

Deployment Model

Non-ONAP Central

ONAP Central

Edge using ONAP Orchestration/Architecture Near-term Priority for NFV Orchestration/Architecture Near-term Priority for App Orchestration

Note: This does not assume any orchestration hierarchy – ONAP central could be orchestrating edge directly

Edge using

non-ONAP

ONAP Orchestration/Architecture Near-term Priority for NFV Orchestration/Architecture Near-term Priority for App Orchestration

Note: This assumes at least a two level hierarchy for orchestration - ONAP Central Orchestrator and Edge Orchestrator

Edge and Central Provider are same

NA

Yes for all

combinations of edge

cases

  • Allows ONAP Central to install their ONAP SW components (incl K8S cluster)
  • Support ONAP managed workloads on edge

High?

  • Analytics/closed loop offloads (purely ONAP-management-based
,
  • or 3rd party integrated with ONAP management
or ONAP managed workload) is a key edge use case
  • ) are key edge use cases


Participant Operator Priority

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

Medium?

  • ONAP's primary focus is NFV Orch.







Participant Operator Priority

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


  • Can install ONAP SW components (incl K8S cluster) via other mechanisms








Medium?

  • This is more of a standardization exercise given that different NFV orchestrators typically have different APIs




Participant Operator Priority

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

Medium?

  • ONAP's primary focus is NFV Orch.
  • This is more of a standardization exercise given that different NFV orchestrators typically have different APIs


Participant Operator Priority

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

Edge and Central Providers are different

NA

Yes for all

combinations of edge

cases

Use Existing VPCs (VPC creation out of scope for ONAP)

  • Allows ONAP Central to install their ONAP SW (incl K8S cluster)
  • Support ONAP managed workloads on edge
  • Can use Edge provider Services

Same as above.


Participant Operator Priority

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

Same as above.


Participant Operator Priority

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

High?

Analytics (purely ONAP-management-based, 3rd party integrated with ONAP management or ONAP managed workload) is a key edge use case

Use Existing VPCs (VPC creation out of scope for ONAP)

  • Can install their ONAP SW via other mechanisms
  • Can use Edge provider Services




Same as above.


Participant Operator Priority

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

Same as above.


Participant Operator Priority

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

Medium?

This is more of a standardization exercise given that different NFV orchestrators typically have different APIs

Definition of done:

  • This activity is closed when there is a:
    • Description of alternative concepts for distributing the ONAP functionality.
    • A recommendation for which alternatives to pursue (and when). 

...