Edge Automation through ONAP




Overview

Edge clouds are located at close proximity to end users. Typical deployment locations are within the access networks or at the boundary of access networks. In some deployments, they can be within the customer premises (e.g., home; enterprise; factory floor; vehicles including trains, planes, private cars). The core thrusts of edge clouds for applications are low latency, high bandwidth, and trusted computing and storage. Various edge cloud architectures have already emerged from different communities and potentially can be plugged into the ONAP architecture for service orchestration. The group analyzes the orchestration requirements of services over various edge clouds and how these requirements impact ONAP components in terms of data collection, processing, policy management, resource management, control loop models, security, as well as application & network function deployment and control.

ONAPARC-63 - Getting issue details... STATUS

Problem Statement : Edge Architecture & Work Items

  • Edge Cloud Domain = collection of Edge Cloud Nodes in a Domain
  • Where/What is Edge

Key Presentations:

Key ONAP Project Impact:

Dublin Plan:

Frankfurt Plan:

Architecture Task Force - Edge Automation through ONAP Arch. Task Force - Distributed Management (ONAP etc.) components

Call Schedule:

List Subscription/Meeting Notification:

WG Coordinators:  Ramki Krishnan




Contributions

  File Modified

PDF File MEC_Apps_ONS2018_Rev1.1.pdf

Apr 01, 2018 by Prakash Ramchandran

Microsoft Word Document Edge Scoping-r3.docx

Apr 05, 2018 by buyukkoc