Page History

Deploy-ment Model

Non-ONAP Central

ONAP Central

Edge using certain ONAP functions as an Offload

Note: In this case, ONAP central is interfacing with edge directly using Multi-Cloud APIs for workload deployment.

Edge using ONAP Orchestration

Note: In this case, their is a two (or more) level orchestration hierarchy when ONAP Central is interfacing with ONAP Edge Orchestrator using SO style APIs for workload deployment.

Edge *not* using ONAP 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 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 (purely ONAP mgmt. based or 3rd party integrated with ONAP mgmt.). Note that this also supports ONAP specific K8S cluster installation.
• Support ONAP managed workloads on edge

Priority - High?

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 - ?
• Reliance Jio - ?
• Verizon - ?
• Vodafone - ?

Priority - Medium?

Rationale:

• ONAP's primary focus is NFV Orch.

Participant Operator Priority

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

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

• ONAP edge orchestrator should be  registered in ONAP central with the service specific capabilities it can offer. This step should happen before service instantiation.Can install ONAP SW components via other mechanisms
  
  
  

Priority - Medium?

Rationale:

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

Rationale:

• 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

Priority - High?

Rationale:

• Same as above.

Participant Operator Priority

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

Priority - Medium?

Rationale:

• 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 ONAP Edge Orchestration SW (incl K8S cluster)
• Support ONAP managed workloads on edge
• Can use Edge provider Services

Priority - Medium?

Rationale:

• Same as above.

Participant Operator Priority

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

Priority - Medium?

Rationale:

• Same as above.

Participant Operator Priority

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

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

• Can install ONAP SW components via other mechanismsONAP edge orchestrator should be  registered in ONAP central with the service specific capabilities it can offer. This step should happen before service instantiation.
• Can use Edge provider Services

Priority - Medium?

Rationale:

• Same as above.

Participant Operator Priority

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

Priority - Medium?

Rationale:

• Same as above.

Participant Operator Priority

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