# User-Friendly Orchestration Management Proposal

Pablo Josue Rojas Yepes, Carlos Jaime Barrios Hernández, Oscar Carrillo, Frédéric Le Mouël

► To cite this version:

Pablo Josue Rojas Yepes, Carlos Jaime Barrios Hernández, Oscar Carrillo, Frédéric Le Mouël. User-Friendly Orchestration Management Proposal. 2025 - 5th Workshop CATAÏ, May 2025, Chalon sur Saône, France. pp.1-4. hal-05064641

HAL Id: hal-05064641

https://hal.science/hal-05064641v1

Submitted on 5 Jun 2025

HAL is a multi-disciplinary open access
archive for the deposit and dissemination of sci-
entific research documents, whether they are pub-
lished or not. The documents may come from
teaching and research institutions in France or
abroad, or from public or private research centers.

L'archive ouverte pluridisciplinaire HAL, est
destinée au dépôt et à la diffusion de documents
scientifiques de niveau recherche, publiés ou non,
émanant des établissements d'enseignement et de
recherche français ou étrangers, des laboratoires
publics ou privés.

<figure><img src="image_1.png" /></figure>

Distributed under a Creative Commons Attribution 4.0 International License
User-Friendly Orchestration Management Proposal

1st Pablo J. ROJAS Y.

SC3UIS CAGE

Universidad Industrial de Santander
INRIA/INSA-Lyon, CITI Laboratory

Bucaramanga, Colombia
0000-0003-1823-7922

2nd Carlos J. BARRIOS H.

SC3UIS CAGE

Universidad Industrial de Santander
LIG/INRIA-Grenoble

INRIA/INSA-Lyon, CITI Laboratory

Saint Martin d'Hères, France
0000-0002-3227-8651

3rd Oscar A. CARRILLO R.

INRIA/INSA-Lyon, CITI Laboratory

Université de Lyon, CPE-Lyon

Villeurbanne, France
0000-0001-5081-1774

4th Frédéric LE MOUËL

INRIA/INSA-Lyon, CITI Laboratory

Université de Lyon, INSA-Lyon

Villeurbanne, France
0000-0002-7323-4057

*Abstract*—Computing Continuum, with its diverse architectures and distributed features, presents certain challenges in managing and orchestrating resources. Traditional orchestration often requires specialized knowledge, which can be a barrier for users who may lack expertise. In this paper, we introduce User-Friendly Orchestration Management (UFOM), an innovative approach designed to simplify the orchestration of containerized services. With an intuitive interface, automated workflows, and contextual support, UFOM streamlines the entire process. Importantly, UFOM integrates seamlessly with Osmotic Computing, enabling smooth interactions between users and technology. This novel approach democratizes orchestration, empowering users to deploy and manage applications with minimal technical difficulty. We will examine its impact on Quality of Experience (QoE) and present a case study on smart home automation. This case study highlights the capabilities of UFOM in real-world environments, stressing its effectiveness in streamlining deployment, monitoring, and maintenance. Our findings suggest that UFOM not only fosters user independence, but also maintains system reliability and efficiency.

*Index Terms*—Orchestration, DevOps, Computing Continuum, Osmotic Computing, QoS, User QoE.

# I. INTRODUCTION

Distributed computing has evolved significantly, transforming resource management through the integration of cloud, fog, edge computing, and IoT. This integration forms the Computing Continuum (CC), which enables intelligent workload distribution across these layers. This approach improves efficiency, performance, and scalability. To effectively manage the complexity of these diverse environments, robust orchestration and automation are critical. Powered by DevOps practices in the CC, the deployment of applications is further enhanced by making it agile, automated, and resilient, as seen in Fig. 1. This combination promotes continuous delivery and adaptive resource management. Consequently, it drives innovation in areas such as Industry 4.0, Industrial Internet of Things

(2IoT), smart cities, and real-time analytics. Understanding these fundamental principles is essential to effectively utilize the CC and address the challenges of modern distributed systems.

# II. COMPUTING CONTINUUM (CC) TODAY

The Computing Continuum (CC) has evolved through advancements in cloud, fog, and edge computing, alongside the proliferation of IoT devices. This ecosystem enables real-time data processing, enhanced responsiveness, and scalable resource management, that seen in Fig 1. Ensuring quality of service (QoS) [1] and addressing security concerns [2] are key challenges, mitigated through Software-Defined Networking (SDN) and Network Function Virtualization (NFV) [12]. These technologies support applications in domains such as Agriculture 4.0 and time-sensitive data analysis [3]. Fog computing extends cloud capabilities to the network edge [4], optimizing latency-sensitive IoT applications such as tsunami warning systems [5]. Efficient resource utilization is critical, with approaches such as rule-based resource matching, emulation techniques, and serverless computing [6]–[8] improving performance and scalability. Tools such as Continuum Deployer and frameworks like CODA enhance resource allocation while balancing performance, carbon footprint, and QoS [1], [9]. Advanced methods, including EPOS Fog and Markov Blanket applications, further optimize distributed environments [10]–[12]. By strategically distributing computational tasks across the cloud, fog, and edge layers, the CC reduces latency and improves system performance [12].

Fig. 1 illustrates its modern conceptualization, emphasizing seamless data flow and adaptive resource management. Further advancements require robust orchestration mechanisms for dynamic resource allocation [13], [14] and DevOps integration to enable agile development, continuous delivery, and efficient management of the application
<figure><img src="image_2.png" /><figcaption>Fig. 1. Representation of Computing Continuum Concept</figcaption></figure>

[15], [16]. Traditional cloud-centric orchestration platforms struggle with the heterogeneity, volatility, and security challenges on the CC and this can be intuited by the tangle of Fig. 1. Emerging solutions include AI/ML-powered or- chestration for predictive resource allocation and anomaly detection [1], [13], [14], native edge orchestration tailored for edge computing constraints [1], [3], [5], fog computing orchestration optimizing latency, bandwidth, and energy consumption [1], [13], [14]. DevOps enables automation, collaboration, and continuous improvement. Challenges such as organizational inertia, skills gaps, and security risks must be addressed. However, with the support of DevOps practices, software delivery is accelerated, quality and efficiency are improved, and competitive advantage is increased [15], [16]. However, successful DevOps im- plementation requires training and skills development to build expertise, infrastructure modernization for scalable DevOps adoption [17], cross-team collaboration to break down silos, security integration during development [18], continuous improvement based on feedback and best prac- tices [17]. Organizations can make the most of CC for next- generation applications by addressing these factors.

The CC integrates various technologies, leading to sig-
nificant complexity for users. Therefore, a specialized or-
chestrator is essential. This orchestrator should prioritize
user-friendliness by abstracting the underlying techno-
logical complexity. An intuitive orchestrator will enable
developers to build and manage applications efficiently.
Consequently, the CC will become more accessible to a
wider audience.

III. USER-FRIENDLY ORCHESTRATION MANAGEMENT
(UFOM): A PROPOSAL

The Computing Continuum (CC) presents significant
management challenges due to its diverse architectures
and dynamic behavior. Traditional orchestration tools
often demand specialized knowledge, making them diffi-
cult for users with limited experience. To address this,
we propose the User-Friendly Orchestrated Management
(UFOM) concept. It is important to note that UFOM
is a conceptual ideal that requires strong documentation
and thorough testing for validation. Currently, the field
is rich with well-documented proposals that focus on
technology integration, QoS, SLAs, security, and more.
However, these proposals often add layers of complexity,
overwhelming new users, as illustrated in Fig. 1. UFOM
aims to simplify orchestration by providing an intuitive,
user-friendly interface that abstracts the underlying com-
plexities.

UFOM should include several tools designed to enhance
the user experience without compromising orchestration
optimization. Firstly, an intuitive Graphical User Interface
 GUI) is essential. Visual aids like topology diagrams
and resource utilization graphs, similar to those in other
systems, will improve user understanding. Drag-and-drop
and block-based building functionalities for easier appli-
cation/service deployment and configuration should be
considered. A workflow wizard will guide users, helping
them make informed decisions and avoid common errors.
Furthermore, UFOM aims to optimize workflows by pro-
viding predefined templates/mockups for rapid deploy-
ment, automated processes triggered by events or user actions, and predictive analytics to prevent potential issues. Contextual help and support, including in-context tutorials and integration with a knowledge base or chatbot, will significantly assist users in navigating the platform and finding solutions quickly. Implementing Role-Based Access Control (RBAC) will ensure that users access only relevant resources and features, improving security, and simplifying the user experience. Finally, integrating user feedback tools, such as surveys and feedback forms, will facilitate continuous improvement by identifying areas for development and customizing the platform to meet specific user needs.

UFOM addresses the core challenges of traditional orchestration systems. By simplifying inherent complexities, UFOM empowers users with limited experience to efficiently manage their applications, reducing cognitive load, and streamlining orchestration. Furthermore, UFOM enhances the overall user experience with a simple, intuitive, and easy-to-use interface, making system interactions less frustrating. Integrating DevOps practices into UFOM brings significant advantages. Automation, collaboration, and continuous improvement lead to faster and higher-quality software deliveries. Specifically, automated deployment and configuration processes reduce manual errors and accelerate the delivery time. Collaboration channels within UFOM facilitate teamwork, enabling efficient problem resolution and knowledge sharing. Continuous improvement through feedback loops allows for rapid adaptation to changing requirements and user needs. Ultimately, UFOM increases user autonomy and control. Users can make informed decisions about their applications and better understand the underlying infrastructure, leading to a more productive and satisfying experience. This results in greater efficiency, reliability, and innovation in the management of distributed systems.

To assess how well this proposal improves user quality of experience (QoE), we must evaluate it using metrics across three key areas. These areas offer a complete view of system performance, user perception, and operational efficiency, ensuring a thorough and balanced evaluation.

Performance metrics are essential for evaluating a system's ability to respond to user requests efficiently and reliably, establishing a foundation for operational excellence. These metrics include Response Latency, which measures the average time for services to process and return responses, with lower latency indicating a more responsive user experience. Container Startup Time indicates how quickly new containers become operational, crucial for rapid scaling and deployment. Service availability reflects the percentage of time that services are operational, typically measured against SLAs, ensuring continuous service. The error rate quantifies request processing failures, such as HTTP 500 errors, with a low rate indicating system stability. Finally, Network Performance assesses bandwidth and latency between containers and users, critical for

seamless data transfer.

User QoE metrics measure how users experience the system, directly impacting their satisfaction and engagement. This includes Application Load Time, which represents the perceived speed of the application, with faster times improving user satisfaction. Request Success Rate indicates the percentage of user requests completed without errors, building trust and reliability. Service interruptions track the frequency and duration of service interruptions, where minimizing these is crucial to a consistent user experience. Finally, User Satisfaction, assessed through usability surveys and NPS, provides direct feedback on user experience and loyalty.

Operational Efficiency Metrics assess how well a system manages resources while maintaining user experience, focusing on both efficiency and sustainability. This includes CPU and Memory Usage, which monitors resource utilization to optimize based on load, minimizing costs, and maximizing performance. Failure Recovery Time measures how quickly the system recovers from interruptions, reducing downtime and user impact. Dynamic scalability assesses the ability of the system to adapt to changing loads without affecting users, ensuring consistent performance. Energy consumption tracks resource usage to minimize energy expenditure, contributing to sustainability and reducing operational costs.

To validate improvements in user experience, a comparative analysis of these metrics is essential. Specifically, metrics should be measured both before and after implementing orchestration optimizations. Tools such as Prometheus, Grafana, Kiali, Jaeger, and A/B testing techniques can be used effectively to quantify the impact of these changes. This comparative approach, coupled with meticulous monitoring across all three areas, enables us to gain a comprehensive understanding of the system's performance and continuously improve the user Quality of Experience (QoE).

## IV. UFOM PLUS OSMOTIC COMPUTING (UFOM+OC) TO ENCOMPASS SEAMLESS CC

UFOM seeks to reduce the burden on users and at the same time empower them to be self-sufficient in the face of the demands of their applications/services. For this reason, Osmotic Computing and its emphasis on integrating CC layers with seamless and effortless service deployment align perfectly with the goals of UFOM. By abstracting away the complexities of orchestration, UFOM can significantly contribute to a more "osmotic" user experience within the CC. Traditional orchestration platforms require users to understand complex technologies such as containerization or resource management. This shortcoming increases the learning curve and prevents many users from taking advantage of the CC. However, UFOM aims to make orchestration more accessible and intuitive, allowing users to focus on applications, their requirements,
and business objectives while remaining focused on the infrastructure details that they learn as they use UFOM.

UFOM+OC offers several key benefits for the CC. Firstly, it reduces cognitive load by simplifying orchestration, allowing users to focus on higher-level tasks and achieve goals efficiently. Secondly, a better user experience is achieved through a user-friendly interface, which facilitates easier interaction and application management within the CC. Thirdly, UFOM increases accessibility by democratizing orchestration capabilities, making them available to a wider range of users, including those with limited technical expertise. Finally, UFOM empowers users by providing control and visibility into their applications, enabling informed decisions and resource optimization.

Imagine a homeowner who wants to implement a smart home application for lighting, temperature, and security. With traditional orchestration, this would require understanding the infrastructure, writing deployment scripts, and ongoing monitoring. In contrast, UFOM simplifies this process. The homeowner could select a preconfigured template, customize settings through a graphical interface, and deploy with a single click, monitoring progress via a user-friendly dashboard. They would also receive proactive alerts and access online help resources, streamlining the entire deployment and management experience.

This example demonstrates how UFOM can enhance the user experience by abstracting away the complexities of the underlying infrastructure and providing a more intuitive and user-friendly interface for managing smart home applications.

## V. CONCLUSION

UFOM will offer a graphical interface, workflow automation, and contextual assistance to simplify service infrastructure management. It will reduce the need for specialized knowledge, making it more accessible. The proposal seeks to reduce user frustration with visual interfaces, simplified controls, and real-time support. The metrics assess the impact of UFOM on user experience, covering system performance, user perception, and operational efficiency.

UFOM integrates osmotic computing, enabling seamless interaction between user and technology by abstracting the infrastructure. Provides access to complex orchestration without advanced technical skills. A simple demonstration would be to use it in the implementation of smart home applications by removing technical complexities by using ready-made configurations, which would benefit the user with automated monitoring and proactive alerts.

The adoption of UFOM has the potential to democratize infrastructure management in distributed environments and accelerate the expansion of orchestration to new domains. Future research should focus on integrating machine learning, security mechanisms, and standardized communication protocols to improve the effectiveness of

UFOM. Ultimately, UFOM seeks to represent a significant advancement in CC management, aligning with the shift toward more accessible, efficient, and user-centric orchestration.

## REFERENCES

[1] Gupta, H. et al., 2016. SDFog: A software defined computing architecture for QoS aware service orchestration over edge devices. arXiv preprint arXiv:1609.01190.

[2] Kahvazadeh, S. et al., 2019. Securing combined fog-to-cloud systems: challenges and directions. In FTC 2019 (pp. 877-892). Springer.

[3] Zeiner, H. and Unterberger, R., 2021. Timeaware Data Spaces - A key Computing Unit in the Edge-to-Cloud Continuum. In 2021 FiCloud (pp. 250-255). IEEE.

[4] Chiang, M. and Zhang, T., 2016. Fog and IoT: An overview of research opportunities. IEEE Internet of things journal, 3(6), pp.854-864.

[5] Balouek-Thomert, D. et al., 2019. Towards a computing continuum: Enabling edge-to-cloud integration for data-driven workflows. The International Journal of High Performance Computing Applications, 33(6), pp.1159-1174.

[6] Kassir, S. et al., 2020. Service placement for real-time applications: Rate-adaptation and load balancing at the network edge. In CSCloud 2020/EdgeCom 2020 (pp. 207-215). IEEE.

[7] Beckman, P. et al., 2020. Harnessing the computing continuum for programming our world. Fog Computing: Theory and Practice, pp.215-230.

[8] Risco, S. et al., 2021. Serverless workflows for containerized applications in the cloud continuum. Journal of Grid Computing, 19(3), pp.1-18.

[9] Kimovski, D. et al., 2021. Cloud, Fog, or Edge: Where to Compute?. IEEE Internet Computing, 25(4), pp.30-36.

[10] Nezami, Z. et al., 2021. Decentralized edge-to-cloud load balancing: Service placement for the Internet of Things. IEEE Access, 9, pp.64983-65000.

[11] Dustdar, S. et al., 2022. On distributed computing continuum systems. IEEE Transactions on Knowledge and Data Engineering.

[12] Spillner, J. et al., 2022. Intent-Based Placement of Microservices in Computing Continuums. Future Intent-Based Networking, 38-50

[13] Tomarchio O, Calcaterra D, Modica GD (2020) Cloud resource orchestration in the multi-cloud landscape: a systematic review of existing frameworks. J Cloud Comput. https://doi.org/10.1186/s13677-020-00194-7

[14] Svorobej S, Bendechache M, Griesinger F, Domaschka J (2020) Orchestration from the Cloud to the Edge. In: Lynn T, Mooney JG, Lee B, Endo PT (eds) The Cloud-to-Thing Continuum: Opportunities and Challenges in Cloud, Fog and Edge Computing. Springer International Publishing, Cham, p 61–77. https://doi.org/10.1007/978-3-030-41110-7_4

[15] Smeds, J., Nybom, K., & Porres, I. (2015). DevOps: a definition and perceived adoption impediments. In International Conference on Agile Software Development (pp. 166-177). Springer, Cham.

[16] Senapathi, M., Buchan, J., & Osman, H. (2018). DevOps Capabilities, Practices, and Challenges: Insights from a Case Study. Proceedings of the 22nd International Conference on Evaluation and Assessment in Software Engineering 2018.

[17] Trigo, A., Varajão, J., & Sousa, L. (2022). DevOps adoption: Insights from a large European Telco. Cogent Engineering, 9(1), 2083474.

[18] I. Koren, F. Rinker, K. Meixner, J. Matevska, and J. Walter, "Challenges and Opportunities of DevOps in Cyber-Physical Production Systems Engineering," in 2023 IEEE 6th International Conference on Industrial Cyber-Physical Systems (ICPS). Wuhan, China: IEEE, 2023.