OPNFV Edge Cloud strategy Task Force meeting notes: https://etherpad.opnfv.org/p/tsc_edge_cloud

OPNFV Edge Cloud Activities

Note:

Edge NFV (eNFV) project was approved in 2015 but has not been active. Project was terminated by the TSC on 5/8/2018
Multi-access Edge project proposal has been withdrawn

Project or activity	Edge focus (e.g. ingredients, requirements, ...)	Edge scenarios / use-cases	Hardware aspects	Test framework. Edge specific test-cases.	Upstream collaboration	Suggestions
Auto	ONAP-based automation of VNF management with Edge Cloud use-case	Management of Edge Cloud 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	TBD	is working with pharos for edge specific hardware	TBD	openstack EC WG	Begin on code development of reference platform work out report and gap analysis for upstream communities
Container4NFV	Container4NFV 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
Clover	Edge is a scenario for cloud native support. Focus is on service mesh (micro-services) with containers managed by Kubernetes.	5G low latency services, AR/VR, IoT	Select edge devices, will contribute an edge pod to Pharos (with K8S and container support).	Extend CI to zero-touch continuous deployment. Developing Edge test cases for various Cloud Native test tools. Planning performance testing.	ONAP ( pending discussion), k8s, CNCF	Collaborate with EdgeCloud to contribute micro-services use-case and requirements. Contribute Edge POD definition to Pharos spec.
VCO Demo 2.0 (Is a PoC, not run as a project)	Central Office Edge. Mobile network access (vRAN) and scope includes virtualized mobile core network components. "Learn by doing" approach and gap analysis using commercial and open source VNFs.	A set of mobile network specific services	Using community contributed/supported hardware as demo, not on a Pharos POD. For future may use hardware from e.g. OCP, TIP, others?	No edge specific test cases. Testing is not a focus.	ONAP Casablanca (not committed to yet). Also Open Stack, ODL, k8s, OpenAirInterface	Collaborate with EdgeCloud to feed requirements, gaps and learnings. Consider EdgeCloud scenarios for design of VCO 3.0

Upstream Edge Cloud related activities

Upstreams	Edge related activities	useful link	progress	collaboration with OPNFV	suggestion for next step
ONAP	Edge automation WG	https://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 Consider vCPE scenario from white paper. Test Glance and Cinder Edge scenarios.
Akraino (LFN)	Fully integrated edge stack with production quality code 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).	OPNFV liason to Akraino helps inform and facilitate collaboration with regular report back to TSC.
Airship (OSF)	ATT "Oceans" seed code for deployment of "under cloud"		OSF project		Consider site definitions (from ATT) for Pharos Edge spec
StarlingX (OSF)	Wind River Titanium Cloud R5 seed code.		OSF project announced at Open Stack Summit		Consider Wind River Titanium deployment flavors for Edge POD definition.
Open Edge Compute Initiative (OEC)	Developing Open Edge API for 3rd party developers
CORD (ONF)		https://opencord.org/
CNCF (Kubernetes)
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

Opens and Gaps

ETSI MEC

Should OPNFV consider a scenario with ETSI MEC upstream implementation (e.g. NEV SDK)?