Thesis (Ph.D.)--University of Nebraska-Lincoln, 2009. / Title from title screen (site viewed June 26, 2009). PDF text: 169 p. : ill. ; 3 Mb. UMI publication number: AAT 3350444. Includes bibliographical references. Also available in microfilm and microfiche formats.

The purpose of this study is to compare the software deployment tools Ansible, Chef and SaltStackregarding deployment time and their respective resource utilization, and the findings of this studyare also compared to the previous works of Benson et al. (2016), which also studied deploymenttime. However, there is no previous research which mentions resource utilization, which is equallyimportant. The study consists of an experiment performed in one of the laboratory rooms at theUniversity of Skövde where all three software deployment tools are configured to deploy a setamount of packages to three hosts each.By measuring deployment time with the most stable releases (as of 2017-04-22) for each softwaredeployment tool, as well as resource utilization for each host and server, this study may assist systemadministrators to make more informed decisions when deciding which application to use to managetheir computers and infrastructure.The results of the study show that Chef is the fastest software deployment tool in terms ofdeployment time. Chef is also shown to be the most optimized application, as its usage of resourcesis better than both Ansible and SaltStack. / Syftet med denna studie är att studera och jämföra fjärrinstallationsprogrammen Ansible, Chef ochSaltStack gällande den tid det att installera en mängd program på ett antal klienter, och derasrespektive resursutnyttjande. Resultaten från denna studie jämförs även med tidigare studier avBenson et al. (2016), som också studerat tidsåtgången för Ansible, Chef och SaltStack. Det finnsemellertid ingen tidigare forskning som nämner resursutnyttjande, vilket är lika viktigt. Studienbestår av ett experiment som utförs i ett av laboratorierna vid Högskolan i Skövde där alla treprogram konfigureras och användes för att installera en viss mängd paket till tre klientdatorervardera.Genom att mäta tiden det tar för varje program med de senaste stabila utgåvorna (2017-04-22),samt resursutnyttjandet för varje klientdator och server, kan systemadministratörer läsa dennastudie för att fatta mer informerade beslut när de bestämmer vilken applikation som ska användasför att hantera deras datorer och infrastruktur.Resultaten av studien visar att Chef är det snabbaste fjärrinstallationsprogrammet för att installerapaket på klienter. Chef visar sig också vara den mest optimerade applikationen, eftersom dessresursutnyttjande är bättre än både Ansible och SaltStack.

Software deployment, eller mjukvarudistribution översatt till svenska kan ses som processen där alla aktiviteter ingår för att göra en mjukvara tillgänglig för användare utan en manuell installation på användarens dator eller annan maskin. Det finns ett flertal software deployment-verktyg, som hanterar automatiska installationer, tillgängliga för företag på marknaden idag.  Avdelningen HVDC på ABB i Ludvika har behov att börja använda ett verktyg för automatiserade installationer av mjukvaror då installationer idag utförs manuellt och är tidsödande. Som Microsoftpartners vill ABB se hur Microsofts verktyg för mjukvarudistribution skulle kunna hjälpa för detta behov.  Vår studie syftade till att undersöka hur arbetet med installationer av mjukvara ser ut idag, samt hitta förbättringsmöjligheter för installationer som inte kan automatiseras i nuläget. I studien ingick även att ta fram ett generellt ramverk för hur verksamheter kan gå tillväga när de vill börja använda sig utav software deployment-verktyg. I ramverket ingår en utformad kravspecifikation som ska utvärderas mot Microsofts verktyg.  För att skapa en uppfattning om hur arbetet i verksamheten ser ut idag har vi utfört enkätundersökning och intervjuer med personal på HVDC. För att utveckla ett ramverk har vi använt oss av insamlade data från de intervjuer, enkätundersökning och gruppintervju som utförts, detta för att identifiera krav och önskemål från personalen hos ett software deployment-verktyg. Litteraturstudier utfördes för att skapa en teoretisk referensram att utgå ifrån vid utvecklande av ramverket och kravspecifikationen.  Studien har resulterat i en beskrivning av software deployment, förbättringsmöjligheter i arbetet med installationer av mjukvara samt ett generellt ramverk som beskriver hur verksamheter kan gå tillväga när de ska börja använda ett software deployment-verktyg. Ramverket innehåller också en kravspecifikation som använts för att utvärdera Microsofts verktyg för mjukvarudistribution. I vår studie har vi inte sett att någon tidigare har tagit fram ett generellt ramverk och kravspecifikation som verksamheter kan använda sig av som underlag när de ska börja använda ett software deployment-verktyg. Vårt resultat av studien kan täcka upp detta kunskapsgap. / Software deployment can be seen as the process where all activities are included to make a software available to users without a manual installation on the user’s computer or other machine. There are several software deployment tools that manage automated installations available to enterprises on the market today. The department HVDC at ABB in Ludvika has needs of starting to use a tool for automated installations of software which currently is installed manually and is time consuming. As Microsoft partners ABB wants to see how Microsoft’s tool for software deployment could help for this need.  Our study aimed to investigate how the department´s work with installations of software looks like today and to find opportunities for improvement for installations that can’t be automated at this time. The study also includes to develop a general framework for how businesses can proceed when they want to start using a software deployment tool. The framework also includes a designed requirement specification that will be evaluated against Microsoft´s tool. To create an idea of how the work in the business looks like today, we have performed surveys and interviews with staff in HVDC. In order to develop a framework, we have used the data collected from the interviews, questionnaires and group interviews conducted to identify requirements and wishes from the staff of a software deployment tool. Literature studies were also conducted to create a theoretical framework to use when developing the framework and the requirement specification.  Our studies have resulted in a description of software deployment, opportunities for improvement in the work of software installations and a general framework that describes how businesses can proceed when they are about to start using a software deployment tool. The framework also provides a set of requirements that have used to evaluate Microsoft's tool for software distribution. In our study we have not seen that anyone before have developed a general framework and requirements specification that businesses can use as a basis when to start using a software deployment tool. Our results of the study can cover up this knowledge gap.

A implantação de composições de serviços web de grande escala apresentam vários desafios, tais como falhas corriqueiras na infraestrutura, heterogeneidade tecnológica, distribuição do sistema por diferentes organizações e atualização frequente dos serviços em operação. Nesta dissertação, estudamos como uma implantação automatizada baseada em middleware pode auxiliar na superação de tais desafios. Para isso, desenvolvemos o CHOReOS Enactment Engine, um sistema de middleware que possibilita a implantação distribuída e automatizada de composições de serviços web em uma infraestrutura virtualizada, operando no modelo de computação em nuvem denominado Plataforma como um Serviço. O middleware desenvolvido é avaliado qualitativamente em comparação a abordagens de implantação ad-hoc e quantitativamente pela sua escalabilidade em relação ao tempo de implantação das composições de serviços. / The deployment of large-scale service compositions presents several challenges, such as infrastructure failures, technological heterogeneity, distributions across different organizations, and continuous services updating. In this master thesis, we study how the automated deployed supported by middleware can help in overcoming such challenges. For this purpose, we developed the CHOReOS Enactment Engine, a middleware system that enables the distributed and automated deployment of web service compositions in a virtualized infrastructure, operating in the cloud computing model known as Platform as a Service. The developed middleware is evaluated qualitatively by comparing it with ad-hoc deployment solutions, and it is also evaluated quantitatively by its scalability regarding the deployment time of service compositions.

Le déploiement de logiciels répartis dans des environnements à grande échelle et ouverts (tels les systèmes ubiquitaires, les systèmes mobiles et les systèmes P2P) est une problématique actuelle ouverte. Ces environnements sont distribués, hétérogènes et peuvent être de nature instable (dotés d’une topologie dynamique du réseau). Le déploiement dans ces environnements met en jeu un très grand nombre de machines, de liens réseau ainsi qu’un ensemble de contraintes de déploiement. Quelques solutions de déploiement existent aujourd’hui, mais ne sont exploitables que dans le cadre d’architectures figées et fiables. Dans la plupart des solutions, une personne en charge du déploiement doit décrire plus ou moins manuellement la topologie. En outre, la majorité de ces outils ne prennent pas en compte les problèmes dûs à la variabilité de la qualité de service du réseau, aux pannes des hôtes, aux défaillances des liens du réseau ou encore aux changements dynamiques de topologie, qui caractérisent les environnements ouverts. Dans ce mémoire, nous présentons les motivations de la réalisation d'une infrastructure de déploiement logiciel autonomique et les exigences sous-jacentes d'une telle plate-forme. Nous présentons un état de l’art du déploiement logiciel que nous analysons au regard du contexte visé. Ensuite, nous présentons notre contribution pour le déploiement autonomique. Notre proposition s'appuie sur une combinaison de technologies (composants logiciels, agents mobiles adaptables, intergiciel, langage dédié). Nous proposons j-ASD, un intergiciel qui exploite la complémentarité de ces technologies pour réaliser un déploiement logiciel autonomique. Le processus de déploiement contient trois étapes : description des contraintes de déploiement, résolution, et déploiement autonomique. Pour la première étape, nous avons défini un langage dédié (DSL) comme langage de haut niveau pour exprimer des contraintes de déploiement. Pour la deuxième, nous avons conçu une infrastructure répartie pour collecter les propriétés des sites cibles, ce qui permet de résoudre les contraintes de déploiement. Pour la troisième étape, nous proposons un intergiciel à base d’agents mobiles pour la réalisation et la supervision du déploiement autonomique. Enfin, nous donnons les éléments de conception du prototype que nous avons implémenté, ainsi que les résultats de certaines expérimentations pour montrer la validité de notre approche / Software deployment in large-scale and open distributed systems (such as ubiquitous systems, mobile systems and P2P systems) is still an open issue. These environments are distributed, heterogeneous and can be naturally unstable (fitted with a dynamic network topology). Deployment in such environments require the management of a large number of hosts, network links and deployment constraints. Existing distributed deployment solutions are usable only within static and reliable topologies of hosts, where a man in charge of the deployment has to describe more or less manually the topology. Moreover, majority of these tools do not take into account network and computer QoS variabilities, hosts crashes, network link failures and network topology changes, which characterize open and mobile environments. In this thesis, we discuss the motivations for an autonomic software deployment and the requirements underlying for such a platform. We carefully study and compare the existing work about software deployment. Then, we propose a middleware framework, designed to reduce the human cost for setting up software deployment and to deal with failure-prone and change-prone environments. We also propose an autonomic deployment process in three steps : deployment constraints description step, constraints resolution step and the autonomic deployment step. For the first step, we defined a high-level constraint-based dedicated language (DSL) as support for expressing deployment constraints. In the second step, we have designed a distributed infrastructure to collect target hosts properties used to solve deployment constraints. For the third step, we propose an agent-based system for establishing and maintaining software deployment. At last, we give an overview of our working prototype with some details on some experimental results

Thesis (Master of Military Studies)-Marine Corps Command and Staff College, 2008. / Title from title page of PDF document (viewed on: Jan 5, 2010). Includes bibliographical references.

A implantação de composições de serviços web de grande escala apresentam vários desafios, tais como falhas corriqueiras na infraestrutura, heterogeneidade tecnológica, distribuição do sistema por diferentes organizações e atualização frequente dos serviços em operação. Nesta dissertação, estudamos como uma implantação automatizada baseada em middleware pode auxiliar na superação de tais desafios. Para isso, desenvolvemos o CHOReOS Enactment Engine, um sistema de middleware que possibilita a implantação distribuída e automatizada de composições de serviços web em uma infraestrutura virtualizada, operando no modelo de computação em nuvem denominado Plataforma como um Serviço. O middleware desenvolvido é avaliado qualitativamente em comparação a abordagens de implantação ad-hoc e quantitativamente pela sua escalabilidade em relação ao tempo de implantação das composições de serviços. / The deployment of large-scale service compositions presents several challenges, such as infrastructure failures, technological heterogeneity, distributions across different organizations, and continuous services updating. In this master thesis, we study how the automated deployed supported by middleware can help in overcoming such challenges. For this purpose, we developed the CHOReOS Enactment Engine, a middleware system that enables the distributed and automated deployment of web service compositions in a virtualized infrastructure, operating in the cloud computing model known as Platform as a Service. The developed middleware is evaluated qualitatively by comparing it with ad-hoc deployment solutions, and it is also evaluated quantitatively by its scalability regarding the deployment time of service compositions.

Software deployment is all of the activities that make a software system available for use. An examaple of such activites can be installations, updating and removing of software. Each deployment platform can differ in quality attributes such as performance, maintainability, etc. Docker, a deployment platform using container technology offering a more modular way of deployment has become increasingly popular over the past few years. The aim of the project is to find out how a deployment with Docker would affect the performance of a client­server application from the mining industry. Three scenarios were performed in a simulated environment for the existing as well as the potential deployment platform. Measures of round­trip time were made for both sets of the scenarios. Results show a general decrease in performance when running the application on Docker. This is especially seen in early stages of each scenario, where Docker in average has 15 times higher round­trip times than the existing platform. However, results gathered from each scenario suggests that while Docker does start much slower than the existing platform, in later stages of each scenarios, Docker manages to narrow the gap and be at most 1.14 times higher than the existing platform. In conclusion, while the deployment in which the existing platform is deployed on does out perform Docker, it still shows some promise and could potentially be a worthy option to look at for further work.

Nous avons étudié durant cette thèse les moyens de rendre le déploiement d'un intergiciel auto-adaptatif. Le type d'intergiciel que nous avons considéré ici est hiérarchique (structure de graphe) et distribué. Chaque sommet du graphe modélise un processus qui peut être déployé sur une machine physique ou virtuelle d'une infrastructure de type grille/cloud, les arêtes modélisent des liens de communications entre processus. Il offre aux clients des services de calcul haute performance. Les infrastructures de grilles/cloud étant élastiques (perte et ajout de nœuds), un déploiement statique n'est pas la solution idéale car en cas de panne on risque de tout reprendre à zéro, ce qui est coûteux. Nous avons donc proposé un algorithme auto-stabilisant pour que l'intergiciel puisse retrouver un état stable sans intervention extérieure, au bout d'un temps fini, lorsqu'il est confronté à certains types de pannes. Les types de pannes que nous avons considérés sont les pannes transitoires (simulé par la perte de nœuds, l'ajout de nouveaux nœuds, la perte de liens entre deux nœuds). Pour évaluer ces algorithmes, nous avons conçu un simulateur. Les résultats des simulations montrent qu'un déploiement, sujet à des pannes transitoires, s'auto-adapte. Avant d'en arriver à la phase de programmation du simulateur, nous avons d'abord proposé un modèle d'infrastructure distribuée (ce modèle permet de décrire des environnements de type grille/cloud), un modèle pour décrire certains types d'intergiciels hiérarchiques et enfin un modèle pouvant décrire un intergiciel en cours d'exécution (processus déployés sur les machines). / We have studied the means to make a middleware deployment self-adaptive. Our use case middleware is hierarchical and distributed and can be modeled by a graph. A vertex models a process and an edge models a communication link between two processes. The middleware provides high performance computing services to the users.Once the middleware is deployed on a computing infrastructure like a grid or cloud, how it adapt the changes in dynamic environment? If the deployment is static, it may be necessary to redo all the deployment process, which is a costly operation. A better solution would be to make the deployment self-adaptive. We have proposed a rules-based self-stabilizing algorithm to manage a faulty deployment. Thus, after the detection of an unstable deployment, caused by some transients faults (joining of new nodes or deletion of existing nodes which may modify the deployment topology), the system will eventually recover a stable state, without external help, but only by executing the algorithm.We have designed an ad hoc discrete events simulator to evaluate the proposed algorithm. The simulation results show that, a deployment, subjected to transients faults which make it unstable, adapts itself. Before the simulator design, we had proposed a model to describe a distributed infrastructure, a model to describe hierarchical middleware and a model to describe a deployment, that is the mapping between the middleware processes and the hardware on which they are running on.

Οι ενσωματωμένες συσκευές αποτελούν μια κατηγόρια υπολογιστών ειδικού σκοπού με ραγδαία αύξηση τα τελευταία χρόνια. Σε αντίθεση με τους γνωστούς σε όλους υπολογιστές γενικού σκοπού που μπορούν να επιτελέσουν σχεδόν οποιαδήποτε λειτουργία, οι ενσωματωμένες συσκευές επιτελούν μόνο συγκεκριμένες λειτουργίες, οι οποίες είναι προκαθορισμένες κατά τον σχεδιασμό τους. Η διαχείριση τέτοιων και μη συσκευών αποτελεί ένα τεράστιο κεφάλαιο αφού η διαφορετικότητα των λειτουργιών τους, δημιουργεί ένα διαφορετικό τρόπο αντιμετώπισης τους κατά την πρακτική της διαχείρισης. Υπάρχει περιορισμός στα διαθέσιμα εργαλεία για την διαχείριση όλων των ενσωματωμένων συστημάτων με ένα εργαλείο, αλλά η ερεύνα μας επικεντρώνεται στη διαχείριση οικογενειών τέτοιων συσκευών με κριτήριο τη λειτουργία του ειδικού σκοπού που επιτελούν. Σκοπός λοιπόν της εργασίας είναι ο σχεδιασμός και η ανάπτυξη λογισμικού για την ομαδική διαχείριση οικογένειας ενσωματωμένων συσκευών και κοινών υπολογιστών γενικού σκοπού οπουδήποτε λειτουργικού συστήματος. Η συνεισφορά της υπάρχουσας εργασίας συνοψίζεται στις εξής συνιστώσες: 1. Οι ενσωματωμένες συσκευές στις οποίες επικεντρωθήκαμε αφορούν δικτυακές συσκευές (ασύρματες ή ενσύρματες) πολλών λειτουργιών (Access Points, Clients, Repeaters,Points to Points, WDS, Transparent Clients, Routers). 2. Το λογισμικό για υπολογιστές ειδικού σκοπού που δημιουργήθηκε μπορεί να εκτελεστεί τόσο σε λειτουργικά συστήματα MS Windows όσο και σε *ΝΙΧ. 3. Η ανάπτυξη του λογισμικού έγινε βάση του συστήματος ORSM, το οποίο είναι ένα εργαλείο ανοικτού κώδικα για την απομακρυσμένη διαχείριση συστημάτων και δικτύων. (Με αστερίσκο * τόσο στα περιεχόμενα όσο και στο κύριο μέρος της εργασίας δείχνουμε τις δυνατότητες του νέου λογισμικού σε σχέση με το σύστημα ORSM). Συνοπτικά οι δυνατότητες διαχείρισης αφορά τις παρακάτω λειτουργίες: • Ανακάλυψη περιουσιακών στοιχείων (Inventory Process). • Παρακολούθηση απόδοσης συστημάτων (Monitoring). • Εγκατάσταση και απεγκατάσταση λογισμικού (Software Deployment). • Απομακρυσμένο έλεγχο (Remote Desktop). • Εκτέλεση εντολών κελύφους (Remote Command). / An embedded system is a special-purpose computer system designed to perform one or a few dedicated functions, often with real-time computing constraints. It is usually embedded as a part of a complete device including hardware and mechanical parts. In contrast, a general-purpose computer, such as a personal computer, can do many different tasks depending on programming. Embedded systems control many of the common devices in use today. Managing infrastructure with such devices (embedded and general purpose computers) is usually demanding and expensive but nevertheless essential for organizations. There is a limit in tools which achieve effective management to those infrastructure topologies. At present, open management solutions are few and immature however there are tools such as OpenRSM aiming to deliver lightweight, remote and customizable management, easily customizable to cover the needs of small organizations. OpenRSM implements a generic management framework that models generalized use cases that can be exploited by users to adapt the tool to their needs. However, given maturity of the tool, it is unclear how easy it would be for users to extend it in order to include management of new types of devices. As network environments grow to digital ecosystems, the management targets increase in number and diversity. Wireless active elements, handheld systems or embedded devices are becoming common and need to be brought under standard management practices in the same manner as routers or workstations. This paper describes how the OpenRSM management functionality can be extended in order to provide customizable management of embedded devices and more specifically of wireless access points (the symbol * shows the new extension of ORSM). In general the management capabilities which are embed to OPENRSM system and target to wireless active elements are: (Inventory process, monitoring, firmware upgrade, save/reload configuration settings, remote commands, and discovery process).