Page History

Deployment Model

Non-ONAP Central

ONAP Central

Edge using ONAP Orchestration/

Architecture Near-term Priority for NFV VNF Orchestration/

Architecture Near-term Priority for App Orchestration

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

Edge *not* using ONAP Orchestration/

Architecture Near-term Priority for NFV VNF 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. 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.

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

High?

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

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

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