You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 54 Next »



Overview/Scope

This group will address the needs of an edge automation environment to satisfy following 

  • Providing contextual information to application services after gathering information from 5G network functions.
  • Traffic  steering to the right edge applications (e.g  Programming UE classifier of UPF)
  • Scaling needs 
  • Securing confidential information/keys/secrets and detecting any software tampering.
  • Optimal placing of edge applications. For example placing edge applications in close proximity of end users.
  • Supporting various application types (VMs and containers)
  • Performance determinism and high throughput edge 
  • Deploying IOT specific infrastructure software in edges.

This group will study the needs of edges,  identify ONAP role,  identify gaps in ONAP to satisfy above needs and propose solutions to address the gaps.

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. 


ONAPARC-63 - Getting issue details... STATUS

Problem Statement:

Initial Draft: Cagatay/Vimal/Kaniz drafted the following, waiting your input.

Edge Scoping-r3.docx

To Do:

  • Problem Statement - Clarify Where/What is Edge...and, focus of this effort
  • Identify Target Communities
  • Requirements for ONAP R2+

Call Schedule


Contributions (drag-and-drop to this page)

  File Modified
No files shared here yet.

Links to Other ONAP work related to "Edge"

Distributed Multi-vendor Cloud Enablement in ONAP (In progress) - context of  "Edge Realization" from a multi-vendor Cloud Infrastructure perspective

OpenSource Access Manager - context of "Edge Orchestration" for Fixed Access

Use case proposal: 5G- RAN deployment, Slicing, SON - context of "Edge Compute" for hosting CU function



Participants:

Coordinators: Raghu/Ramki

NameCompanyonap-usecasesub@
ramki krishnan
VMwareyes

Paul-André Raymond

B.Yond
Raghu Ranganathan
Cienayes
Vimal Begwani
AT&T

Srinivasa Addepalli

IntelYes
Seshu Kumar Mudiganti
Huawei
Vara Prasad Talari
Nokia
Cagatay BuyukkocAT&T
Alexander Vul
Intel

Ulas Kozat

Huawei
Gil HellmannWind River
Lyndon OngCiena

Rittwik Jana

AT&T
Ramu
Nokia
John Quilty
Ericsson
Karpura Suryadevara
Amdocs

Dhruv Gupta

AT&T

Sven van der Meer

Ericsson

Prem Sankar Gopannan

Ericsson
Evgeniy Zhukov
Netcracker

Steve Baillargeon

 Ericsson

 maopeng zhang

 ZTE


 Parviz Yegani Huawei
Pasi VaananenRed Hat
Yang Xu
Huawei
Remus TanCiena

Timo Perala

Nokiayes
Ramesh NagarajanAccenture
Jasmin AudetGenicom

Zhe Huang

AT&Tyes



Call Notes

DateAgendaNotes
apr/6
  1. Permanent time for meetings: Mondays 9am est is proposed by multi parties
  2. Review the Edge scoping doc/updates
  3. Review the list of docs submitted
  4. Open discussion for follow up topics with priorities
  5. Clarify where/what is Edge (tentatively, a gold star has been awarded to one :-)..but, could be awarded to more!)
  6. ONAP specific aspects/scoping doc addressed this?
  1. Meeting time consensus - 8:00am PT Ramki to reach out to OOF team to change the time of OOF meetings.


















  • No labels