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

Compare with Current View Page History

« Previous Version 102 Next »



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 - In Progress:

  • Edge Scoping
  • Clarify Where/What is Edge...and, focus of this effort
  • Requirements for ONAP R2+
    • 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

Call Schedule:

  • Time: 8:00am PT - 9:30am PT

  • Day: Every Monday
  • Zoom: zoom.us/j/7626591316 (will move to ONAP zoom shortly)

List Subscription/Meeting Notification:

WG Coordinators: 



Contributions

  File Modified
No files shared here yet.

Child Pages

Links to Other ONAP work related to "Edge"

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

Links to other Community Work

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

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




Participants:

WG Coordinators: Raghu Ranganathan, Ramki Krishnan

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 RiverYes
Lyndon OngCiena

Rittwik Jana

AT&T
Ramu
Nokia
John Quilty
Ericsson
Karpura Suryadevara
Amdocs

Dhruv Gupta

AT&Tyes

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

Michela Bevilacqua

Ericsson
Sergio SlobodrianCienayes
Anh LeNetcracker

yaoguang wang

Huawei
Shekar Sundaramurthy  AT&T yes

Call Notes

DateAgendaNotes
04-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.
    • Alexander Vul 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 Scoping 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.

04-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 Scoping discussion
      1. Priorities for Casablanca – initial thoughts captured in the Edge Scoping 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 Scoping 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, Cagatay Buyukkoc to review and expand.

  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
  3. Edge Requirements - input from Vimal Begwani & Cagatay Buyukkoc
  4. Complete discussion Edge_ONAP_WG_v4.pdf for Edge Architecture - Srinivasa Addepalli















  • No labels