...
- 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.
...
Few examples: on scaling - OOM based scaling may not be good enough and there may be a need to offload some ONAP functionality to regional level as the target number of edge clouds could be in tens of thousands. Also, to reduce amount of data to central ONAP services for analytics, there is a need for offloading DCAE functions to regional level, which could involve identifying real time data sources, collecting and analyzing the data and disseminating output data to central ONAP function. Controlling fabric (L2/L3 switches in edge-clouds and WAN links) is another function that may require offloading some ONAP SDNC functions to regional sites.
Example Service
...
Models
Note - arch gliffy to be updated after tweaking this example service model
Edge from internal Business Unit
| Panel |
|---|
| borderColor | red |
|---|
| borderStyle | solid |
|---|
|
| Gliffy |
|---|
| |
|---|
| size | 600 |
|---|
| name | Internal Edge - Service Model |
|---|
| pagePin | 1 |
|---|
|
|
Edge from Partner
| Panel |
|---|
| borderColor | red |
|---|
| borderStyle | solid |
|---|
|
| Gliffy |
|---|
| |
|---|
| size | 600 |
|---|
| name | Edge Automation - Service Model |
|---|
| pagePin |
|---|
|
|
...
ONAP Hierarchical (Central/Edge) Architecture
| Gliffy |
|---|
| |
|---|
| size | 600 |
|---|
| name | Edge Automation - hierarchy |
|---|
| pagePin | 11 |
|---|
|
...