/
Regional Edge Orchestrator support
Regional Edge Orchestrator support
Purpose:
Thin edges can be headless. A regional controller, in this case, can be edge controller for many edge sites. ONAP communicates with a regional controller for a set of edges.
At this time, each site is registered with ONAP. Each edge has its own control and same is reflected in ONAP.
With one regional controller supporting multiple edge locations, ONAP should ensure that it can talk to regional controller on behalf of edges.
Based on ESR and A&AI capabilities we see in R2, we believe that regional controllers can be supported, but we need to verify.
As part of this effort, intention is create edge orchestrator using K8S and verify that multiple headless edges can be used to deploy VNFs using central K8S orchestrator.
, multiple selections available,
Related content
Edge Automation through ONAP
Edge Automation through ONAP
More like this
Edge Automation through ONAP Arch. Task Force - Distributed Management (ONAP etc.) components
Edge Automation through ONAP Arch. Task Force - Distributed Management (ONAP etc.) components
More like this
Edge Sub-committee creation proposal
Edge Sub-committee creation proposal
More like this
Use Case Realization Call: May 22, 2019
Use Case Realization Call: May 22, 2019
More like this
K8S based Cloud region support (Continue from R4)
K8S based Cloud region support (Continue from R4)
More like this
Support for K8S (Kubernetes) based Cloud regions
Support for K8S (Kubernetes) based Cloud regions
More like this