Currently, the Technology Modeling Language only enables the modeling of service properties for deployment and infrastructure (i.e., operation) technologies. The set of expressible property types should be extended by technology-dependent properties that concern the operation node itself, e.g., Kubernetes configuration properties.
The current workaround for operation models to configure a node is the usage of the default properties section. Semantically, this section does however also target services that are deployed to the node (container) or use the node (infrastructure).
For the inclusion of technology-dependent, node-related properties further reasoning is required (list is probably not complete):
How to call the new type of properties and how to map it to a section in the concrete syntax of the Technology and Operation Modeling Language?
What happens to the default properties section of the Operation Modeling Language? Should it be renamed, e.g., to default service properties?
etc.
Currently, the Technology Modeling Language only enables the modeling of
service propertiesfor deployment and infrastructure (i.e., operation) technologies. The set of expressible property types should be extended by technology-dependent properties that concern the operation node itself, e.g., Kubernetes configuration properties.The current workaround for operation models to configure a node is the usage of the
default propertiessection. Semantically, this section does however also target services that are deployed to the node (container) or use the node (infrastructure).For the inclusion of technology-dependent, node-related properties further reasoning is required (list is probably not complete):
default propertiessection of the Operation Modeling Language? Should it be renamed, e.g., todefault service properties? etc.