EdgeRDV: A Framework for Edge Workload Management at Scale
EdgeRDV: A Framework for Edge Workload Management at Scale
复制标题
DOI：
10.1109/edge60047.2023.00051
复制
发表时间：
2023-07
期刊：
影响因子：
--
通讯作者：
Gloire Rubambiza;Braulio Dumba;Andrew J. Anderson;Hakim Weatherspoon
中科院分区：
文献类型：
--
作者：
Gloire Rubambiza;Braulio Dumba;Andrew J. Anderson;Hakim Weatherspoon
边缘计算是一种分布式计算范式，它将数据密集型应用程序和服务（例如人工智能）移动到更靠近数据源的地方。如今，连接到Internet的边缘端点的快速增长给可扩展应用程序生命周期管理带来了一些挑战。也就是说，管理数千甚至数百万个边缘端点上的数据和工作负载，受到有限的连接性、资源约束、网络和边缘端点故障的挑战。在这项工作中，我们提出了EdgeRDV，这是一种新的边缘抽象，建立在交会节点的思想之上，以大规模管理边缘工作负载。EdgeRDV架构由中央云管理端点（或云集线器）、每个边缘站点（或边缘集线器）的中心网关、冗余网关（或集合节点）和边缘端点组成。除了可扩展的架构外，EdgeRDV还提供了解决单点故障的新技术和算法，并在边缘网络部署中提供可调整的弹性水平和成本效益。我们通过模拟进行了初步的实验来评估EdgeRDV，我们的结果表明，与中继结构相比，EdgeRDV需要的中间节点少一到三个数量级，可以优雅地适应故障，并且在边缘站点的故障恢复期间需要恒定数量的消息，多达667K+边缘端点。
Edge computing is a distributed computing paradigm that moves data-intensive applications and services (e.g., AI) closer to the data source. The rapid growth of edge endpoints connected to the Internet today poses several challenges in scalable application life cycle management. That is, managing data and workloads on several thousand, up to millions of edge endpoints, challenged by limited connectivity, resource constraints, network and edge endpoint failures. In this work, we present EdgeRDV, a new edge abstraction that builds on the idea of rendezvous nodes to manage edge workloads at scale. The EdgeRDV architecture is comprised of a central cloud management endpoint (or cloud hub), a central gateway for each edge site (or edge hub), redundant gateways (or rendezvous nodes), and edge endpoints. Beyond its scalable architecture, EdgeRDV presents new techniques and algorithms that address single points of failures and provide adjustable levels of resilience and cost-effectiveness in edge network deployments. We conducted preliminary experiments to evaluate EdgeRDV, through simulations, and our results show that EdgeRDV requires one to three orders of magnitude fewer intermediate nodes compared to relay structures, can gracefully adapt to failures, and requires a constant number of messages during failure recovery in edge sites with up to 667K+ edge endpoints.