Miles Stötzner

Miles Stötzner


Research Focus & Metrics

Academic Career Length

5Years (2022-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
16 March 2024
Verified
Book Chapter
Closed access
PDF file
RPRobin D. Pesl
Robin D. Pesl
MSMiles Stötzner
Miles Stötzner
IGIlche Georgievski
Ilche Georgievski
MAMarco Aiello
Marco Aiello

19 October 2022 in Algorithms
Verified
Journal Article
Open access
PDF file
MSMiles Stötzner
Miles Stötzner
SBSteffen Becker
Steffen Becker
Uwe BreitenbücherUwe Breitenbücher
Uwe Breitenbücher
KKKálmán Képes
Kálmán Képes
FLFrank Leymann
Frank Leymann
For automating the deployment of composite applications, typically, declarative deployment models are used. Depending on the context, the deployment of an application has to fulfill different requirements, such as costs and elasticity. As a consequence, one and the same application, i.e., its components, and their dependencies, often need to be deployed in different variants. If each different variant of a deployment is described using an individual deployment model, it quickly results in a large number of models, which are error prone to maintain. Deployment technologies, such as Terraform or Ansible, support conditional components and dependencies which allow modeling different deployment variants of a composite application in a single deployment model. However, there are deployment technologies, such as TOSCA and Docker Compose, which do not support such conditional elements. To address this, we extend the Essential Deployment Metamodel (EDMM) by conditional components and dependencies. EDMM is a declarative deployment model which can be mapped to several deployment technologies including Terraform, Ansible, TOSCA, and Docker Compose. Preprocessing such an extended model, i.e., conditional elements are evaluated and either preserved or removed, generates an EDMM conform model. As a result, conditional elements can be integrated on top of existing deployment technologies that are unaware of such concepts. We evaluate this by implementing a preprocessor for TOSCA, called OpenTOSCA Vintner, which employs the open-source TOSCA orchestrators xOpera and Unfurl to execute the generated TOSCA conform models.


4 December 2023
Verified
Conference Paper
Open access
MSMiles Stötzner
Miles Stötzner
SBSteffen Becker
Steffen Becker
LHLukas Harzenetter
Lukas Harzenetter
FLFrank Leymann
Frank Leymann
BWBenjamin Weder
Benjamin Weder
Jacopo SoldaniJacopo Soldani
Jacopo Soldani

4 December 2023
Verified
Conference Paper
Open access
MSMiles Stötzner
Miles Stötzner
FKFloriment Klinaku
Floriment Klinaku
RPRobin Dominic Pesl
Robin Dominic Pesl
SBSteffen Becker
Steffen Becker
Since applications often need to be deployed in different variants, deployment technologies, such as Ansible and Terraform, support modeling variability. Unfortunately, applications typically need the combination of multiple deployment technologies, which have proprietary and non-interoperable variability concepts. Therefore, variable deployment models have been introduced to model deployment variability across different technologies by assigning variability conditions to elements to specify their presence. However, the manual modeling of these conditions is repetitive, error-prone, and time-consuming. In this paper, we propose to reduce the modeling effort by a pruning concept, i.e., the automated removal of elements due to consistency issues and semantic aspects. To validate the practical feasibility, we implemented a prototype based on Open-TOSCA Vintner. Moreover, we present a case study that shows that the number of conditions to be modeled is significantly decreased.

14 August 2025 in Software: Practice and Experience
Verified
Journal Article
Open access
MSMiles Stötzner
Miles Stötzner
NKNiklas Krieger
Niklas Krieger
SSSandro Speth
Sandro Speth
MWMarcel Weller
Marcel Weller
SBSteffen Becker
Steffen Becker
VMValentin Morlock
Valentin Morlock
Domain: The deployment of distributed multi‐component cloud applications typically requires a combination of multiple heterogeneous deployment technologies. A different combination of deployment technologies should be chosen due to varying deployment qualities, such as the functional suitability and reliability of the deployment technologies for the deployment of the components. A suboptimal selection of deployment technologies makes the deployment error‐prone.Problem: Selecting and maintaining the combination of deployment technologies requires modeling effort and expertise.Contributions: We present a method that automatically selects deployment technologies based on a knowledge base of deployment scenarios and corresponding deployment qualities of deployment technologies.Evaluation: We show the practical applicability and the usefulness of our method. For the practical applicability, we conduct two case studies based on an open‐source reference architecture application and a real‐world industry application using a prototypical implementation of our method. For the usefulness, we conduct a user study in which participants assign deployment technologies with and without our method.Conclusions: Our method is a useful contribution that reduces the modeling effort and the required expertise when maintaining the combination of deployment technologies. Further, our method enhances the deployment quality.