| Table of Contents |
|---|
...
- e.g., MEC APIs - Location info, Radio control info etc.
- e.g., Cloud APIs - IaaS/PaaS + Context Awareness (time, places, activity, weather etc.)
Edge Infrastructure
This diverse work load will require somewhat heterogeneous cloud environment, including Graphical Processing Unit, highly programmable network accelerators, etc., in addition to traditional compute, storage, etc.
...
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
ONAP Hierarchy - Multiple Providers
Additional Notes on Gliffy
- Cloud Provider Business Unit: Provides hosting of Workloads, ie., IaaS/PaaS
- SP installs and manages ONAP in separate 'Management Cloud' instances
- SP installs and manages Network Services + 3rd Party Apps in separate 'Services/Apps Cloud' instances
- Cloud Provider Business Unit: Provides SaaS, eg., Analytics/Closed Loop as a Service, LCM of Apps, etc..
- ONAP Edge may not be needed
Sequence Diagram
| Gliffy | ||||
|---|---|---|---|---|
|
...
- Cloud Provider Business Unit:
- Types of virtualized cloud resource tenant and their characteristics
- Virtualized Network Workload Cloud Resource Tenant Category
- Network Management Cloud Resource Tenant Category
- Virtualized Application Workload Cloud Resource Tenant Category
- Application Management Cloud Resource Tenant Category
- Physical Network Tenant Category
- Physical tenant and their characteristics
- Part of Edge Orchestrator
- Types of virtualized cloud resource tenant and their characteristics
- Immediate interest to ONAP for 5G use cases
- Virtualized Network Workload Cloud Resource Tenant Category
- Guaranteed
- Burstable (with minimum guarantee)
- Best Effort
- Network Management Cloud Resource Tenant Category
- Burstable (with minimum guarantee)
- Virtualized Network Workload Cloud Resource Tenant Category
Sequence Diagram
| Gliffy | ||
|---|---|---|
|
...
Edge Application (refer to app classification) / Infrastructure (refer to infra profile summary) Requirement – ONAP Project impact
...
A&AI, Multi-Cloud, Policy, APP-C, VF-C, CLAMP, DCAE, OOF etc.
OOF Enhancements
- Example: Choosing the Cloud Region for deployment of Network Functions (PNF/VNF) based on various constraints
- Leverage Infrastructure Events/Alerts besides Metrics for aggregate objects (Tenant, Cluster etc.) from Edge Cloud
Multi-Cloud Enhancements
...
- Analytics (Infra/App)
- Value: Summarize data in the edge and avoid WAN bandwidth deluge
- Generate appropriate events and alarms
- Edge Infra Analytics
- Cloud
- Edge App Analytics
- VNFs
- Close Loop Use Cases which need only ONAP Central intervention
- VNF Scale in/out - Proactive using app/infra predictive analytics
- Enhanced Alarm Correlation
- Value: Summarize data in the edge and avoid WAN bandwidth deluge
- Closed Loop Use cases which does not need ONAP intervention
- Fault Management
- Cloud provider can automatically recover from VM/Host going unresponsive (e.g. heartbeat mechanism)
- VNF/App vendor can automatically recover from VNF/App going unresponsive (e.g. health check mechanism)
- Fault Management
- ONAP requires IaaS/PaaS attributes from Cloud providers for Infrastructure profiles that allow Distributed, Highly-secure, Config/Cloud-diverse, Capacity-constrained and Peformance/Isolation-aware – Key Features
Resource Reservation (Aggregate/Atomic Objects) for Superior Isolation
High Performance Networking Enablement (Intra-DC DPDK-based Overlay & SR-IOV)
...
Related Use Cases:
- Closed Loop Use Case Link (VoLTE etc.): ONAP Beijing Release Developer Forum, Dec. 11-13, 2017, Santa Clara, CA US
- 5G - Optimization of the Deployed Network Slices (https://wiki.onap.org/ pages/viewpage.action?pageId=28382490)
- 5G - Creation & Management of Network Slices
Related Work:
Notes:
- This assumes Analytics and Fault Management Policies in Clouds and VNFs are independently configured.
- Single pane of glass policy management through ONAP involves managing a multi-vendor distributed policy framework and out of scope for R3.
...
Same as Option A + ONAP Central Project(s) based on Edge DCAE Apps
- OOM Enhancements
- SP uses a central-OOM with a 'policy' for deployment of an onap-edge instance, e.g., xyz edge provider with abc components, etc.
- However, onap-edge instance can be 'lighter weight' with subset of components needed (per MVP discussed below)
- Desirable to managed as a separate K8s cluster (ie., separate from onap-central instance, of course) and, only for onap-edge use, ie., don't use for other 'workloads' like network apps or 3rd party apps
- SP uses a central-OOM with a 'policy' for deployment of an onap-edge instance, e.g., xyz edge provider with abc components, etc.
- Cloudify Enhancements (Lusheng TBD)
...
- ONAP Edge DCAE Microservices
- Support New microservice based Apps – Centralized SON applications, Optimization (SON Drive Test Minimization etc.), ML methodologies for various apps etc.
...
Related Use Cases:
- Edge Automation - Application Profile – Edge Scoping
Notes:
- Choose applications that are independent and which do not impact closed loop operations
ONAP Edge XYZ ↔ ONAP Edge GW ↔ ONAP Central GW ↔ ONAP Central XYZ
...
Same as Option B + ONAP Central Project(s) based on ONAP Edge Closed Loop
CLAMP Enhancements
...
- ONAP Edge Closed Loop
- Edge Policy
- Static/Dynamic Policy - PDP
- Policy may depend on current deployment state and also might need service context for the service component such as VNFs? So, other ONAP components may be involved at the edge?
- Static/Dynamic Policy - PDP
- Edge APP-C, VF-C, Multi-Cloud for Controller Function
- ...
- Edge Policy
...
- ONAP Edge Service Orchestration
- SO for service orchestration
- OOF for homing
- A&AI for inventory
- ...
...
GW Options (one or more options are relevant based on use cases):
- Option 1:
- API GW – HTTPS communication across Gateways
- Session termination of local communication from ONAP instance (DMaaP etc.) and translation to HTTPS session to peer API GW
- Benefit
- Hierarchical and Scalable communication across ONAP Central and ONAP Edge instance and/or Edge Cloud instance microservices (avoid full-mesh communication)
- Option 2:
- Secure IPSEC communication across Gateways, especially for public networks
- No Session termination of local communication from ONAP instances (DMaaP etc.)
- Benefit
- Easy Implementation (full-mesh communication) with High Performance
Need to align table with Edge Infrastructure Profile Summary
...
Support External controllers that take up the load of ONAP (Identify changes i required in ONAP to support external entities that take up the load off of ONAP)
- Site specific or regional level external controller support
- Exteral controllers
- VNF LCM Controllers (that bringup, terminate, heal, migrate, configure, monitor of workloads)
- Fabric Controller (that control/configure L2/L3 switches at the Edge)
- CE and PE controllers (that control WAN connectivity of Edge sites)
- Exteral controllers
- Distribution of ONAP configuration to Edge sites/regional-sites
- Policy configuration (for Closed loop control within the site)
- Policies that help in local optimization (VNF Placement as part of scaling)
- Support for site/region level for analytics and get hold of aggregate data (API and Model support for remote site)
- API suppot for sites/regions to send relevant topoloyg information
- Scaling of ONAP CA (AAF CA or ISTIO CA) to issue Intermediate CA certificates to Edge sites/regional-sties
...
VNF LCM Controller support: SO, APP-C
Fabric and WAN controller support: SDN-C
DIstribution of Policies : POLICY
Regional Site Analytics support: DCAE
Topology support: A&AI
High priority:
...
Medium Priority:
- Regional/Edge level fabric controller
- VNF LCM Controller at regional/edge level.
- Closed loop control at regional/edge level, which requires selective policy synchronization from central ONAP to regional/edges.
- Support for regional/edge level for topology and inventory repository
Low priority:
- CE/PE controllers
...
- Support for SRIOV-NIC (Ability for ONAP to take care of unique requirements of VIMs)
- Support for GPUs and FPGAs (Support on-demand programming. Example: Via Openstack Cyborg)
...
High Priority
- SRIOV NIC support
Medium Priority:
- FPGA support: Stretch as OS & K8S don't have FPGA support yet. Openstack Rocky is going to support Cyborg
...
- Support for containerized workloads (Network functions) using K8S
- Unified networking among VM and Container workloads
...
- AF (Application Functions - 5G Terminology)) / User App LCM Proxy (MEC terminology) support
- APIs for AF registration to ONAP
- APIs to provide NEF Reachability information to external AFs -
- To allow External AFs to reach 5G NFs to create traffic rules in UPFs on the sites where edge applications being brought up.
- To register with the 5G NFs (via NEF) to get hold of contextual information.
- Acting as proxy to reach 5G NFs from AF.
- ONAP to provide more constraints in selecting the best region to place edge application (Cost, Latency, Bandwidth etc...)
...
- Constraints to support VNF placement based on data-placement regulations (such as GDPR)
- Ensuring that secrets and password shared with region-site level external controllers are secured well (Using TPM/SGX)
- ONAP ensuring that site-sepcific controllers/software are not tampered
...
OOF
AAF (Secret Management Service, CA Service)
New project for SW tampering detection and taking actions
...
High Priority :
- VNF placement based on data-placement regulations
Medium Priority:
- Architecture and design of secret/password management with edge sites and Software tampering.
...
ONAP to do centralized VNF image management
- Ability for VNF vendors to provide set of images for their VDUs (One per type of remote site - Openstack based, K8S based, AWS based, Azure based.
- Ability for VNF vendors to provide artifacts specific to remote site specific controls.
- ONAP to manage images to sites (Pro-active basis - PUSH , on-demand basis - PULL)
- Some images to some sites can be pushed on pro-active basis (e.g Hyperclouds) : Push images to sites whenever VNF image is uploaded in ONAP. Also, remove image when the image is removed from the ONAP.
- Some images or some sites may not take too many images (due to persistent memory limitations or cost) and hence support for pulling images. Support for docker hub based image management for K8S based sites and Support for glance API for Openstack based edge sites : As part of instantiation request, letting the remote sites download the image.
...
Currently each site is expected to be registered manually. Need for dynamic registration of edge-site, regional site
ONAP to API to
- Edge/Regional-site registration/De-registration
- In case of regional-sites, edge sites that it controls.
- Site status (reach-ability status, Site capacity, current VNFs, Total number of VNFs brought up so far etc...)
...
|