Versions Compared

Old Version 17

changes.mady.by.user Trevor Cooper

Saved on

compared with

New Version 18

changes.mady.by.user Trevor Cooper

Saved on

Key

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

...

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


Glance image handling in edge environment : https://wiki.openstack.org/wiki/Image_handling_in_edge_environment

Keystone edge architectures: https://wiki.openstack.org/wiki/Keystone_edge_architectures


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.

https://www.akraino.org/

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
  • Proposal to provide lab, test resources?
  • Host Akraino scenario for a release?
Airship (OSF)ATT "Oceans" seed code for deployment of "under cloud"

https://www.airshipit.org/

https://github.com/openstack/airship-in-a-bottle

OSF project


Consider site definitions (from ATT) for Pharos Edge spec
StarlingX (OSF)Wind River Titanium Cloud R5 seed code.http://www.starlingx.io/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)open reference implementation of central office  with commodity servers, white-box switches, open source software (e.g., OpenStack, ONOS, XOS)

https://opencord.org/

https://wiki.opencord.org/

https://guide.opencord.org/

Under development

Kubernetes (CNCF)Automating deployment, scaling, and management of containerized applicationshttps://kubernetes.io/v1.10

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

Telecom Infra Project (TIP)Lab and field implementations for services/applications at the network edge

https://telecominfraproject.com/

https://www.lightreading.com/oss-bss/facebooks-tip-and-telcos-upend-old-operational-models/d/d-id/741488

...





Recommendations

...

  • Develop strong messaging to establish and reinforce OPNFV relevance and unique role in the Industry to integrate and test Edge scenarios in order to solve challenges of deploying and managing Edge Cloud
    • Maintain an Edge "dashboard" to show progress and what has been delivered

...

    • Unified view of Edge use-cases, requirements and features across projects

...


  • Strong collaborations with relevant upstream communities and Edge related activities
    • Already have established working relationship with Open Stack

...

    • Edge Computing Group (this is being merged with FEMDC) and exploring collaboration with Keystone and Glance

  • Establish ongoing feedback with EUAG for evaluating progress and updating objectives

  • Deliver at

...

  • least one Edge Cloud scenario (consider both NFV and non-NFV use-cases) for Gambia 

      ...

        • Pharos Edge spec (first iteration, multi-architecture) 
        • Edge test cases 
           

      ...

      • OVP
        • Develop set of Edge related

      ...

        • test cases based on desirable capabilities of an Edge deployment.


      • Pharos
        • Expand to Edge flavors
          • OpenStack Edge Computing group - 1) small, 2) medium
          • 1) Minimal (fully embedded), 2) small DC (enterprise edge, Access level CO/DC with limited space and power), 3) large (Metro level CO/DC)
        • Harmonize on definitions and terminology. Expand PDF?
        • Support for heterogenous hardware within a POD
        • How to do federation, scaling, simulate characteristics of remote sites?
      • White Paper
        • Include collaboration activities between communities
      • Working with OpenStack on tangible activity 

      ...