Automated Deployment of a Heterogeneous Service-Oriented System

Abstract

Abstract-Deployment of a service-oriented system in a network of machines is often complex and labourious. In many cases components implementing a service have to be built from source code for the right target platform, transferred to the right machines with the right capabilities and activated in the right order. Upgrading a running system is even more difficult as this may break the running system and cannot be performed atomically. Many approaches that deal with the complexity of a distributed deployment process only support certain types of components or specific environments, while general solutions lack certain desirable non-functional properties, such as atomic upgrading. This paper shows Disnix, a deployment tool which allows developers and administrators to reliably deploy, upgrade and roll back a service-oriented system consisting of various types of components in a heterogeneous environment from declarative specifications.

A self-adaptive deployment framework for service-oriented systems

“…Optionally, a proxy can be used to queue connections during this phase, making the transition process truly atomic. More details about the deployment process can be found in [19].…”

“…SDS2 [8] is an industrial case study (described in a previous paper about Disnix [19]). It is a service-oriented architecture designed by Philips Research for Asset Tracking and Utilisation in hospitals.…”

“…We previously have developed Disnix [19,20], a distributed deployment tool built on top of the Nix package manager [10] to deal with the complexity of the deployment process of service-oriented systems. Disnix offers various advantages compared to related tooling, such as a declarative language to capture various properties of distributed systems, the ability to support various types of components, to safely install components next to other components without interference (which ensures that if a machine crashes during an upgrade, the system is not left in an inconsistent state), and to efficiently and reliably upgrade a distributed system in a way that takes all dependencies into account, activating and deactivating components in the right order.…”

“…The function that actually builds the component is defined in the file included at 2 , which is not shown here. More details about these models are described in [19].…”

“…The contribution of this paper is a self-adaptive deployment extension built on top of Disnix [19], a distributed deployment tool for service-oriented systems. This framework continuously discovers machines and their capabilities in a network.…”