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

Compare with Current View Page History

« Previous Version 84 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:

  1. Initial Draft: Cagatay/Vimal/Kaniz: Edge Scoping

To Do:

  • Problem Statement - Clarify Where/What is Edge...and, focus of this effort
  • Identify Target Communities
  • Requirements for ONAP R2+
    • Target April 30th for Use Case sub committee update
    • Target May 1st for Architecture sub committee update 

Call Schedule:

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

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


Contributions

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

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





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. use case sub committee list subscription for addressing email distribution issues.
  2. Finalize Edge Scope.

















  • No labels