propose new qualities

OpenTOSCA · Nov 15, 2024 · 073fd54 · 073fd54
1 parent 30b0e8c
commit 073fd54
Show file tree

Hide file tree

Showing 15 changed files with 568 additions and 36 deletions.
diff --git a/examples/unfurl-technology---boutique---plus-maintenance-automated/lib/technology-rules.yaml b/examples/unfurl-technology---boutique---plus-maintenance-automated/lib/technology-rules.yaml
@@ -35,7 +35,7 @@
 - technology: ansible
   component: gcp.service
   hosting: []
-  weight: 1
+  weight: 0
   reason: Ansible provides a declarative module
   details: '"google.cloud.gcp_serviceusage_service" task'
 - technology: terraform
@@ -139,14 +139,14 @@
       - mysql.dbms
       - docker.engine
       - remote.machine
-  weight: 0.5
+  weight: 0.75
   reason: Terraform provides a declarative module. However, Terraform requires an SSH workaround. Ansible is more specialized.
 - technology: ansible
   component: mysql.database
   hosting:
       - mysql.dbms
       - gcp.cloudsql
-  weight: 0.5
+  weight: 0
   reason: Primary use case due to the specialization of Ansible. However, need to install and handle GCP CloudSQL Proxy, while the corresponding Terraform module already provides this.
 - technology: terraform
   component: mysql.database
@@ -174,7 +174,7 @@
   hosting:
       - mysql.dbms
       - kubernetes.cluster
-  weight: 0
+  weight: 0.25
   reason: Ansible is more specialized.
 - technology: ansible
   component: mysql.database
@@ -263,7 +263,7 @@
   artifact: dbms.image
   hosting:
       - gcp.cloudsql
-  weight: 1
+  weight: 0
   reason: Primary use case due to the specialization of Ansible.
   details: '"google.cloud.gcp_sql_instance" and "google.cloud.gcp_sql_user" tasks'
 - technology: terraform
@@ -334,7 +334,7 @@
   component: object.storage
   hosting:
       - gcp.cloudstorage
-  weight: 1
+  weight: 0
   reason: Primary use case due to the specialization of Ansible.
 - technology: terraform
   component: object.storage
@@ -388,7 +388,7 @@
       - minio.server
       - docker.engine
       - remote.machine
-  weight: 0.5
+  weight: 0.75
   reason: Terraform provides a declarative module. However, Terraform requires an SSH workaround. Ansible is more specialized.
 - technology: ansible
   component: object.storage
@@ -409,7 +409,7 @@
   hosting:
       - minio.server
       - kubernetes.cluster
-  weight: 0
+  weight: 0.25
   reason: Ansible is more specialized.
 - technology: ansible
   component: redis.server
@@ -470,7 +470,7 @@
   artifact: cache.image
   hosting:
       - gcp.memorystore
-  weight: 1
+  weight: 0
   reason: Primary use case due to the specialization of Ansible.
 - technology: terraform
   component: redis.server

diff --git a/examples/unfurl-technology---boutique---plus-maintenance-automated/scripts/study-009.txt b/examples/unfurl-technology---boutique---plus-maintenance-automated/scripts/study-009.txt
diff --git a/examples/unfurl-technology---industry---plus-maintenance-automated/lib/technology-rules.yaml b/examples/unfurl-technology---industry---plus-maintenance-automated/lib/technology-rules.yaml
@@ -35,7 +35,7 @@
 - technology: ansible
   component: gcp.service
   hosting: []
-  weight: 1
+  weight: 0
   reason: Ansible provides a declarative module
   details: '"google.cloud.gcp_serviceusage_service" task'
 - technology: terraform
@@ -139,14 +139,14 @@
       - mysql.dbms
       - docker.engine
       - remote.machine
-  weight: 0.5
+  weight: 0.75
   reason: Terraform provides a declarative module. However, Terraform requires an SSH workaround. Ansible is more specialized.
 - technology: ansible
   component: mysql.database
   hosting:
       - mysql.dbms
       - gcp.cloudsql
-  weight: 0.5
+  weight: 0
   reason: Primary use case due to the specialization of Ansible. However, need to install and handle GCP CloudSQL Proxy, while the corresponding Terraform module already provides this.
 - technology: terraform
   component: mysql.database
@@ -174,7 +174,7 @@
   hosting:
       - mysql.dbms
       - kubernetes.cluster
-  weight: 0
+  weight: 0.25
   reason: Ansible is more specialized.
 - technology: ansible
   component: mysql.database
@@ -263,7 +263,7 @@
   artifact: dbms.image
   hosting:
       - gcp.cloudsql
-  weight: 1
+  weight: 0
   reason: Primary use case due to the specialization of Ansible.
   details: '"google.cloud.gcp_sql_instance" and "google.cloud.gcp_sql_user" tasks'
 - technology: terraform
@@ -334,7 +334,7 @@
   component: object.storage
   hosting:
       - gcp.cloudstorage
-  weight: 1
+  weight: 0
   reason: Primary use case due to the specialization of Ansible.
 - technology: terraform
   component: object.storage
@@ -388,7 +388,7 @@
       - minio.server
       - docker.engine
       - remote.machine
-  weight: 0.5
+  weight: 0.75
   reason: Terraform provides a declarative module. However, Terraform requires an SSH workaround. Ansible is more specialized.
 - technology: ansible
   component: object.storage
@@ -409,7 +409,7 @@
   hosting:
       - minio.server
       - kubernetes.cluster
-  weight: 0
+  weight: 0.25
   reason: Ansible is more specialized.
 - technology: ansible
   component: redis.server
@@ -470,7 +470,7 @@
   artifact: cache.image
   hosting:
       - gcp.memorystore
-  weight: 1
+  weight: 0
   reason: Primary use case due to the specialization of Ansible.
 - technology: terraform
   component: redis.server