Versions Compared

Old Version 28

changes.mady.by.user ramki krishnan

Saved on

compared with

New Version 29

changes.mady.by.user ramki krishnan

Saved on

Key

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

...

ItemAdded byModified by
ONAP Management components can only be brought up in cloud-regions that are based on Kubernetes

Srinivasa Addepalli








Architectural Deployment Scenarios to consider:

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 VNF Orchestration/

certain ONAP functions as an Offload

Note: ONAP central could is interfacing with edge directly using Multi-Cloud APIs

Edge using ONAP

Architecture Near-term Priority for App

Orchestration

Note: This

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

covers the case where is a two (or more) level orchestration hierarchy when ONAP Central is interfacing with ONAP Edge Orchestrator using SO style APIs

Edge *not* using ONAP Orchestration/

Architecture Near-term Priority for VNF Orchestration/

Architecture Near-term Priority for App Orchestration

Note: This assumes at least a two level hierarchy for orchestration - ONAP Central Orchestrator and 3rd party Edge Orchestrator. This is specific to Service (VNF/App) Orchestration and *not* Cloud infrastructure orchestration. Interfacing to cloud infrastructure Orchestrators is already covered through ONAP multi-cloud.




DescriptionArchitecture Near-term Priority for VNFsArchitecture Near-term Priority for AppsDescriptionArchitecture Near-term Priority for VNF OrchestrationArchitecture Near-term Priority for App OrchestrationDescriptionArchitecture Near-term Priority for VNF OrchestrationArchitecture Near-term Priority for App Orchestration

Edge and Central Provider are same

NA

Yes for all cases

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

Priority - High?

Rationale:

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


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

Participant Operator Priority

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

Priority - Medium?

Rationale:

  • ONAP's primary focus is NFV Orch.
  • Allows ONAP Central to install ONAP Edge Orchestration SW (incl K8S cluster)
  • Support ONAP managed workloads on edge

Priority - Medium?

Rationale:

  • ONAP Edge Orchestration provides scalability which is a long-term use case


Participant Operator Priority

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

Priority - Medium?

Rationale:

  • 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








Priority - 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 - ?

Priority - 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 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 - ?

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 - ?

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 - ?

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). 

...