...
Every week as part of Edge Automation WG – Edge Automation through ONAP
Status:
Draft.
Plan to be finalized in Arch. sub committee meeting on 01/15/2018.
References:
- ONAP Dublin Architecture Requirements: https://wiki.lfnetworking.org/display/LN/OPNFV-ONAP+January+2019+Session+Proposals?preview=/8257582/10551784/2019-01%20Dublin%20Architecture%20Requirements-pa1.pptx
- DCAE Platform Requirements: https://wiki.onap.org/download/attachments/28379482/DCAE%20Platform%20Requirements.pptx?api=v2
...
- Leverage existing capabilities, and select what; or motivate new approaches
- Management Workload:
- Align on a single orchestrator solution for all management workloads
- Managed Workload:
- Enhance SDC, SO, A&AI, MC etc. to support containerized functions
- Leverage ONAP for deploying and managing non-network functions
- Longer-term:
- Explore feasibility for orchestration alignment between managed workload and management workload
- Cloud-Native-foundation:
- Leverage K8S (Operators, Custom Resource Definitions etc.) for Distributed Systems Management
- Image management – at scale rolling upgrade
Policy/Configuration change – notify only deltas
- Leverage Istio Service Mesh (Distributed Tracing etc.) for Component Performance Management
- Leverage K8S (Operators, Custom Resource Definitions etc.) for Distributed Systems Management
Architectural Deployment Scenarios to consider:
Management Workloads
Deployment Model | Edge using certain ONAP management workload functions as an Offload | |
| Description | Architecture Near-term Priority | |
Edge and Central Provider are same |
| Priority - ? Rationale:
Note: Analytics is currently addressed by a Distributed DCAE Orchestrator based on Cloudify. Participant Operator Priority
|
Edge and Central Providers are different |
| Priority - High? Rationale - Same as above. Participant Operator Priority
|
Managed Workloads
- Managed workload instantiation is always started by ONAP Central components
- If "Edge using certain ONAP management workload functions as an Offload" as described in the previous table, the corresponding workload LCM functions will be taken care of by offloaded ONAP management components
- If "Edge using certain ONAP management workload functions as an Offload" as described in the previous table, the corresponding workload LCM functions will be taken care of by offloaded ONAP management components
No change is envisioned in the workload instantiation from a ONAP user perspective.
Distributed Management application Requirements / Considerations
...
| Item | Added by | Modified by | |
|---|---|---|---|
| ONAP Management components can only be brought up in cloud-regions that are based on Kubernetes |
Architectural Deployment Scenarios to consider:
Outcome of Edge Automation Discussions on 01/16/2019:
Deploy-ment Model
Non-ONAP Central
ONAP Central
Edge using certain ONAP management workload functions as an Offload
Clarification Notes:
In this case, their is no hierarchical orchestration.
Edge using ONAP Orchestration
Clarification Notes:
In this case, their is a two (or more) level orchestration hierarchy when ONAP Central is interfacing with ONAP Edge Orchestrator.
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.
Edge and Central Provider are same
NA
Yes for all cases
- Allows ONAP Central Controller function to install 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 Controller 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
Priority - Medium?
Rationale:
- ONAP's primary focus is NFV Orch.
Participant Operator Priority
- AT&T - ?
- Reliance Jio - ?
- Verizon - ?
- Vodafone - ?
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)
- 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 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
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).
...