Jump to: navigation, search

Difference between revisions of "Edge Computing Group"

(Meetings)
(Agenda)
 
(5 intermediate revisions by the same user not shown)
Line 16: Line 16:
 
** '''Calendar file is available [https://object-storage-ca-ymq-1.vexxhost.net/swift/v1/6e4619c416ff4bd19e1c087f27a43eea/www-assets-prod/edge/OSF-Edge-Computing-Group-Weekly-Calls2.ics here].'''
 
** '''Calendar file is available [https://object-storage-ca-ymq-1.vexxhost.net/swift/v1/6e4619c416ff4bd19e1c087f27a43eea/www-assets-prod/edge/OSF-Edge-Computing-Group-Weekly-Calls2.ics here].'''
  
=== Next meeting: Monday (September 21), 6am PST / 1300 UTC ===
+
=== Next meeting: Monday (November 03), 6am PST / 1300 UTC ===
  
 
==== Call details ====  
 
==== Call details ====  
Line 31: Line 31:
 
* Action items
 
* Action items
 
** See Action item registry
 
** See Action item registry
* KubeEdge joint session
+
* PTG retrospective
* PTG preparation
 
** Time allocation - deadline Sept 11th
 
 
** Agenda - https://etherpad.opendev.org/p/ecg-vptg-october-2020
 
** Agenda - https://etherpad.opendev.org/p/ecg-vptg-october-2020
 
* Recurring items
 
* Recurring items

Latest revision as of 08:37, 13 October 2020

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

Weekly calls in two time slots:

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

Next meeting: Monday (November 03), 6am PST / 1300 UTC

Call details

Action item registry

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.

Meeting Logs

Weekly Call Logs

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

Virtual PTG Recordings, June, 2020

Working Group Activities

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

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.