Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Meeting notes are here: https://etherpad.opnfv.org/p/tsc_edge_cloud

...

Project or activityEdge focus (e.g. ingredients, requirements, ...)

Edge scenarios / use-cases

Hardware aspectsTest framework. Edge specific test-cases.Upstream collaborationSuggestions
AutoONAP-based automation of VNF management with Edge Cloud use-case
  1. Management of Edge Cloud
  2. vCPE
Compare power consumption of architectures

Functest initially only functional tests. Later include performance monitoring with ONAP Data Collection Analytics and Events

ONAP Edge automation
EdgeCloud

requirement analysis

architecture design

reference platform for edge.

TBDis working with pharos for edge specific hardwareTBDopenstack EC WG
  • Begin on code development of reference platform
  • work out report and gap analysis for upstream communities
Container4NFVContainer4NFV provides basic CT feature for VNF, for example. It supports mutlus, DPDK, and SR-IOV.  In edge , container is the best tool which can reduce the resource usage. No In Container4NFV, we support x86 and ARM.  In order to accelerate data plane, containe4nfv support DPDK and SR-IOV. In future, we will support VPP.

Project specific testing for yardstick.

 test the network performance ,including DPDK, SR-IOV and VPP. 

but not specific for edge


  • cross project collaboration with the edge cloud project and AUTO to work out edge scenario taking consideration of container management
CRAN

Concluding the MEC applications for radio access network, exploring the deployment proposal  for MEC and 5G CU. For the specific design.

TBD


  • start project work asap (mailing list discussion, regular project call, release planning, and etc.)
  • provide CRAN requirement for edge, e.g. acceleration
CloverService mesh (micro-services) with containers managed by Kubernetes.5G low latency services, AR/VR, IoTSelect edge devices with suitable applications.Extend CI to zero-touch continuous deployment.ONAP ( pending discussion)
  • Collaborate with EdgeCloud to provide contribute micro-services use-case and requirements.
VCO Demo 2.0 PoCCentral Office. Mobile network access (vRAN) and virtualized mobile core network components. "Learn by doing" approach and gap analysis suing commercial and open source VNFs.A set of mobile network specific servicesUsing community contributed/supported Hardware, not a Pharos POD. For future use hw from OCP, TIP, others?No edge specific test cases. Testing is not a focus.ONAP Casablanca (not committed yet). Open Stack, ODL, k8s, OpenAirInterface.
  • Collaborate with EdgeCloud to provide requirements, gaps and learnings.
  • Consider EdgeCloud scenarios for design of VCO 3.0

...

Upstream edge related activities

UpstreamsEdge related activitiesuseful linkprogresscollaboration with OPNFVsuggestion for next step
ONAPEdge automation WGhttps://wiki.onap.org/display/DW/Edge+Automation+through+ONAP

Regular meetings

some discussion for vCPE and MEC

Not yet.

Hope the connection could be built with AUTO and Edge cloud project to address Orchestration issue of edge

  • Build connection through AUTO and edge cloud project
  • addresss edge orchestration issues in ONAP
OpenStack

Edge computing WG start in 2017

Fog/Edge/Massively Distributed Clouds SIG

https://www.openstack.org/edge-computing/

https://www.openstack.org/assets/edge/OpenStack-EdgeWhitepaper-v3-online.pdf

https://wiki.openstack.org/wiki/Fog_Edge_Massively_Distributed_Clouds

white paper publish for edge from the EC WG

discussion of EC WG mainly focusing on security of edge, Keystone, Glance. Not to redesign OpenStack from scrach for edge, but to made certain modification to have openstack fit into edge

Collaboration with the edge cloud project already built
  • Enhance the collaboration following the deployment of EC WG and bring them back into OPNFV integration
Akraino (LFN)
Blueprints, enable developers with APIs, SDKs, integrated stack including MEC (NEV SDK)
Fully integrated edge stack with production quality and blue-prints including hardware specs.

Akraino 1.0 release definition, Blueprints definition, use cases .... brainstorm from May F2F https://etherpad.acumos.org/p/Akraino-release

Mailing lists https://lists.akraino.org/g/main


Governance and membership/process structures WIP

Current seed code is NEV SDK however this may move into StarlingX

Definition of deliverables WIP ... "blueprints", developer APIs, middleware (SDKs), ETSI MEC functions and APIs


OPNFV has mature CI/CD Infra, test frameworks and release engineering tools/process which could be leveraged by Akraino. OPNFV EdgeCloud is developing requirements which could be consumed by Akraino.

Akraino help define OPNFV Edge Cloud scenarios and Pharos Edge flavors (from Blueprints).


  • Appoint OPNFV liason to Akraino to inform and facilitate collaboration.
Airship (OSF)ATT "Oceans" seed code for
distributed Edge
deployment of "under cloud"
OSF project

StarlingX (OSF)Wind River Titanium Cloud R5 seed code.
OSF project announced at Open Stack Summit

Open Edge Compute Initiative (OEC)Developing Open Edge API for 3rd party developers



CORD (ONF)
https://opencord.org/


ETSI MEC




CNCF (Kubernetes)
MobileEdgeXDeutch Telecom startup for developers doing distributed (Edge) Apps.





EdgeXFoundry (LF)

IoT edge computing framework and and ecosystem of interoperable components that accelerates the
deployment of IoT solutions

https://www.edgexfoundry.org/


Certification program planned