Edge Automation through ONAP

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: Edge Compute- Edge Automation through ONAPClosed

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


Child Pages


Links to Other ONAP work related to "Edge"

OpenSource Access Manager (OSAM) Use Case - context of "Edge Orchestration" for Fixed Access

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


Links to other Community Work

OPNFVhttps://wiki.opnfv.org/display/AUTO/Auto+Use+Cases - "Service Provider's Management of Edge Cloud"

AKRAINOhttps://www.akraino.org/ – "Open source software stack to improve the state of edge cloud infrastructure"

AKRAINO TECH DOChttps://docs.google.com/document/d/1NDZWFpMUVe0BPwcsOYecNrwwNDnlFmkdP4jur5pE4oo/edit#

OSF EDGE COMPUTING GROUPhttps://www.openstack.org/edge-computing/ - "Open source initiative to explore cloud edge computing related use cases and scenarios and work on addressing the requirements the group identifies."

Other Useul Links

"NGMN 5G RAN  Whitepaper" https://www.ngmn.org/fileadmin/ngmn/content/downloads/Technical/2018/180226_NGMN_RANFSX_D1_V20_Final.pdf







Participants:

WG Coordinators: @Ramki Krishnan

Name

Company

onap-usecasesub@

Name

Company

onap-usecasesub@

@Ramki Krishnan

VMware

yes

@Paul-André Raymond

B.Yond



@Raghu Ranganathan

Ciena

yes

@Vimal Begwani

AT&T



@Srinivasa Addepalli

Intel

Yes

@Seshu Kumar Mudiganti

Huawei



 @Vijay Kumar

AT&T 



@Vara Prasad Talari

Nokia



@buyukkoc

AT&T



@Alex Vul (Deactivated)

Intel



@Ulas Kozat

Huawei



Gil Hellmann

Wind River

Yes

@Lyndon Ong (Deactivated)

Ciena



@rjana

AT&T



@RAMANJANEYUL AKULA

Nokia



@John Quilty

Ericsson



@Karpura Suryadevara

Amdocs



@Dhruv Gupta

AT&T

yes

@Sven van der Meer [VMware]

Ericsson



@Prem Sankar

Ericsson



@Evgeniy Zhukov

Netcracker



@Steve Baillargeon

 Ericsson



 @maopeng zhang

 ZTE



 @Parviz Yegani

 Huawei



@Pasi Vaananen

Red Hat

yes

@Yang Xu

Huawei



@Remus Tan

Ciena



@Timo Perala

Nokia

yes

@Ramesh Nagarajan

Accenture



Jasmin Audet

Genicom



@Zhe Huang (Felix)

AT&T

yes

@Michela Bevilacqua [Ericsson]

Ericsson



@Sergio Slobodrian (Deactivated)

Ciena

yes

Anh Le

Netcracker



@wangyaoguang

Huawei



Shekar Sundaramurthy 

 AT&T

 yes

Simone Mangiante <simone.mangiante@vodafone.com>

Vodafone



David.PerezCaparros@swisscom.com

Swisscom

yes

Yoav Kluger

Amdocs

yes

@Sumit Verdi

VMware



tuann@vmware.com

VMware

yes

@Borislav Glozman

Amdocs

yes

@Mike Elliott

Amdocs



Margaret.chiosi1@huawei.com

Huawei

yes

@Eric Multanen (Deactivated)

Intel



@Former user (Deleted)

Reliance Jio

yes

@mathieu duperre

Edgegap



@Xin Miao (Unlicensed)

Huawei



@Davide Cherubini

Vodafone

yes

@kumarcv

Verizon



all Notes

Date

Agenda

Notes

Date

Agenda

Notes

Apr 06, 2018

  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?

ZOOM Recording: GMT20180406-170638_Ramki-Kris_1920x1080.mp4

Meeting Notes:

  1. Meeting time consensus - 8:00am PT. Ramki to reach out to OOF team to change the time of OOF meetings.

  2. Cagatay reviewed Edge Scoping-r3.docx.

    • Discuss where is "Edge" and relevant applications for with a app response time context

    • @Gil Bullard brought up relevance to ONAP context, i.e. ONAP services to external party vs ONAP Multi-VIM driven management/optimization. Federated ONAP operations may be relevant here.

      • The consensus is to discuss this after we agree on the use case scope.

    • @Alex Vul (Deactivated) brought up the distinctions between user equipment vs customer premise equipment in mobile node like a car in the context where "Edge" might be.

      • The demarcation between network provider and end user is left up to service provider. In the case of a car example, the demarc is the Mobile SIM (4G/5G etc.).

    • @Ramki Krishnan brought up architecture vs use case distinction in the Applications and time scales section.

      • The consensus was to move architecture details to a separate section.

    • @Ramki Krishnan brought up need for additional examples other than RAN for item 2) "Near-real-time Apps" in the Applications and time scales section.

      • The consensus for the team to provide input.

    • Created child page Edge Architecture & Work Items with some updated text.

      • Team to review and provide comments.

Agenda to be finalized 24 hrs. before each meeting.

Folks are requested to review the contributions and come prepared with questions.

Apr 09, 2018

  1. Housekeeping:

    1. use case sub committee list subscription for addressing email distribution issues –

      use case sub committee link (https://lists.onap.org/mailman/listinfo/onap-usecasesub)

    2. target dates for input to use case/architecture sub-committee from a Casablanca perspective

  2. Any additional contributions to discuss from the contributions section?

    1. Make progress on Edge Scope - child page.

ZOOM Recording: zoom_0.mp4

Meeting Notes:

  1. Housekeeping

    1. Informed the team through email

    2. Target Dates:

      1. April 30th for Use Case sub committee update about functional requirements for Casablanca and beyond

      2. May 15th for Architecture sub committee update about any changes to the functional/reference architecture for Casablanca and beyond

  2. Contributions:

    1. Distinction between Akraino and this work - question from @Margaret Chiosi

      1. Akraino is an integration project using an opinionated edge stack based on certain open source components.

      2. This effort in ONAP would treat Akraino as another type of edge cloud and managed though ONAP Multi Cloud and other ONAP relevant components.

    2. Edge Architecture & Work Items discussion

      1. Priorities for Casablanca – initial thoughts captured in the Edge Architecture & Work Items wiki

      2. Need to differentiate between 3rd party and operator provided applications – differentiate along real-time and non-real-time and application characteristics – input from Vimal 

      3. MEC_Apps_ONS2018_Rev1.1.pdf was briefly mentioned by @Vimal Begwani as an example of a 3rd party edge app (e.g. pothole fixer app) including relevant MEC APIs; Follow up action: Request @Prakash Ramchandran to present work in one of the call.

    3. Edge_ONAP_WG_v4.pdf (updated deck) from @Srinivasa Addepalli

      1. Edge Deployment/Functional Architecture diagram (slide nos. 7,8, 9) provide initial context for this work. (what diagram to add in Edge Architecture & Work Items wiki?)

      2. For scalability, there was a discussion about child ONAP with a subset of ONAP components.

      3. Edge Requirements - initial thoughts in slides 4, 5 - @Vimal Begwani, @buyukkoc to review and expand.

Apr 16, 2018

  1. Differentiate between 3rd party and operator provided applications  – input from @Vimal Begwani

  2. Differentiate along real-time and non-real-time and application characteristics – input from @Vimal Begwani