Jump to: navigation, search

Difference between revisions of "Edge Computing Group"

(Next meeting: Monday (November 15), 6am PST / 1300 UTC)
(Upcoming Topics)
 
(89 intermediate revisions by the same user not shown)
Line 8: Line 8:
 
* ''' IRC Channel on Freenode - #edge-computing-group '''
 
* ''' IRC Channel on Freenode - #edge-computing-group '''
 
** IRC Channel Logs: http://eavesdrop.openstack.org/irclogs/%23edge-computing-group/
 
** IRC Channel Logs: http://eavesdrop.openstack.org/irclogs/%23edge-computing-group/
* ''' Mailing list - http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing '''
+
* ''' Mailing list - http://lists.opendev.org/cgi-bin/mailman/listinfo/edge-computing '''
  
 
== Meetings ==
 
== Meetings ==
Line 15: Line 15:
 
** '''Calendar file is available [https://object-storage-ca-ymq-1.vexxhost.net/swift/v1/6e4619c416ff4bd19e1c087f27a43eea/www-assets-prod/edge/OpenInfra-Edge-Computing-Group-Weekly-Calls.ics here].'''
 
** '''Calendar file is available [https://object-storage-ca-ymq-1.vexxhost.net/swift/v1/6e4619c416ff4bd19e1c087f27a43eea/www-assets-prod/edge/OpenInfra-Edge-Computing-Group-Weekly-Calls.ics here].'''
  
=== Next meeting: Monday (November 15), 6am PST / 1400 UTC ===
+
=== Next meeting: Monday (May 23), 6am PST / 1300 UTC ===
  
 
==== Call details ====  
 
==== Call details ====  
Line 36: Line 36:
 
=== Action item registry ===
 
=== Action item registry ===
  
*
+
* Find industry experts to invite to the conversations
  
 
=== Agenda ===
 
=== Agenda ===
  
 
Please feel free to add your topic to the agenda. Please add your name as well so we know on the meeting who to ping.
 
Please feel free to add your topic to the agenda. Please add your name as well so we know on the meeting who to ping.
 +
Notes: https://etherpad.opendev.org/p/oif-edge-computing-group
  
 
* '''Action items'''
 
* '''Action items'''
 
** See Action item registry
 
** See Action item registry
* '''Tangled up in Edge Series - Smart Edge'''
+
* '''Tangled up in Edge Series'''
** Presentation and discussion with Neal Oliver
+
** License Management at the edge
 +
** Design and deployment driven by Day2/n ops
 
* '''AoB'''
 
* '''AoB'''
  
 
=== Upcoming Topics ===
 
=== Upcoming Topics ===
* '''November 15th''' at 6am Pacific / 1400 UTC
+
 
** Smart Edge presentation and discussion - Neal Oliver
+
* '''May 23'''
* '''November 22nd'''
+
** '''Containers at the Edge'''
** '''Thanksgiving break, meeting will be cancelled'''
 
* '''November 29th''' at 6am Pacific / 1400 UTC
 
** Networking and DNS discussion with Cricket Liu and Andrew Wertkin
 
* '''December 6th''' at 6am Pacific / 1400 UTC
 
** Networking and IPv6 discussion with Ed Horley
 
* '''December 13th''' at 6am Pacific / 1400 UTC
 
** The Industry IoT Consortium (IIC) Edge Computing Efforts by Chuck Byers - Associate CTO - Industry IoT Consortium (Formerly Industrial Internet Consortium)
 
** IIC has been working on edge computing for about five years.  When the OpenFog Consortium joined IIC in 2019, our edge efforts were strengthened.  We have worked on requirements, reference architectures, standards, best practices, testbeds, product catalogues, presentations and publications regarding edge computing.  In this session, we will outline IIC's edge computing efforts, the work of our Edge Computing Task Group, and the many publications and industry best practices we have delivered.  We will also describe some of our ongoing liaison work, and several whitepapers on edge computing we currently have in production.
 
* '''December 20th''' at 6am Pacific / 1400 UTC
 
** 2022-2023 Predictions
 
* '''December 27th'''
 
** '''Christmas and New Years holiday break, meeting will be cancelled'''
 
* '''January 3rd''' at 6am Pacific / 1400 UTC
 
** 2021 retrospective and 2022 planning
 
  
 
=== Meeting Logs ===
 
=== Meeting Logs ===
Line 78: Line 66:
 
** https://etherpad.opendev.org/p/edge-computing-group-2021-planning
 
** https://etherpad.opendev.org/p/edge-computing-group-2021-planning
  
==== Weekly Call Logs ====
+
==== Virtual PTG Recordings, April, 2022 ====
https://wiki.openstack.org/wiki/Edge_Computing_Group/Weekly_Call_Logs
+
 
 +
* Monday (April 04):
 +
** https://youtu.be/H5sd-VuYP9Y
 +
** https://us06web.zoom.us/rec/share/QGK80wCE9VI25pbnCh9g3VCJpH4sVexrzXnYlnsqinuxbQebs5iRp9zOlQMe2F7_.xXltrV9w0rx_CHw1
 +
*** Access Passcode: jE!1FRn8
 +
* Tuesday (April 05):
 +
** https://us06web.zoom.us/rec/share/AtUvovNIBpt_8gS6r9Euki3YeewlrZmaUHOepfIA3ktQLqn0tobBlkvfHuZ5Vjfr.-yD3rYZSJ6O3Neim
 +
*** Access Passcode: 4fz.2+WF
 +
* Wednesday (April 06):
 +
** https://us06web.zoom.us/rec/share/8rZo9-VjSBOpUniDZ3yNaLGk-6FCUo-40XrrjSknTi4rZ3uAEMO4N431uXCylKVJ.45FGdhGtg2pbx1IG
 +
*** Access Passcode: 33&y41Wp
 +
* etherpad: https://etherpad.opendev.org/p/ecg-ptg-april-2022
 +
 
 +
==== Cheops project update from Inria ====
 +
 
 +
* https://zoom.us/rec/share/gdpFC0_f9uhGXnEGpSSToISTHJyoHTmKcr57uk8LN1gt0yUezRcJqkv4lgxmH-Q.5PhBzbh944kPOS0Q
 +
** Passcode: hrbusv6!
 +
 
 +
==== The Industry IoT Consortium (IIC) Edge Computing Efforts presentation by Chuck Byers ====
 +
 
 +
* https://zoom.us/rec/share/blwYnwvwhAX444tM7uJ23Bq2mnopVA_luASUtrKE_JrDE-mkw0g8LgdAux1IB7Zb.aIdyGCPB8Vj7-4Fy
 +
** Passcode: F=4.U.fA
 +
 
 +
==== Networking and IPv6 discussion with Ed Horley ====
 +
* https://zoom.us/rec/share/2krGWjroEODMZxlCfHq3aOPEHJv1J9R0J6V3oGTq8e_SkjjZPcZRpaIBPukqQPlQ.GMPiav3SJeDm-VGc
 +
** Passcode: QN=z7J*y
 +
 
 +
==== Networking and DNS discussion with Cricket Liu and Andrew Wertkin ====
 +
* https://zoom.us/rec/share/nJ_7hfz3RK93LqwbWjBxIc47QmcqMW2MaSs2HZtuzBZT9U7-UroS9sdaOiqmW2DC.0IMOGbBh_j0mGC--
 +
** Passcode: ccX@PB7M
  
 +
==== Smart Edge presentation and discussion with Neal Oliver, November 15, 2021 ====
 +
* https://zoom.us/rec/share/_REjzMfac1g0p7whjeSAyLM1kO_fpaDnpNygJIXERosWMXqrDqz-og54lm8gO92u.H3IcdwZ-5NWiFjyL
 +
** Passcode: L.7V#RN8
  
 
==== Digital Rebar presentation and discussion with Rob Hirschfeld, November 8, 2021 ====
 
==== Digital Rebar presentation and discussion with Rob Hirschfeld, November 8, 2021 ====
Line 129: Line 149:
 
* https://zoom.us/rec/share/1N0yIozW9n9LbLeS5Vztf7UYDrvdaaa80XUf-PpYz0mZm-PbUlBL8mHcZfzyJN6E
 
* https://zoom.us/rec/share/1N0yIozW9n9LbLeS5Vztf7UYDrvdaaa80XUf-PpYz0mZm-PbUlBL8mHcZfzyJN6E
 
** Password: 8H?A7OC2
 
** Password: 8H?A7OC2
 +
 +
==== Archive - Weekly Call Logs ====
 +
https://wiki.openstack.org/wiki/Edge_Computing_Group/Weekly_Call_Logs
  
 
== Working Group Activities ==
 
== Working Group Activities ==

Latest revision as of 04:01, 13 May 2022

Mission Statement

  • This OSF Edge Computing Group’s objective is to define infrastructure systems needed to support applications distributed over a broad geographic area, with potentially thousands of sites, located as close as possible to discrete data sources, physical elements or end users. The assumption is that network connectivity is over a WAN.
  • The OSF Edge Computing Group will identify use cases, develop requirements, and produce viable architecture options and tests for evaluating new and existing solutions, across different industries and global constituencies, to enable development activities for Open Infrastructure and other Open Source community projects to support edge use cases.

Group Resources

Meetings

  • Mondays at 6am PDT / 1300 UTC
    • Calendar file is available here.

Next meeting: Monday (May 23), 6am PST / 1300 UTC

Call details

  • Join at: https://zoom.us/j/5495195296?pwd=L3NycXhBRys3UEpOc2JzZjZuM25JUT09
    • Meeting ID: 549 519 5296
    • Passcode: openstack
    • One tap mobile
      • +12532158782,,5495195296# US (Tacoma)
      • +13462487799,,5495195296# US (Houston)
    • Dial by your location
      • +1 253 215 8782 US (Tacoma)
      • +1 346 248 7799 US (Houston)
      • +1 669 900 6833 US (San Jose)
      • +1 646 876 9923 US (New York)
      • +1 301 715 8592 US (Washington DC)
      • +1 312 626 6799 US (Chicago)
        • Meeting ID: 549 519 5296
    • Find your local number: https://zoom.us/u/ad8zlEN7JW

Action item registry

  • Find industry experts to invite to the conversations

Agenda

Please feel free to add your topic to the agenda. Please add your name as well so we know on the meeting who to ping. Notes: https://etherpad.opendev.org/p/oif-edge-computing-group

  • Action items
    • See Action item registry
  • Tangled up in Edge Series
    • License Management at the edge
    • Design and deployment driven by Day2/n ops
  • AoB

Upcoming Topics

  • May 23
    • Containers at the Edge

Meeting Logs

Etherpads

Virtual PTG Recordings, April, 2022

Cheops project update from Inria

The Industry IoT Consortium (IIC) Edge Computing Efforts presentation by Chuck Byers

Networking and IPv6 discussion with Ed Horley

Networking and DNS discussion with Cricket Liu and Andrew Wertkin

Smart Edge presentation and discussion with Neal Oliver, November 15, 2021

Digital Rebar presentation and discussion with Rob Hirschfeld, November 8, 2021

Virtual PTG Recordings, October, 2021

CHI@Edge - recording of the session with the Chameleon project, September 13, 2021

Virtual PTG Recordings, April, 2021

Open Geospatial Consortium presentation, November 16, 2020

Virtual PTG Recordings, October, 2020

Password: ptg2020!

Virtual PTG Recordings, June, 2020

Archive - Weekly Call Logs

https://wiki.openstack.org/wiki/Edge_Computing_Group/Weekly_Call_Logs

Working Group Activities

Events

Use cases

Minimal Reference Architectures

https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures

https://wiki.openstack.org/wiki/Edge_Computing_Group/Architecture_Implementations_With_Kubernetes

https://wiki.openstack.org/wiki/Edge_Computing_Group/Hybrid_Architecture_Implementations

Work items for testing

Hacking days

OpenStack Activities

https://wiki.openstack.org/wiki/Edge_Computing_Group/OpenStack_Edge_Activities

StarlingX Activities

Adjacent Projects and Communities

https://wiki.openstack.org/wiki/Edge_Computing_Group/Adjacent_Edge_Projects

Challenges

  • Life-cycle Management. A virtual-machine/container/bare-metal manager in charge of managing machine/container lifecycle (configuration, scheduling, deployment, suspend/resume, and shutdown). (Current Projects: TK)
  • Image Management. An image manager in charge of template files (a.k.a. virtual-machine/container images). (Current Projects: TK)
  • Network Management. A network manager in charge of providing connectivity to the infrastructure: virtual networks and external access for users. (Current Projects: TK)
  • Storage Management. A storage manager, providing storage services to edge applications. (Current Projects: TK)
  • Administrative. Administrative tools, providing user interfaces to operate and use the dispersed infrastructure. (Current Projects: TK)
  • Storage latency. Addressing storage latency over WAN connections.
  • Reinforced security at the edge. Monitoring the physical and application integrity of each site, with the ability to autonomously enable corrective actions when necessary.
  • Resource utilization monitoring. Monitor resource utilization across all nodes simultaneously.
  • Orchestration tools. Manage and coordinate many edge sites and workloads, potentially leading toward a peering control plane or “selforganizing edge.”
  • Federation of edge platforms orchestration (or cloud-of-clouds). Must be explored and introduced to the IaaS core services.
  • Automated edge commission/decommission operations. Includes initial software deployment and upgrades of the resource management system’s components.
  • Automated data and workload relocations. Load balancing across geographically distributed hardware.
  • Synchronization of abstract state propagation Needed at the “core” of the infrastructure to cope with discontinuous network links.
  • Network partitioning with limited connectivity New ways to deal with network partitioning issues due to limited connectivity—coping with short disconnections and long disconnections alike.
  • Manage application latency requirements. The definition of advanced placement constraints in order to cope with latency requirements of application components.
  • Application provisioning and scheduling. In order to satisfy placement requirements (initial placement).
  • Data and workload relocations. According to internal/external events (mobility use-cases, failures, performance considerations, and so forth).
  • Integration location awareness. Not all edge deployments will require the same application at the same moment. Location and demand awareness are a likely need.
  • Dynamic rebalancing of resources from remote sites. Discrete hardware with limited resources and limited ability to expand at the remote site needs to be taken into consideration when designing both the overall architecture at the macro level and the administrative tools. The concept of being able to grab remote resources on demand from other sites, either neighbors over a mesh network or from core elements in a hierarchical network, means that fluctuations in local demand can be met without inefficiency in hardware deployments.