TOSCA-based Intent modelling: goal-modelling for infrastructure-as-code

Damian A. Tamburri; Willem-Jan Van den Heuvel; Chris Lauwers; Paul Lipton; Derek Palma; Matt Rutkowski

doi:10.1007/s00450-019-00404-x

TOSCA-based Intent modelling: goal-modelling for infrastructure-as-code

Damian A. Tamburri^*, Willem-Jan Van den Heuvel, Chris Lauwers, Paul Lipton, Derek Palma, Matt Rutkowski

^*Corresponding author for this work

Information Systems & Oper. Mgt.

Research output: Contribution to journal › Article › Scientific › peer-review

Abstract

DevOps entails a set of practices that speed up the time needed to rollout software product changes. One such practice is automating deployment and delivery with infrastructure-as-code, i.e., automated scripts that ideally carry out 1-click deployment. Providing effective infrastructure-as-code poses the tricky issue in determining the modelling and information representation paradigm (e.g., Imperative, Declarative, etc.) most compatible with specifying infrastructural code. The OASIS TOSCA standard ("Topology and Orchestration Specification for Cloud Applications") is the de-facto and de-iure standard language for infrastructure-as-code, and adopts an innovative take called "intent modelling". This paper articulates the foundations of this modelling approach incorporating the most related modelling paradigm, that is, goal-modelling. We elaborate on it with a real but simple industrial sample featuring the TOSCA language.

Original language	English
Pages (from-to)	163-172
Journal	Sics software-Intensive cyber-Physical systems
Volume	34
Issue number	2-3
DOIs	https://doi.org/10.1007/s00450-019-00404-x
Publication status	Published - Jun 2019

Keywords

DevOps
Infrastructure-as-code
Orchestration
Microservices
TOSCA
Goal-modelling
SERVICES

Access to Document

10.1007/s00450-019-00404-x

Cite this

@article{bd5253fe66994df79e7305c0d04c650f,

title = "TOSCA-based Intent modelling: goal-modelling for infrastructure-as-code",

abstract = "DevOps entails a set of practices that speed up the time needed to rollout software product changes. One such practice is automating deployment and delivery with infrastructure-as-code, i.e., automated scripts that ideally carry out 1-click deployment. Providing effective infrastructure-as-code poses the tricky issue in determining the modelling and information representation paradigm (e.g., Imperative, Declarative, etc.) most compatible with specifying infrastructural code. The OASIS TOSCA standard ({"}Topology and Orchestration Specification for Cloud Applications{"}) is the de-facto and de-iure standard language for infrastructure-as-code, and adopts an innovative take called {"}intent modelling{"}. This paper articulates the foundations of this modelling approach incorporating the most related modelling paradigm, that is, goal-modelling. We elaborate on it with a real but simple industrial sample featuring the TOSCA language.",

keywords = "DevOps, Infrastructure-as-code, Orchestration, Microservices, TOSCA, Goal-modelling, SERVICES",

author = "Tamburri, {Damian A.} and {Van den Heuvel}, Willem-Jan and Chris Lauwers and Paul Lipton and Derek Palma and Matt Rutkowski",

year = "2019",

month = jun,

doi = "10.1007/s00450-019-00404-x",

language = "English",

volume = "34",

pages = "163--172",

journal = "Sics software-Intensive cyber-Physical systems",

issn = "2524-8510",

publisher = "SPRINGER HEIDELBERG",

number = "2-3",

}

TY - JOUR

T1 - TOSCA-based Intent modelling

T2 - goal-modelling for infrastructure-as-code

AU - Tamburri, Damian A.

AU - Van den Heuvel, Willem-Jan

AU - Lauwers, Chris

AU - Lipton, Paul

AU - Palma, Derek

AU - Rutkowski, Matt

PY - 2019/6

Y1 - 2019/6

N2 - DevOps entails a set of practices that speed up the time needed to rollout software product changes. One such practice is automating deployment and delivery with infrastructure-as-code, i.e., automated scripts that ideally carry out 1-click deployment. Providing effective infrastructure-as-code poses the tricky issue in determining the modelling and information representation paradigm (e.g., Imperative, Declarative, etc.) most compatible with specifying infrastructural code. The OASIS TOSCA standard ("Topology and Orchestration Specification for Cloud Applications") is the de-facto and de-iure standard language for infrastructure-as-code, and adopts an innovative take called "intent modelling". This paper articulates the foundations of this modelling approach incorporating the most related modelling paradigm, that is, goal-modelling. We elaborate on it with a real but simple industrial sample featuring the TOSCA language.

AB - DevOps entails a set of practices that speed up the time needed to rollout software product changes. One such practice is automating deployment and delivery with infrastructure-as-code, i.e., automated scripts that ideally carry out 1-click deployment. Providing effective infrastructure-as-code poses the tricky issue in determining the modelling and information representation paradigm (e.g., Imperative, Declarative, etc.) most compatible with specifying infrastructural code. The OASIS TOSCA standard ("Topology and Orchestration Specification for Cloud Applications") is the de-facto and de-iure standard language for infrastructure-as-code, and adopts an innovative take called "intent modelling". This paper articulates the foundations of this modelling approach incorporating the most related modelling paradigm, that is, goal-modelling. We elaborate on it with a real but simple industrial sample featuring the TOSCA language.

KW - DevOps

KW - Infrastructure-as-code

KW - Orchestration

KW - Microservices

KW - TOSCA

KW - Goal-modelling

KW - SERVICES

U2 - 10.1007/s00450-019-00404-x

DO - 10.1007/s00450-019-00404-x

M3 - Article

SN - 2524-8510

VL - 34

SP - 163

EP - 172

JO - Sics software-Intensive cyber-Physical systems

JF - Sics software-Intensive cyber-Physical systems

IS - 2-3

ER -

TOSCA-based Intent modelling: goal-modelling for infrastructure-as-code

Abstract

Keywords

Access to Document

Fingerprint

Cite this