Architectural Deployment Scenarios to consider:
Management Workloads
Deployment Model | ONAP Central | Edge using certain ONAP management workload functions as an Offload | |
| Description | Architecture Near-term Priority | ||
Edge and Central Provider are same | Yes for all cases |
| Priority - High? Rationale:
Note: Analytics is currently addressed by a Distributed DCAE Orchestrator based on Cloudify. Participant Operator Priority
|
Edge and Central Providers are different | Yes for all cases |
| Priority - High? Rationale - Same as above. Participant Operator Priority
|
Managed Workloads
Deploy-ment Model | ONAP Central | Edge using certain ONAP management workload functions as an Offload | Edge *not* using ONAP Orchestration Clarification Notes: 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. | ||||
| Description | Architecture Near-term Priority for VNFs | Architecture Near-term Priority for Apps | Description | Architecture Near-term Priority for VNF Orchestration | Architecture Near-term Priority for App Orchestration | ||
Edge and Central Provider are same | Yes for all cases |
| Priority - High? Rationale:
Participant Operator Priority
| Priority - Medium? Rationale:
Participant Operator Priority
|
| Priority - Medium? Rationale:
Participant Operator Priority
| Priority - Medium? Rationale:
Participant Operator Priority
|
Edge and Central Providers are different | Yes for all cases | Use Existing VPCs (VPC creation out of scope for ONAP) | Priority - High? Rationale:
Participant Operator Priority
| Priority - Medium? Rationale:
Participant Operator Priority
| Use Existing VPCs (VPC creation out of scope for ONAP) | Priority - Medium? Rationale:
Participant Operator Priority
| Priority - Medium? Rationale:
Participant Operator Priority
|