Deployment Quality Specification 1.0 Release Candidate¶
Hidden Information
The document hides the quality assessments until the user study is conducted.
Quick Tip #1
Elements in graphs can be clicked to open their type definition!
This document specifies the deployment qualities. The specification is under active development and is not backwards compatible with any previous versions.
Deployment Technologies¶
Deployment qualities are defined in the context of the following deployment technologies.
Ansible¶
Ansible is an automation tool that can be used for configuration management, application deployment, and task automation. It allows system administrators and DevOps teams to manage software on servers using SSH, without the need for agents on target nodes. Further, Ansible is capable of managing infrastructure components, such as virtual machines, networks, and storage, and supports a wide range of cloud providers, such as AWS, Azure, Google Cloud and many others. Find out more.
Terraform¶
Terraform is an infrastructure as code (IaC) tool that allows users to define, provision, and manage cloud infrastructure. Using a declarative configuration language called HashiCorp Configuration Language (HCL), Terraform enables users to define infrastructure components such as virtual machines, networks, and storage in human-readable configuration files. It supports a wide range of cloud providers, including AWS, Azure, Google Cloud, and many others. Find out more.
Kubernetes¶
Kubernetes is a platform for automating the deployment, scaling, and management of containerized applications, such as Docker Containers. It provides capabilities for running and managing applications in clusters of servers, ensuring high availability, scalability, and efficient resource utilization. Kubernetes allows to define the desired state of their applications using declarative manifests, which specify the configuration, deployment, and management of containerized workloads. Find out more.
Docker Compose¶
Docker Compose is a tool that enables the definition and running of multi-container applications on a Docker Engine, using a single YAML configuration file. It allows the management of services, networks, and volumes, in a declarative manner. Find out more.
Component "docker.engine"¶
The following scenarios deploy a node template of node type docker.engine with various hosting stacks, artifacts, deployment technologies, and qualities.
Scenario #1¶
In this scenario, the node template "component" of node type docker.engine is deployed. The node template is hosted on the node template "host 1" of node type local.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #2¶
In this scenario, the node template "component" of node type docker.engine is deployed. The node template is hosted on the node template "host 1" of node type remote.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Component "gcp.service"¶
The following scenarios deploy a node template of node type gcp.service with various hosting stacks, artifacts, deployment technologies, and qualities.
Scenario #1¶
In this scenario, the node template "component" of node type gcp.service is deployed. The scenario does not require a specific hosting.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Component "ingress"¶
The following scenarios deploy a node template of node type ingress with various hosting stacks, artifacts, deployment technologies, and qualities.
Scenario #1¶
In this scenario, the node template "component" of node type ingress is deployed. The node template is hosted on the node template "host 1" of node type kubernetes.cluster.
Ansible supports deploying this scenario
Kubernetes supports deploying this scenario
Terraform supports deploying this scenario
Scenario #2¶
In this scenario, the node template "component" of node type ingress is deployed. The node template is hosted on the node template "host 1" of node type local.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #3¶
In this scenario, the node template "component" of node type ingress is deployed. The node template is hosted on the node template "host 1" of node type remote.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Component "mysql.database"¶
The following scenarios deploy a node template of node type mysql.database with various hosting stacks, artifacts, deployment technologies, and qualities.
Scenario #1¶
In this scenario, the node template "component" of node type mysql.database is deployed. The node template is hosted on the node template "host 1" of node type mysql.dbms, which is hosted on the node template "host 2" of node type docker.engine, which is hosted on the node template "host 3" of node type local.machine.
Ansible supports deploying this scenario
Docker Compose supports deploying this scenario
Terraform supports deploying this scenario
Scenario #2¶
In this scenario, the node template "component" of node type mysql.database is deployed. The node template is hosted on the node template "host 1" of node type mysql.dbms, which is hosted on the node template "host 2" of node type docker.engine, which is hosted on the node template "host 3" of node type remote.machine.
Ansible supports deploying this scenario
Docker Compose supports deploying this scenario
Terraform supports deploying this scenario
Scenario #3¶
In this scenario, the node template "component" of node type mysql.database is deployed. The node template is hosted on the node template "host 1" of node type mysql.dbms, which is hosted on the node template "host 2" of node type gcp.cloudsql.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #4¶
In this scenario, the node template "component" of node type mysql.database is deployed. The node template is hosted on the node template "host 1" of node type mysql.dbms, which is hosted on the node template "host 2" of node type kubernetes.cluster.
Ansible supports deploying this scenario
Kubernetes supports deploying this scenario
Terraform supports deploying this scenario
Scenario #5¶
In this scenario, the node template "component" of node type mysql.database is deployed. The node template is hosted on the node template "host 1" of node type mysql.dbms, which is hosted on the node template "host 2" of node type local.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #6¶
In this scenario, the node template "component" of node type mysql.database is deployed. The node template is hosted on the node template "host 1" of node type mysql.dbms, which is hosted on the node template "host 2" of node type remote.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Component "mysql.dbms"¶
The following scenarios deploy a node template of node type mysql.dbms with various hosting stacks, artifacts, deployment technologies, and qualities.
Scenario #1¶
In this scenario, the node template "component" of node type mysql.dbms is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type dbms.image. The node template is hosted on the node template "host 1" of node type docker.engine, which is hosted on the node template "host 2" of node type local.machine.
Ansible supports deploying this scenario
Docker Compose supports deploying this scenario
Terraform supports deploying this scenario
Scenario #2¶
In this scenario, the node template "component" of node type mysql.dbms is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type dbms.image. The node template is hosted on the node template "host 1" of node type docker.engine, which is hosted on the node template "host 2" of node type remote.machine.
Ansible supports deploying this scenario
Docker Compose supports deploying this scenario
Terraform supports deploying this scenario
Scenario #3¶
In this scenario, the node template "component" of node type mysql.dbms is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type dbms.image. The node template is hosted on the node template "host 1" of node type gcp.cloudsql.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #4¶
In this scenario, the node template "component" of node type mysql.dbms is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type dbms.image. The node template is hosted on the node template "host 1" of node type kubernetes.cluster.
Ansible supports deploying this scenario
Kubernetes supports deploying this scenario
Terraform supports deploying this scenario
Scenario #5¶
In this scenario, the node template "component" of node type mysql.dbms is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type dbms.image. The node template is hosted on the node template "host 1" of node type local.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #6¶
In this scenario, the node template "component" of node type mysql.dbms is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type dbms.image. The node template is hosted on the node template "host 1" of node type remote.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Component "object.storage"¶
The following scenarios deploy a node template of node type object.storage with various hosting stacks, artifacts, deployment technologies, and qualities.
Scenario #1¶
In this scenario, the node template "component" of node type object.storage is deployed. The node template is hosted on the node template "host 1" of node type gcp.cloudstorage.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #2¶
In this scenario, the node template "component" of node type object.storage is deployed. The node template is hosted on the node template "host 1" of node type minio.server, which is hosted on the node template "host 2" of node type docker.engine, which is hosted on the node template "host 3" of node type local.machine.
Ansible supports deploying this scenario
Docker Compose supports deploying this scenario
Terraform supports deploying this scenario
Scenario #3¶
In this scenario, the node template "component" of node type object.storage is deployed. The node template is hosted on the node template "host 1" of node type minio.server, which is hosted on the node template "host 2" of node type docker.engine, which is hosted on the node template "host 3" of node type remote.machine.
Ansible supports deploying this scenario
Docker Compose supports deploying this scenario
Terraform supports deploying this scenario
Scenario #4¶
In this scenario, the node template "component" of node type object.storage is deployed. The node template is hosted on the node template "host 1" of node type minio.server, which is hosted on the node template "host 2" of node type kubernetes.cluster.
Ansible supports deploying this scenario
Kubernetes supports deploying this scenario
Terraform supports deploying this scenario
Component "redis.server"¶
The following scenarios deploy a node template of node type redis.server with various hosting stacks, artifacts, deployment technologies, and qualities.
Scenario #1¶
In this scenario, the node template "component" of node type redis.server is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type cache.image. The node template is hosted on the node template "host 1" of node type docker.engine, which is hosted on the node template "host 2" of node type local.machine.
Ansible supports deploying this scenario
Docker Compose supports deploying this scenario
Terraform supports deploying this scenario
Scenario #2¶
In this scenario, the node template "component" of node type redis.server is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type cache.image. The node template is hosted on the node template "host 1" of node type docker.engine, which is hosted on the node template "host 2" of node type remote.machine.
Ansible supports deploying this scenario
Docker Compose supports deploying this scenario
Terraform supports deploying this scenario
Scenario #3¶
In this scenario, the node template "component" of node type redis.server is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type cache.image. The node template is hosted on the node template "host 1" of node type gcp.memorystore.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #4¶
In this scenario, the node template "component" of node type redis.server is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type cache.image. The node template is hosted on the node template "host 1" of node type kubernetes.cluster.
Ansible supports deploying this scenario
Kubernetes supports deploying this scenario
Terraform supports deploying this scenario
Component "service.component"¶
The following scenarios deploy a node template of node type service.component with various hosting stacks, artifacts, deployment technologies, and qualities.
Scenario #1¶
In this scenario, the node template "component" of node type service.component is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type docker.image. The node template is hosted on the node template "host 1" of node type docker.engine, which is hosted on the node template "host 2" of node type local.machine.
Ansible supports deploying this scenario
Docker Compose supports deploying this scenario
Terraform supports deploying this scenario
Scenario #2¶
In this scenario, the node template "component" of node type service.component is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type docker.image. The node template is hosted on the node template "host 1" of node type docker.engine, which is hosted on the node template "host 2" of node type remote.machine.
Ansible supports deploying this scenario
Docker Compose supports deploying this scenario
Terraform supports deploying this scenario
Scenario #3¶
In this scenario, the node template "component" of node type service.component is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type docker.image. The node template is hosted on the node template "host 1" of node type gcp.cloudrun.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #4¶
In this scenario, the node template "component" of node type service.component is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type docker.image. The node template is hosted on the node template "host 1" of node type kubernetes.cluster.
Ansible supports deploying this scenario
Kubernetes supports deploying this scenario
Terraform supports deploying this scenario
Scenario #5¶
In this scenario, the node template "component" of node type service.component is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type tar.archive. The node template is hosted on an arbitrary hosting stack of arbitrary length, which is hosted on the node template "host 2" of node type local.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #6¶
In this scenario, the node template "component" of node type service.component is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type tar.archive. The node template is hosted on an arbitrary hosting stack of arbitrary length, which is hosted on the node template "host 2" of node type remote.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #7¶
In this scenario, the node template "component" of node type service.component is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type zip.archive. The node template is hosted on an arbitrary hosting stack of arbitrary length, which is hosted on the node template "host 2" of node type local.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #8¶
In this scenario, the node template "component" of node type service.component is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type zip.archive. The node template is hosted on an arbitrary hosting stack of arbitrary length, which is hosted on the node template "host 2" of node type remote.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #9¶
In this scenario, the node template "component" of node type service.component is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type zip.archive. The node template is hosted on the node template "host 1" of node type gcp.appengine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Component "software.component"¶
The following scenarios deploy a node template of node type software.component with various hosting stacks, artifacts, deployment technologies, and qualities.
Scenario #1¶
In this scenario, the node template "component" of node type software.component is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type apt.package. The node template is hosted on an arbitrary hosting stack of arbitrary length, which is hosted on the node template "host 2" of node type local.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #2¶
In this scenario, the node template "component" of node type software.component is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type apt.package. The node template is hosted on an arbitrary hosting stack of arbitrary length, which is hosted on the node template "host 2" of node type remote.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #3¶
In this scenario, the node template "component" of node type software.component is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type tar.archive. This node template has the management operations: "create", "delete". The node template is hosted on an arbitrary hosting stack of arbitrary length, which is hosted on the node template "host 2" of node type local.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #4¶
In this scenario, the node template "component" of node type software.component is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type tar.archive. This node template has the management operations: "create", "delete". The node template is hosted on an arbitrary hosting stack of arbitrary length, which is hosted on the node template "host 2" of node type remote.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #5¶
In this scenario, the node template "component" of node type software.component is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type zip.archive. This node template has the management operations: "create", "delete". The node template is hosted on an arbitrary hosting stack of arbitrary length, which is hosted on the node template "host 2" of node type local.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Scenario #6¶
In this scenario, the node template "component" of node type software.component is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type zip.archive. This node template has the management operations: "create", "delete". The node template is hosted on an arbitrary hosting stack of arbitrary length, which is hosted on the node template "host 2" of node type remote.machine.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Component "virtual.machine"¶
The following scenarios deploy a node template of node type virtual.machine with various hosting stacks, artifacts, deployment technologies, and qualities.
Scenario #1¶
In this scenario, the node template "component" of node type virtual.machine is deployed. This node template is implemented by its deployment artifact "artifact" of artifact type machine.image. The node template is hosted on the node template "host 1" of node type openstack.provider.
Ansible supports deploying this scenario
Terraform supports deploying this scenario
Appendix A "Cards"¶
This appendix contains the deployment quality cards.
Rule #1¶
| Attribute | Value |
|---|---|
| Number | 1 |
| Rules | docker.engine::ansible@local.machine |
| Scenario | docker.engine@local.machine |
| Component | docker.engine |
| Technology | ansible |
| Hosting | local.machine |
| Topology |
Rule #2¶
| Attribute | Value |
|---|---|
| Number | 2 |
| Rules | docker.engine::terraform@local.machine |
| Scenario | docker.engine@local.machine |
| Component | docker.engine |
| Technology | terraform |
| Hosting | local.machine |
| Topology |
Rule #3¶
| Attribute | Value |
|---|---|
| Number | 3 |
| Rules | docker.engine::ansible@remote.machine |
| Scenario | docker.engine@remote.machine |
| Component | docker.engine |
| Technology | ansible |
| Hosting | remote.machine |
| Topology |
Rule #4¶
| Attribute | Value |
|---|---|
| Number | 4 |
| Rules | docker.engine::terraform@remote.machine |
| Scenario | docker.engine@remote.machine |
| Component | docker.engine |
| Technology | terraform |
| Hosting | remote.machine |
| Topology |
Rule #5¶
| Attribute | Value |
|---|---|
| Number | 5 |
| Rules | gcp.service::ansible |
| Scenario | gcp.service |
| Component | gcp.service |
| Technology | ansible |
| Topology |
Rule #6¶
| Attribute | Value |
|---|---|
| Number | 6 |
| Rules | gcp.service::terraform |
| Scenario | gcp.service |
| Component | gcp.service |
| Technology | terraform |
| Topology |
Rule #7¶
| Attribute | Value |
|---|---|
| Number | 7 |
| Rules | ingress::ansible@kubernetes.cluster |
| Scenario | ingress@kubernetes.cluster |
| Component | ingress |
| Technology | ansible |
| Hosting | kubernetes.cluster |
| Topology |
Rule #8¶
| Attribute | Value |
|---|---|
| Number | 8 |
| Rules | ingress::kubernetes@kubernetes.cluster |
| Scenario | ingress@kubernetes.cluster |
| Component | ingress |
| Technology | kubernetes |
| Hosting | kubernetes.cluster |
| Topology |
Rule #9¶
| Attribute | Value |
|---|---|
| Number | 9 |
| Rules | ingress::terraform@kubernetes.cluster |
| Scenario | ingress@kubernetes.cluster |
| Component | ingress |
| Technology | terraform |
| Hosting | kubernetes.cluster |
| Topology |
Rule #10¶
| Attribute | Value |
|---|---|
| Number | 10 |
| Rules | ingress::ansible@local.machine |
| Scenario | ingress@local.machine |
| Component | ingress |
| Technology | ansible |
| Hosting | local.machine |
| Topology |
Rule #11¶
| Attribute | Value |
|---|---|
| Number | 11 |
| Rules | ingress::terraform@local.machine |
| Scenario | ingress@local.machine |
| Component | ingress |
| Technology | terraform |
| Hosting | local.machine |
| Topology |
Rule #12¶
| Attribute | Value |
|---|---|
| Number | 12 |
| Rules | ingress::ansible@remote.machine |
| Scenario | ingress@remote.machine |
| Component | ingress |
| Technology | ansible |
| Hosting | remote.machine |
| Topology |
Rule #13¶
| Attribute | Value |
|---|---|
| Number | 13 |
| Rules | ingress::terraform@remote.machine |
| Scenario | ingress@remote.machine |
| Component | ingress |
| Technology | terraform |
| Hosting | remote.machine |
| Topology |
Rule #14¶
| Attribute | Value |
|---|---|
| Number | 14 |
| Rules | mysql.database::ansible@mysql.dbms->docker.engine->local.machine |
| Scenario | mysql.database@mysql.dbms->docker.engine->local.machine |
| Component | mysql.database |
| Technology | ansible |
| Hosting | mysql.dbms -> docker.engine -> local.machine |
| Topology |
Rule #15¶
| Attribute | Value |
|---|---|
| Number | 15 |
| Rules | mysql.database::compose@mysql.dbms->docker.engine->local.machine |
| Scenario | mysql.database@mysql.dbms->docker.engine->local.machine |
| Component | mysql.database |
| Technology | compose |
| Hosting | mysql.dbms -> docker.engine -> local.machine |
| Topology |
Rule #16¶
| Attribute | Value |
|---|---|
| Number | 16 |
| Rules | mysql.database::terraform@mysql.dbms->docker.engine->local.machine |
| Scenario | mysql.database@mysql.dbms->docker.engine->local.machine |
| Component | mysql.database |
| Technology | terraform |
| Hosting | mysql.dbms -> docker.engine -> local.machine |
| Topology |
Rule #17¶
| Attribute | Value |
|---|---|
| Number | 17 |
| Rules | mysql.database::ansible@mysql.dbms->docker.engine->remote.machine |
| Scenario | mysql.database@mysql.dbms->docker.engine->remote.machine |
| Component | mysql.database |
| Technology | ansible |
| Hosting | mysql.dbms -> docker.engine -> remote.machine |
| Topology |
Rule #18¶
| Attribute | Value |
|---|---|
| Number | 18 |
| Rules | mysql.database::compose@mysql.dbms->docker.engine->remote.machine |
| Scenario | mysql.database@mysql.dbms->docker.engine->remote.machine |
| Component | mysql.database |
| Technology | compose |
| Hosting | mysql.dbms -> docker.engine -> remote.machine |
| Topology |
Rule #19¶
| Attribute | Value |
|---|---|
| Number | 19 |
| Rules | mysql.database::terraform@mysql.dbms->docker.engine->remote.machine |
| Scenario | mysql.database@mysql.dbms->docker.engine->remote.machine |
| Component | mysql.database |
| Technology | terraform |
| Hosting | mysql.dbms -> docker.engine -> remote.machine |
| Topology |
Rule #20¶
| Attribute | Value |
|---|---|
| Number | 20 |
| Rules | mysql.database::ansible@mysql.dbms->gcp.cloudsql |
| Scenario | mysql.database@mysql.dbms->gcp.cloudsql |
| Component | mysql.database |
| Technology | ansible |
| Hosting | mysql.dbms -> gcp.cloudsql |
| Topology |
Rule #21¶
| Attribute | Value |
|---|---|
| Number | 21 |
| Rules | mysql.database::terraform@mysql.dbms->gcp.cloudsql |
| Scenario | mysql.database@mysql.dbms->gcp.cloudsql |
| Component | mysql.database |
| Technology | terraform |
| Hosting | mysql.dbms -> gcp.cloudsql |
| Topology |
Rule #22¶
| Attribute | Value |
|---|---|
| Number | 22 |
| Rules | mysql.database::ansible@mysql.dbms->kubernetes.cluster |
| Scenario | mysql.database@mysql.dbms->kubernetes.cluster |
| Component | mysql.database |
| Technology | ansible |
| Hosting | mysql.dbms -> kubernetes.cluster |
| Topology |
Rule #23¶
| Attribute | Value |
|---|---|
| Number | 23 |
| Rules | mysql.database::kubernetes@mysql.dbms->kubernetes.cluster |
| Scenario | mysql.database@mysql.dbms->kubernetes.cluster |
| Component | mysql.database |
| Technology | kubernetes |
| Hosting | mysql.dbms -> kubernetes.cluster |
| Topology |
Rule #24¶
| Attribute | Value |
|---|---|
| Number | 24 |
| Rules | mysql.database::terraform@mysql.dbms->kubernetes.cluster |
| Scenario | mysql.database@mysql.dbms->kubernetes.cluster |
| Component | mysql.database |
| Technology | terraform |
| Hosting | mysql.dbms -> kubernetes.cluster |
| Topology |
Rule #25¶
| Attribute | Value |
|---|---|
| Number | 25 |
| Rules | mysql.database::ansible@mysql.dbms->local.machine |
| Scenario | mysql.database@mysql.dbms->local.machine |
| Component | mysql.database |
| Technology | ansible |
| Hosting | mysql.dbms -> local.machine |
| Topology |
Rule #26¶
| Attribute | Value |
|---|---|
| Number | 26 |
| Rules | mysql.database::terraform@mysql.dbms->local.machine |
| Scenario | mysql.database@mysql.dbms->local.machine |
| Component | mysql.database |
| Technology | terraform |
| Hosting | mysql.dbms -> local.machine |
| Topology |
Rule #27¶
| Attribute | Value |
|---|---|
| Number | 27 |
| Rules | mysql.database::ansible@mysql.dbms->remote.machine |
| Scenario | mysql.database@mysql.dbms->remote.machine |
| Component | mysql.database |
| Technology | ansible |
| Hosting | mysql.dbms -> remote.machine |
| Topology |
Rule #28¶
| Attribute | Value |
|---|---|
| Number | 28 |
| Rules | mysql.database::terraform@mysql.dbms->remote.machine |
| Scenario | mysql.database@mysql.dbms->remote.machine |
| Component | mysql.database |
| Technology | terraform |
| Hosting | mysql.dbms -> remote.machine |
| Topology |
Rule #29¶
| Attribute | Value |
|---|---|
| Number | 29 |
| Rules | mysql.dbms#dbms.image::ansible@docker.engine->local.machine |
| Scenario | mysql.dbms#dbms.image@docker.engine->local.machine |
| Component | mysql.dbms |
| Artifact | dbms.image |
| Technology | ansible |
| Hosting | docker.engine -> local.machine |
| Topology |
Rule #30¶
| Attribute | Value |
|---|---|
| Number | 30 |
| Rules | mysql.dbms#dbms.image::compose@docker.engine->local.machine |
| Scenario | mysql.dbms#dbms.image@docker.engine->local.machine |
| Component | mysql.dbms |
| Artifact | dbms.image |
| Technology | compose |
| Hosting | docker.engine -> local.machine |
| Topology |
Rule #31¶
| Attribute | Value |
|---|---|
| Number | 31 |
| Rules | mysql.dbms#dbms.image::terraform@docker.engine->local.machine |
| Scenario | mysql.dbms#dbms.image@docker.engine->local.machine |
| Component | mysql.dbms |
| Artifact | dbms.image |
| Technology | terraform |
| Hosting | docker.engine -> local.machine |
| Topology |
Rule #32¶
| Attribute | Value |
|---|---|
| Number | 32 |
| Rules | mysql.dbms#dbms.image::ansible@docker.engine->remote.machine |
| Scenario | mysql.dbms#dbms.image@docker.engine->remote.machine |
| Component | mysql.dbms |
| Artifact | dbms.image |
| Technology | ansible |
| Hosting | docker.engine -> remote.machine |
| Topology |
Rule #33¶
| Attribute | Value |
|---|---|
| Number | 33 |
| Rules | mysql.dbms#dbms.image::compose@docker.engine->remote.machine |
| Scenario | mysql.dbms#dbms.image@docker.engine->remote.machine |
| Component | mysql.dbms |
| Artifact | dbms.image |
| Technology | compose |
| Hosting | docker.engine -> remote.machine |
| Topology |
Rule #34¶
| Attribute | Value |
|---|---|
| Number | 34 |
| Rules | mysql.dbms#dbms.image::terraform@docker.engine->remote.machine |
| Scenario | mysql.dbms#dbms.image@docker.engine->remote.machine |
| Component | mysql.dbms |
| Artifact | dbms.image |
| Technology | terraform |
| Hosting | docker.engine -> remote.machine |
| Topology |
Rule #35¶
| Attribute | Value |
|---|---|
| Number | 35 |
| Rules | mysql.dbms#dbms.image::ansible@gcp.cloudsql |
| Scenario | mysql.dbms#dbms.image@gcp.cloudsql |
| Component | mysql.dbms |
| Artifact | dbms.image |
| Technology | ansible |
| Hosting | gcp.cloudsql |
| Topology |
Rule #36¶
| Attribute | Value |
|---|---|
| Number | 36 |
| Rules | mysql.dbms#dbms.image::terraform@gcp.cloudsql |
| Scenario | mysql.dbms#dbms.image@gcp.cloudsql |
| Component | mysql.dbms |
| Artifact | dbms.image |
| Technology | terraform |
| Hosting | gcp.cloudsql |
| Topology |
Rule #37¶
| Attribute | Value |
|---|---|
| Number | 37 |
| Rules | mysql.dbms#dbms.image::ansible@kubernetes.cluster |
| Scenario | mysql.dbms#dbms.image@kubernetes.cluster |
| Component | mysql.dbms |
| Artifact | dbms.image |
| Technology | ansible |
| Hosting | kubernetes.cluster |
| Topology |
Rule #38¶
| Attribute | Value |
|---|---|
| Number | 38 |
| Rules | mysql.dbms#dbms.image::kubernetes@kubernetes.cluster |
| Scenario | mysql.dbms#dbms.image@kubernetes.cluster |
| Component | mysql.dbms |
| Artifact | dbms.image |
| Technology | kubernetes |
| Hosting | kubernetes.cluster |
| Topology |
Rule #39¶
| Attribute | Value |
|---|---|
| Number | 39 |
| Rules | mysql.dbms#dbms.image::terraform@kubernetes.cluster |
| Scenario | mysql.dbms#dbms.image@kubernetes.cluster |
| Component | mysql.dbms |
| Artifact | dbms.image |
| Technology | terraform |
| Hosting | kubernetes.cluster |
| Topology |
Rule #40¶
| Attribute | Value |
|---|---|
| Number | 40 |
| Rules | mysql.dbms#dbms.image::ansible@local.machine |
| Scenario | mysql.dbms#dbms.image@local.machine |
| Component | mysql.dbms |
| Artifact | dbms.image |
| Technology | ansible |
| Hosting | local.machine |
| Topology |
Rule #41¶
| Attribute | Value |
|---|---|
| Number | 41 |
| Rules | mysql.dbms#dbms.image::terraform@local.machine |
| Scenario | mysql.dbms#dbms.image@local.machine |
| Component | mysql.dbms |
| Artifact | dbms.image |
| Technology | terraform |
| Hosting | local.machine |
| Topology |
Rule #42¶
| Attribute | Value |
|---|---|
| Number | 42 |
| Rules | mysql.dbms#dbms.image::ansible@remote.machine |
| Scenario | mysql.dbms#dbms.image@remote.machine |
| Component | mysql.dbms |
| Artifact | dbms.image |
| Technology | ansible |
| Hosting | remote.machine |
| Topology |
Rule #43¶
| Attribute | Value |
|---|---|
| Number | 43 |
| Rules | mysql.dbms#dbms.image::terraform@remote.machine |
| Scenario | mysql.dbms#dbms.image@remote.machine |
| Component | mysql.dbms |
| Artifact | dbms.image |
| Technology | terraform |
| Hosting | remote.machine |
| Topology |
Rule #44¶
| Attribute | Value |
|---|---|
| Number | 44 |
| Rules | object.storage::ansible@gcp.cloudstorage |
| Scenario | object.storage@gcp.cloudstorage |
| Component | object.storage |
| Technology | ansible |
| Hosting | gcp.cloudstorage |
| Topology |
Rule #45¶
| Attribute | Value |
|---|---|
| Number | 45 |
| Rules | object.storage::terraform@gcp.cloudstorage |
| Scenario | object.storage@gcp.cloudstorage |
| Component | object.storage |
| Technology | terraform |
| Hosting | gcp.cloudstorage |
| Topology |
Rule #46¶
| Attribute | Value |
|---|---|
| Number | 46 |
| Rules | object.storage::ansible@minio.server->docker.engine->local.machine |
| Scenario | object.storage@minio.server->docker.engine->local.machine |
| Component | object.storage |
| Technology | ansible |
| Hosting | minio.server -> docker.engine -> local.machine |
| Topology |
Rule #47¶
| Attribute | Value |
|---|---|
| Number | 47 |
| Rules | object.storage::compose@minio.server->docker.engine->local.machine |
| Scenario | object.storage@minio.server->docker.engine->local.machine |
| Component | object.storage |
| Technology | compose |
| Hosting | minio.server -> docker.engine -> local.machine |
| Topology |
Rule #48¶
| Attribute | Value |
|---|---|
| Number | 48 |
| Rules | object.storage::terraform@minio.server->docker.engine->local.machine |
| Scenario | object.storage@minio.server->docker.engine->local.machine |
| Component | object.storage |
| Technology | terraform |
| Hosting | minio.server -> docker.engine -> local.machine |
| Topology |
Rule #49¶
| Attribute | Value |
|---|---|
| Number | 49 |
| Rules | object.storage::ansible@minio.server->docker.engine->remote.machine |
| Scenario | object.storage@minio.server->docker.engine->remote.machine |
| Component | object.storage |
| Technology | ansible |
| Hosting | minio.server -> docker.engine -> remote.machine |
| Topology |
Rule #50¶
| Attribute | Value |
|---|---|
| Number | 50 |
| Rules | object.storage::compose@minio.server->docker.engine->remote.machine |
| Scenario | object.storage@minio.server->docker.engine->remote.machine |
| Component | object.storage |
| Technology | compose |
| Hosting | minio.server -> docker.engine -> remote.machine |
| Topology |
Rule #51¶
| Attribute | Value |
|---|---|
| Number | 51 |
| Rules | object.storage::terraform@minio.server->docker.engine->remote.machine |
| Scenario | object.storage@minio.server->docker.engine->remote.machine |
| Component | object.storage |
| Technology | terraform |
| Hosting | minio.server -> docker.engine -> remote.machine |
| Topology |
Rule #52¶
| Attribute | Value |
|---|---|
| Number | 52 |
| Rules | object.storage::ansible@minio.server->kubernetes.cluster |
| Scenario | object.storage@minio.server->kubernetes.cluster |
| Component | object.storage |
| Technology | ansible |
| Hosting | minio.server -> kubernetes.cluster |
| Topology |
Rule #53¶
| Attribute | Value |
|---|---|
| Number | 53 |
| Rules | object.storage::kubernetes@minio.server->kubernetes.cluster |
| Scenario | object.storage@minio.server->kubernetes.cluster |
| Component | object.storage |
| Technology | kubernetes |
| Hosting | minio.server -> kubernetes.cluster |
| Topology |
Rule #54¶
| Attribute | Value |
|---|---|
| Number | 54 |
| Rules | object.storage::terraform@minio.server->kubernetes.cluster |
| Scenario | object.storage@minio.server->kubernetes.cluster |
| Component | object.storage |
| Technology | terraform |
| Hosting | minio.server -> kubernetes.cluster |
| Topology |
Rule #55¶
| Attribute | Value |
|---|---|
| Number | 55 |
| Rules | redis.server#cache.image::ansible@docker.engine->local.machine |
| Scenario | redis.server#cache.image@docker.engine->local.machine |
| Component | redis.server |
| Artifact | cache.image |
| Technology | ansible |
| Hosting | docker.engine -> local.machine |
| Topology |
Rule #56¶
| Attribute | Value |
|---|---|
| Number | 56 |
| Rules | redis.server#cache.image::compose@docker.engine->local.machine |
| Scenario | redis.server#cache.image@docker.engine->local.machine |
| Component | redis.server |
| Artifact | cache.image |
| Technology | compose |
| Hosting | docker.engine -> local.machine |
| Topology |
Rule #57¶
| Attribute | Value |
|---|---|
| Number | 57 |
| Rules | redis.server#cache.image::terraform@docker.engine->local.machine |
| Scenario | redis.server#cache.image@docker.engine->local.machine |
| Component | redis.server |
| Artifact | cache.image |
| Technology | terraform |
| Hosting | docker.engine -> local.machine |
| Topology |
Rule #58¶
| Attribute | Value |
|---|---|
| Number | 58 |
| Rules | redis.server#cache.image::ansible@docker.engine->remote.machine |
| Scenario | redis.server#cache.image@docker.engine->remote.machine |
| Component | redis.server |
| Artifact | cache.image |
| Technology | ansible |
| Hosting | docker.engine -> remote.machine |
| Topology |
Rule #59¶
| Attribute | Value |
|---|---|
| Number | 59 |
| Rules | redis.server#cache.image::compose@docker.engine->remote.machine |
| Scenario | redis.server#cache.image@docker.engine->remote.machine |
| Component | redis.server |
| Artifact | cache.image |
| Technology | compose |
| Hosting | docker.engine -> remote.machine |
| Topology |
Rule #60¶
| Attribute | Value |
|---|---|
| Number | 60 |
| Rules | redis.server#cache.image::terraform@docker.engine->remote.machine |
| Scenario | redis.server#cache.image@docker.engine->remote.machine |
| Component | redis.server |
| Artifact | cache.image |
| Technology | terraform |
| Hosting | docker.engine -> remote.machine |
| Topology |
Rule #61¶
| Attribute | Value |
|---|---|
| Number | 61 |
| Rules | redis.server#cache.image::ansible@gcp.memorystore |
| Scenario | redis.server#cache.image@gcp.memorystore |
| Component | redis.server |
| Artifact | cache.image |
| Technology | ansible |
| Hosting | gcp.memorystore |
| Topology |
Rule #62¶
| Attribute | Value |
|---|---|
| Number | 62 |
| Rules | redis.server#cache.image::terraform@gcp.memorystore |
| Scenario | redis.server#cache.image@gcp.memorystore |
| Component | redis.server |
| Artifact | cache.image |
| Technology | terraform |
| Hosting | gcp.memorystore |
| Topology |
Rule #63¶
| Attribute | Value |
|---|---|
| Number | 63 |
| Rules | redis.server#cache.image::ansible@kubernetes.cluster |
| Scenario | redis.server#cache.image@kubernetes.cluster |
| Component | redis.server |
| Artifact | cache.image |
| Technology | ansible |
| Hosting | kubernetes.cluster |
| Topology |
Rule #64¶
| Attribute | Value |
|---|---|
| Number | 64 |
| Rules | redis.server#cache.image::kubernetes@kubernetes.cluster |
| Scenario | redis.server#cache.image@kubernetes.cluster |
| Component | redis.server |
| Artifact | cache.image |
| Technology | kubernetes |
| Hosting | kubernetes.cluster |
| Topology |
Rule #65¶
| Attribute | Value |
|---|---|
| Number | 65 |
| Rules | redis.server#cache.image::terraform@kubernetes.cluster |
| Scenario | redis.server#cache.image@kubernetes.cluster |
| Component | redis.server |
| Artifact | cache.image |
| Technology | terraform |
| Hosting | kubernetes.cluster |
| Topology |
Rule #66¶
| Attribute | Value |
|---|---|
| Number | 66 |
| Rules | service.component#docker.image::ansible@docker.engine->local.machine |
| Scenario | service.component#docker.image@docker.engine->local.machine |
| Component | service.component |
| Artifact | docker.image |
| Technology | ansible |
| Hosting | docker.engine -> local.machine |
| Topology |
Rule #67¶
| Attribute | Value |
|---|---|
| Number | 67 |
| Rules | service.component#docker.image::compose@docker.engine->local.machine |
| Scenario | service.component#docker.image@docker.engine->local.machine |
| Component | service.component |
| Artifact | docker.image |
| Technology | compose |
| Hosting | docker.engine -> local.machine |
| Topology |
Rule #68¶
| Attribute | Value |
|---|---|
| Number | 68 |
| Rules | service.component#docker.image::terraform@docker.engine->local.machine |
| Scenario | service.component#docker.image@docker.engine->local.machine |
| Component | service.component |
| Artifact | docker.image |
| Technology | terraform |
| Hosting | docker.engine -> local.machine |
| Topology |
Rule #69¶
| Attribute | Value |
|---|---|
| Number | 69 |
| Rules | service.component#docker.image::ansible@docker.engine->remote.machine |
| Scenario | service.component#docker.image@docker.engine->remote.machine |
| Component | service.component |
| Artifact | docker.image |
| Technology | ansible |
| Hosting | docker.engine -> remote.machine |
| Topology |
Rule #70¶
| Attribute | Value |
|---|---|
| Number | 70 |
| Rules | service.component#docker.image::compose@docker.engine->remote.machine |
| Scenario | service.component#docker.image@docker.engine->remote.machine |
| Component | service.component |
| Artifact | docker.image |
| Technology | compose |
| Hosting | docker.engine -> remote.machine |
| Topology |
Rule #71¶
| Attribute | Value |
|---|---|
| Number | 71 |
| Rules | service.component#docker.image::terraform@docker.engine->remote.machine |
| Scenario | service.component#docker.image@docker.engine->remote.machine |
| Component | service.component |
| Artifact | docker.image |
| Technology | terraform |
| Hosting | docker.engine -> remote.machine |
| Topology |
Rule #72¶
| Attribute | Value |
|---|---|
| Number | 72 |
| Rules | service.component#docker.image::ansible@gcp.cloudrun |
| Scenario | service.component#docker.image@gcp.cloudrun |
| Component | service.component |
| Artifact | docker.image |
| Technology | ansible |
| Hosting | gcp.cloudrun |
| Topology |
Rule #73¶
| Attribute | Value |
|---|---|
| Number | 73 |
| Rules | service.component#docker.image::terraform@gcp.cloudrun |
| Scenario | service.component#docker.image@gcp.cloudrun |
| Component | service.component |
| Artifact | docker.image |
| Technology | terraform |
| Hosting | gcp.cloudrun |
| Topology |
Rule #74¶
| Attribute | Value |
|---|---|
| Number | 74 |
| Rules | service.component#docker.image::ansible@kubernetes.cluster |
| Scenario | service.component#docker.image@kubernetes.cluster |
| Component | service.component |
| Artifact | docker.image |
| Technology | ansible |
| Hosting | kubernetes.cluster |
| Topology |
Rule #75¶
| Attribute | Value |
|---|---|
| Number | 75 |
| Rules | service.component#docker.image::kubernetes@kubernetes.cluster |
| Scenario | service.component#docker.image@kubernetes.cluster |
| Component | service.component |
| Artifact | docker.image |
| Technology | kubernetes |
| Hosting | kubernetes.cluster |
| Topology |
Rule #76¶
| Attribute | Value |
|---|---|
| Number | 76 |
| Rules | service.component#docker.image::terraform@kubernetes.cluster |
| Scenario | service.component#docker.image@kubernetes.cluster |
| Component | service.component |
| Artifact | docker.image |
| Technology | terraform |
| Hosting | kubernetes.cluster |
| Topology |
Rule #77¶
| Attribute | Value |
|---|---|
| Number | 77 |
| Rules | service.component#tar.archive::ansible@*->local.machine |
| Scenario | service.component#tar.archive@*->local.machine |
| Component | service.component |
| Artifact | tar.archive |
| Technology | ansible |
| Hosting | * -> local.machine |
| Topology |
Rule #78¶
| Attribute | Value |
|---|---|
| Number | 78 |
| Rules | service.component#tar.archive::terraform@*->local.machine |
| Scenario | service.component#tar.archive@*->local.machine |
| Component | service.component |
| Artifact | tar.archive |
| Technology | terraform |
| Hosting | * -> local.machine |
| Topology |
Rule #79¶
| Attribute | Value |
|---|---|
| Number | 79 |
| Rules | service.component#tar.archive::ansible@*->remote.machine |
| Scenario | service.component#tar.archive@*->remote.machine |
| Component | service.component |
| Artifact | tar.archive |
| Technology | ansible |
| Hosting | * -> remote.machine |
| Topology |
Rule #80¶
| Attribute | Value |
|---|---|
| Number | 80 |
| Rules | service.component#tar.archive::terraform@*->remote.machine |
| Scenario | service.component#tar.archive@*->remote.machine |
| Component | service.component |
| Artifact | tar.archive |
| Technology | terraform |
| Hosting | * -> remote.machine |
| Topology |
Rule #81¶
| Attribute | Value |
|---|---|
| Number | 81 |
| Rules | service.component#zip.archive::ansible@*->local.machine |
| Scenario | service.component#zip.archive@*->local.machine |
| Component | service.component |
| Artifact | zip.archive |
| Technology | ansible |
| Hosting | * -> local.machine |
| Topology |
Rule #82¶
| Attribute | Value |
|---|---|
| Number | 82 |
| Rules | service.component#zip.archive::terraform@*->local.machine |
| Scenario | service.component#zip.archive@*->local.machine |
| Component | service.component |
| Artifact | zip.archive |
| Technology | terraform |
| Hosting | * -> local.machine |
| Topology |
Rule #83¶
| Attribute | Value |
|---|---|
| Number | 83 |
| Rules | service.component#zip.archive::ansible@*->remote.machine |
| Scenario | service.component#zip.archive@*->remote.machine |
| Component | service.component |
| Artifact | zip.archive |
| Technology | ansible |
| Hosting | * -> remote.machine |
| Topology |
Rule #84¶
| Attribute | Value |
|---|---|
| Number | 84 |
| Rules | service.component#zip.archive::terraform@*->remote.machine |
| Scenario | service.component#zip.archive@*->remote.machine |
| Component | service.component |
| Artifact | zip.archive |
| Technology | terraform |
| Hosting | * -> remote.machine |
| Topology |
Rule #85¶
| Attribute | Value |
|---|---|
| Number | 85 |
| Rules | service.component#zip.archive::ansible@gcp.appengine |
| Scenario | service.component#zip.archive@gcp.appengine |
| Component | service.component |
| Artifact | zip.archive |
| Technology | ansible |
| Hosting | gcp.appengine |
| Topology |
Rule #86¶
| Attribute | Value |
|---|---|
| Number | 86 |
| Rules | service.component#zip.archive::terraform@gcp.appengine |
| Scenario | service.component#zip.archive@gcp.appengine |
| Component | service.component |
| Artifact | zip.archive |
| Technology | terraform |
| Hosting | gcp.appengine |
| Topology |
Rule #87¶
| Attribute | Value |
|---|---|
| Number | 87 |
| Rules | software.component#apt.package::ansible@*->local.machine |
| Scenario | software.component#apt.package@*->local.machine |
| Component | software.component |
| Artifact | apt.package |
| Technology | ansible |
| Hosting | * -> local.machine |
| Topology |
Rule #88¶
| Attribute | Value |
|---|---|
| Number | 88 |
| Rules | software.component#apt.package::terraform@*->local.machine |
| Scenario | software.component#apt.package@*->local.machine |
| Component | software.component |
| Artifact | apt.package |
| Technology | terraform |
| Hosting | * -> local.machine |
| Topology |
Rule #89¶
| Attribute | Value |
|---|---|
| Number | 89 |
| Rules | software.component#apt.package::ansible@*->remote.machine |
| Scenario | software.component#apt.package@*->remote.machine |
| Component | software.component |
| Artifact | apt.package |
| Technology | ansible |
| Hosting | * -> remote.machine |
| Topology |
Rule #90¶
| Attribute | Value |
|---|---|
| Number | 90 |
| Rules | software.component#apt.package::terraform@*->remote.machine |
| Scenario | software.component#apt.package@*->remote.machine |
| Component | software.component |
| Artifact | apt.package |
| Technology | terraform |
| Hosting | * -> remote.machine |
| Topology |
Rule #91¶
| Attribute | Value |
|---|---|
| Number | 91 |
| Rules | software.component#tar.archive::ansible@*->local.machine |
| Scenario | software.component#tar.archive@*->local.machine |
| Component | software.component |
| Artifact | tar.archive |
| Operations | create, delete |
| Technology | ansible |
| Hosting | * -> local.machine |
| Topology |
Rule #92¶
| Attribute | Value |
|---|---|
| Number | 92 |
| Rules | software.component#tar.archive::terraform@*->local.machine |
| Scenario | software.component#tar.archive@*->local.machine |
| Component | software.component |
| Artifact | tar.archive |
| Operations | create, delete |
| Technology | terraform |
| Hosting | * -> local.machine |
| Topology |
Rule #93¶
| Attribute | Value |
|---|---|
| Number | 93 |
| Rules | software.component#tar.archive::ansible@*->remote.machine |
| Scenario | software.component#tar.archive@*->remote.machine |
| Component | software.component |
| Artifact | tar.archive |
| Operations | create, delete |
| Technology | ansible |
| Hosting | * -> remote.machine |
| Topology |
Rule #94¶
| Attribute | Value |
|---|---|
| Number | 94 |
| Rules | software.component#tar.archive::terraform@*->remote.machine |
| Scenario | software.component#tar.archive@*->remote.machine |
| Component | software.component |
| Artifact | tar.archive |
| Operations | create, delete |
| Technology | terraform |
| Hosting | * -> remote.machine |
| Topology |
Rule #95¶
| Attribute | Value |
|---|---|
| Number | 95 |
| Rules | software.component#zip.archive::ansible@*->local.machine |
| Scenario | software.component#zip.archive@*->local.machine |
| Component | software.component |
| Artifact | zip.archive |
| Operations | create, delete |
| Technology | ansible |
| Hosting | * -> local.machine |
| Topology |
Rule #96¶
| Attribute | Value |
|---|---|
| Number | 96 |
| Rules | software.component#zip.archive::terraform@*->local.machine |
| Scenario | software.component#zip.archive@*->local.machine |
| Component | software.component |
| Artifact | zip.archive |
| Operations | create, delete |
| Technology | terraform |
| Hosting | * -> local.machine |
| Topology |
Rule #97¶
| Attribute | Value |
|---|---|
| Number | 97 |
| Rules | software.component#zip.archive::ansible@*->remote.machine |
| Scenario | software.component#zip.archive@*->remote.machine |
| Component | software.component |
| Artifact | zip.archive |
| Operations | create, delete |
| Technology | ansible |
| Hosting | * -> remote.machine |
| Topology |
Rule #98¶
| Attribute | Value |
|---|---|
| Number | 98 |
| Rules | software.component#zip.archive::terraform@*->remote.machine |
| Scenario | software.component#zip.archive@*->remote.machine |
| Component | software.component |
| Artifact | zip.archive |
| Operations | create, delete |
| Technology | terraform |
| Hosting | * -> remote.machine |
| Topology |
Rule #99¶
| Attribute | Value |
|---|---|
| Number | 99 |
| Rules | virtual.machine#machine.image::ansible@openstack.provider |
| Scenario | virtual.machine#machine.image@openstack.provider |
| Component | virtual.machine |
| Artifact | machine.image |
| Technology | ansible |
| Hosting | openstack.provider |
| Topology |
Rule #100¶
| Attribute | Value |
|---|---|
| Number | 100 |
| Rules | virtual.machine#machine.image::terraform@openstack.provider |
| Scenario | virtual.machine#machine.image@openstack.provider |
| Component | virtual.machine |
| Artifact | machine.image |
| Technology | terraform |
| Hosting | openstack.provider |
| Topology |
Reference Implementation¶
We provide a reference implementation for this specification as part of OpenTOSCA Vintner. OpenTOSCA Vintner is a TOSCA preprocessing and management layer. The project is open-source, licensed under Apache-2.0, and publicly available at GitHub.
Acknowledgments¶
This specification is developed for the purpose of research by the Institute of Software Engineering (ISTE) and the Institute of Architecture of Application Systems (IAAS) of the University of Stuttgart, Germany. The development is partially funded by the German Federal Ministry for Economic Affairs and Climate Action (BMWK) as part of the Software-Defined Car (SofDCar) project (19S21002).
Correspondence¶
Please address all correspondence concerning this specification to Miles Stötzner <miles.stoetzner@iste.uni-stuttgart.de, https://miles.stoetzner.de>.
Disclaimer of Warranty¶
Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.