惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
GbyAI
GbyAI
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 三生石上(FineUI控件)
美团技术团队
Last Week in AI
Last Week in AI
WordPress大学
WordPress大学
L
LangChain Blog
雷峰网
雷峰网
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
博客园 - 叶小钗
Engineering at Meta
Engineering at Meta
腾讯CDC
Recent Announcements
Recent Announcements
The Register - Security
The Register - Security
有赞技术团队
有赞技术团队
Blog — PlanetScale
Blog — PlanetScale
博客园 - Franky
博客园 - 司徒正美
The Cloudflare Blog
Google DeepMind News
Google DeepMind News
T
Tailwind CSS Blog
C
Check Point Blog
小众软件
小众软件
V
Visual Studio Blog
V
V2EX
F
Full Disclosure
J
Java Code Geeks
MongoDB | Blog
MongoDB | Blog
罗磊的独立博客
人人都是产品经理
人人都是产品经理
量子位
Apple Machine Learning Research
Apple Machine Learning Research
F
Fortinet All Blogs
Microsoft Security Blog
Microsoft Security Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
博客园 - 【当耐特】
博客园_首页
Y
Y Combinator Blog
N
Netflix TechBlog - Medium
酷 壳 – CoolShell
酷 壳 – CoolShell
Stack Overflow Blog
Stack Overflow Blog
Recorded Future
Recorded Future
G
Google Developers Blog
Vercel News
Vercel News
大猫的无限游戏
大猫的无限游戏
Microsoft Azure Blog
Microsoft Azure Blog
U
Unit 42
爱范儿
爱范儿
Jina AI
Jina AI

OpenStack - Recent changes [en]

Meetings/NeutronDrivers - OpenStack Security Notes - OpenStack OSSN/OSSN-0098 - OpenStack User:ZlixnupTop - OpenStack OpenStack OpenStack Meetings/InfraTeamMeeting - OpenStack User:Jibzfloopgraip - OpenStack OpenStack OpenStack OpenStack OpenStack OpenStack User:Normanroppy - OpenStack OpenStack OpenStack OpenStack OpenStack OpenStack OpenStack OpenStack OpenStack OpenStack OpenStack Difference between revisions of "Meetings/QATeamMeeting" OpenStack Difference between revisions of "CinderMeetings" OpenStack OpenStack OpenStack User:Mufftroxkeere - OpenStack OpenStack 错误 - OpenStack User talk:Normanamoup - OpenStack User:Normanamoup - OpenStack OpenStack OpenStack OpenStack User:Vernonclife - OpenStack User:ForloveBlics - OpenStack User:RobertFap - OpenStack User:Victorbam - OpenStack User:Wompvlimdiaks - OpenStack User:EliseRose - OpenStack “Post quantum openstack”的版本间的差异 - OpenStack User:DonaldJog - OpenStack StarlingX/Containers/Applications/HowToAddNewFluxCDAppInSTX - OpenStack User:Vincentthern - OpenStack User:Robertaided - OpenStack Difference between revisions of "Meetings/InfraTeamMeeting" CinderHibiscusPTGSummary - OpenStack Difference between revisions of "CinderHibiscusPTGSummary" Difference between revisions of "Meetings/Nova" Difference between revisions of "Meetings/NeutronDrivers" “Python Client Library (Marconi)”的版本间的差异 - OpenStack Python Client Library (Marconi) - OpenStack User:JamesCence - OpenStack “StarlingX/Releases”的版本间的差异 - OpenStack “Operations/Meetups”的版本间的差异 - OpenStack “Edge Computing Group”的版本间的差异 - OpenStack User:Doramaland axola - OpenStack User:Josephhek - OpenStack User:CharlesDrapy - OpenStack User:DonaldNax - OpenStack User:Charlesjet - OpenStack User:Marioraith - OpenStack User:GustavoAburf - OpenStack “Technical Committee Tracker”的版本间的差异 - OpenStack Technical Committee Tracker - OpenStack User:HaroldNow - OpenStack User:Antoniobag - OpenStack User:Esmeraldosixq - OpenStack User:RonniAbimi - OpenStack “OSSN/OSSN-0095”的版本间的差异 - OpenStack OSSN/OSSN-0095 - OpenStack “Security Notes”的版本间的差异 - OpenStack Security Notes - OpenStack User:SoniaTed - OpenStack User:Theresalag - OpenStack User:MarieNeumn - OpenStack User:FrancesAdate - OpenStack User:JacobReaft - OpenStack User:DanielHoutt - OpenStack User:Jesseedism - OpenStack User:Esmeraldosnxi - OpenStack User:ScottLat - OpenStack User:Gribmookmaync - OpenStack User:Esmeraldoshjp - OpenStack “Manila/Meetings”的版本间的差异 - OpenStack User:Esmeraldostbd - OpenStack User:Esmeraldosfrt - OpenStack “Meetings/QATeamMeeting”的版本间的差异 - OpenStack User:Grobsnobwef - OpenStack User:Esmeraldosjoy - OpenStack User:SwhegrRib - OpenStack “ThirdPartySystems”的版本间的差异 - OpenStack “Manila”的版本间的差异 - OpenStack User:Jameswhend - OpenStack “Network/Meetings”的版本间的差异 - OpenStack “Swift/Etherpads”的版本间的差异 - OpenStack
Difference between revisions of "Edge Computing Group"
Ildiko · 2026-05-11 · via OpenStack - Recent changes [en]

()

()

Line 17: Line 17:
 

'''Please make sure you have the 'OpenInfra Edge Computing Group' selected in the left column in the 'Committee' section.'''

 

'''Please make sure you have the 'OpenInfra Edge Computing Group' selected in the left column in the 'Committee' section.'''

  

=== Next meeting: Monday (May 11, 2026), 8am PDT / 1500 UTC ===

+

=== Next meeting: Monday (May 19, 2026), 8am PDT / 1500 UTC ===

  
 

==== Call details ====  

 

==== Call details ====  


Latest revision as of 15:35, 11 May 2026

Contents

Mission Statement

  • This OpenInfra 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 OpenInfra 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

Please make sure you have the 'OpenInfra Edge Computing Group' selected in the left column in the 'Committee' section.

Next meeting: Monday (May 19, 2026), 8am PDT / 1500 UTC

Call details

Please note that the above meeting link will take you to a new LFX login page first. If you have an LF account, you can sign in to join the call, and if you remain signed in in that browser the Zoom call will open automatically. You also have the option to register for an LF account, or join the meeting as a guest. If you choose to join as a guest, you will only need to add your name.

    • One tap mobile
      • +12532158782,,91370675993#,,,,*363416# US
      • +13462487799,,91370675993#,,,,*363416# US
    • Dial-in
      • +1 253 215 8782 US (Tacoma)
      • +1 346 248 7799 US (Houston)
      • +1 669 900 6833 US (San Jose)
      • +1 646 374 8656 US (New York)
      • +1 301 715 8592 US (Washington DC)
      • +1 312 626 6799 US (Chicago)
      • 877 369 0926 US (Toll Free)
      • 855 880 1246 US (Toll Free)
      • +1 647 374 4685 Canada
      • +1 647 558 0588 Canada
      • +1 778 907 2071 Canada
      • +1 204 272 7920 Canada
      • +1 438 809 7799 Canada
      • +1 587 328 1099 Canada
      • 855 703 8985 Canada (Toll Free)
        • Meeting ID: 913 7067 5993
        • Meeting Passcode: 363416
    • Find your local number: https://zoom.us/u/alwnPIaVT

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/openinfra-edge-computing-group

Upcoming Topics

Meeting Logs and Recordings

Etherpads

Virtual PTG, April 2024

Edge Strategies Discussion - Hardware - Led by Rob Hirschfeld (RackN)

Edge Strategies Presentation and Discussion Led by Rob Hirschfeld (RackN) - Cont'd

Edge Strategies Presentation and Discussion Led by Rob Hirschfeld (RackN)

Automotive Use Case presentation by Telefonica Research and Zentrix

Virtual PTG, October 2023

Private Mobility - Part 2 Session Recording, April, 2023

Private Mobility Session Recording, April, 2023

Virtual PTG Recording, March 2023

Virtual PTG Recording, October, 2022

Virtual PTG Recordings, April, 2022

Orchestration, Day-2 Operations and StarlingX session

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.