Asymmetric and Directed Bidirectional Transformation for Container Orchestrations

TY - JOUR

T1 - Asymmetric and Directed Bidirectional Transformation for Container Orchestrations

AU - Garcia-Dominguez, Antonio

N1 - Publisher Copyright: © 2023 Copyright for this paper by its authors. Use permitted under Creative Commons License Attribution 4.0 International (CC BY 4.0).

PY - 2024/1/18

Y1 - 2024/1/18

N2 - In many DevOps scenarios, tools operate from declarative models of intended system configuration (e.g. Ansible/Puppet/Chef descriptions of infrastructure-as-code, or Kubernetes and Docker Compose descriptions of orchestrations of containers). DevOps-oriented domain-specific modeling notations will typically only cover a subset of all the capabilities in these configuration formats: this means users will need to manually edit the configuration files generated from the higher-level models. In many editing sessions, users will also touch upon parts that came from the high-level model, and will want that high-level model to be updated accordingly. Likewise, a user may want to introduce a change through the high-level model and not lose the YAML customisations that are unrelated to the high-level model. These requirements imply a need for a bidirectional transformation (“bx”) which is asymmetric (the configuration file contains all the information in the high-level model and more), and directed (changes are only applied to one side at a time). This case proposes revisiting the current state of bx tools for asymmetric and directed transformations, and complements the prior Families to Persons case from TTC 2017, which focused on a symmetrical and directed transformation. The case will reuse the Benchmarx framework from the TTC 2017 case.

AB - In many DevOps scenarios, tools operate from declarative models of intended system configuration (e.g. Ansible/Puppet/Chef descriptions of infrastructure-as-code, or Kubernetes and Docker Compose descriptions of orchestrations of containers). DevOps-oriented domain-specific modeling notations will typically only cover a subset of all the capabilities in these configuration formats: this means users will need to manually edit the configuration files generated from the higher-level models. In many editing sessions, users will also touch upon parts that came from the high-level model, and will want that high-level model to be updated accordingly. Likewise, a user may want to introduce a change through the high-level model and not lose the YAML customisations that are unrelated to the high-level model. These requirements imply a need for a bidirectional transformation (“bx”) which is asymmetric (the configuration file contains all the information in the high-level model and more), and directed (changes are only applied to one side at a time). This case proposes revisiting the current state of bx tools for asymmetric and directed transformations, and complements the prior Families to Persons case from TTC 2017, which focused on a symmetrical and directed transformation. The case will reuse the Benchmarx framework from the TTC 2017 case.

KW - bidirectional transformations

KW - container orchestration

KW - graphical models

KW - model merging

KW - YAML

UR - http://www.scopus.com/inward/record.url?scp=85183908894&partnerID=8YFLogxK

M3 - Conference article

AN - SCOPUS:85183908894

SN - 1613-0073

VL - 3620

JO - CEUR Workshop Proceedings

JF - CEUR Workshop Proceedings

M1 - 6

T2 - 2023 Software Technologies: Applications and Foundations Workshops, STAF-WS 2023; 15th Transformation Tool Contest, TTC 2023, 3rd International Workshop on MDE for Smart IoT Systems, MeSS 2023 and Agile Model-driven Engineering Workshop, AgileMDE 2023

Y2 - 18 July 2023 through 21 July 2023

ER -