Lightweight edge Slice Orchestration Framework

Arora, Sagar; Ksentini, Adlen; Bonnet, Christian

doi:10.1109/icc45855.2022.9838854

Cited by 7 publications

(5 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…AC DSWM CA-DL NMA MDM MiCADO-Edge [24] ✓ ✓ ✓ Sophos [25] ✓ ✓ ✓ Oakestra [26] ✓ ✓ DECIDE [27] ✓ ✓ ✓ ✓ HomeCloud [28] ✓ Apollo [29] ✓ ORCH [30] ✓ ECCO [31] ✓ COSMOS [32] ✓ ✓ LeSO [33] ✓ ✓ Caravela [34] ✓ ✓ BumbleBee [35] ✓ ✓ SODA [36] ✓ ✓ CHARIOT [37] ✓ ✓ ✓ FogBus2 [38] ✓ IaaSP-SDN [39] ✓ SDO [40] ✓ ✓ SD-ECC [41] ✓ SDRM [42] ✓ CTOSO [43] ✓…”

Section: Frameworkmentioning

confidence: 99%

“…For example, DECIDE proposes a manager component that provides a test environment to simulate different infrastructure and application deployment scenarios [27]. On the other hand, CHARIOT includes a custom language to model configuration information as a set of constraints and a finite look-ahead algorithm to compute the optimal configuration settings [37], while LeSO manages the deployment of micro-services as sub-slices at the Edge [33].…”

Section: A Automated Configurationmentioning

confidence: 99%

“…On the other hand, MiCADO-Edge automatically deploys complex sets of interconnected micro-services using KubeEdge 30 , an open-source orchestrator that extends Kubernetes clusters to non-Cloud workers [24]. Examples of other Edge-oriented K8s automation facilities include Knative 31 for rapid event-driven scalability and serverless deployment, KCP 32 for multi-cluster solutions designed for Edge-Cloud deployments, and Flotta 33 to meet the stringent requirements of even more constrained environments such as the far Edge.…”

Section: A Automated Configurationmentioning

confidence: 99%

See 2 more Smart Citations

A Framework for Cognitive, Decentralized Container Orchestration

Sofia,

Salomon,

Ferlin-Reiter

et al. 2024

IEEE Access

View full text Add to dashboard Cite

This perspective paper introduces a novel framework for container orchestration called CODECO. The CODECO orchestration framework relies on a data-network-computing approach to define the best infrastructure that can support the operation of next-generation Internet applications across a mobile, heterogeneous Edge-Cloud continuum. The selection of such an infrastructure is aligned with target performance profiles defined by the user, such as resilience or greenness. CODECO proposes to rely on decentralized Artificial Intelligence approaches in an attempt to provide the most suitable infrastructure to an application deployment, considering infrastructural challenges, such as intermittent connectivity and node failure. This paper explains the current CODECO framework and provides insight into operational use-cases where CODECO is being deployed, as relevant examples of application for such a framework. Recent developments in the creation of the open-source CODECO framework are described and explained, allowing the use of the framework by the research community. The paper then provides a thorough analysis of CODECO's features in comparison with existing orchestration frameworks, explaining the benefits introduced with this dynamic orchestration approach.INDEX TERMS Edge-Cloud; Orchestration; Kubernetes; AI/ML; heterogeneous networks; data observability.

show abstract

Section: Frameworkmentioning

confidence: 99%

Section: A Automated Configurationmentioning

confidence: 99%

Section: A Automated Configurationmentioning

confidence: 99%

See 1 more Smart Citation

A Framework for Cognitive, Decentralized Container Orchestration

Sofia,

Salomon,

Ferlin-Reiter

et al. 2024

IEEE Access

View full text Add to dashboard Cite

show abstract

“…To define a network service (i.e., a set of applications connected together to provide a service), a tenant uses the GUI to create a Network Service Descriptor (NSD), which will contain one or more applications defined using the Application Descriptor (AppD) model of MEC ETSI [11]. We extended the AppD with one field that indicates the type of deployment: edge or far edge (i.e., on the 5G device).…”

Section: A the User Layer: Webportalmentioning

confidence: 99%

“…3) VIM: The role of the VIM in the facility is to handle the life-cycle of containers (Onboard/Offboard, Instantiation, Runtime, Update, Terminate) deployed on the edge infrastructure or the end device. The developed VIM [11], particularly for the edge, supports micro-service deployment using a different combination of PoDs and containers. To recall PoDs are the smallest schedulable entity in Kubernetes.…”

Section: B Orchestration and Management Planmentioning

confidence: 99%

A 5G Facility for Trialing and Testing Vertical Services and Applications

Arora

Boutiba

Mekki

et al. 2022

IEEE Internet Things M.

Self Cite

View full text Add to dashboard Cite

With its low latency and high speeds, 5G aims to support vertical services like automotive, industry, agriculture, and manufacturing. Unlike the precedent mobile generations, which just provided voice and data to domestic and business customers, 5G aims to create a common infrastructure to support diverse requirements of the vertical industry's needs in terms of communication and networking capabilities, such as high data rate and low latency. But before a commercial deployment, a trial phase is needed to validate that the network can support these requirements. In this context, several 5G facilities have been established to run 5G trials, mainly built to be used by networking experts. However, vertical service owners have small to no knowledge of the technical details of the 5G infrastructure. In this paper, we introduce EURECOM 5G facility, which was specifically designed to run vertical use cases by abstracting and simplifying as much as possible the trial deployment and Key Performance Indicator (KPI) collection. EURECOM 5G facility provides a rich number of 5G components to test, including 5G New Radio, Network Slicing, Edge Computing, and KPI visualization, allowing verticals to have a real 5G environment for testing their applications and services. Finally, the facility relies mainly on open-source components.

show abstract