Adding observability test cases and tekton files

.tekton/README.md

@@ -36,7 +36,7 @@ https://cloud.ibm.com/devops/getting-started?env_id=ibm:yp:eu-de
 3. cluster_prefix
 4. zone
 5. resource_group
-6. cluster_id
+6. cluster_name
 7. reservation_id
 
 For additional assistance, contact the project maintainers.

.tekton/hpcaas/hpcaas-pr-pipeline/hpcaas-pipeline-git-pr-status.yaml

@@ -60,7 +60,7 @@ spec:
     - name: management_image_name
       description: Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster management nodes. By default, the solution uses a RHEL88 base image with additional software packages mentioned [here](https://cloud.ibm.com/docs/ibm-spectrum-lsf#create-custom-image). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering.
       default: ""
-    - name: cluster_id
+    - name: cluster_name
       description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifer for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
       default: ""
     - name: reservation_id
@@ -223,8 +223,8 @@ spec:
           value: $(params.login_image_name)
         - name: management_image_name
           value: $(params.management_image_name)
-        - name: cluster_id
-          value: $(params.cluster_id)
+        - name: cluster_name
+          value: $(params.cluster_name)
         - name: reservation_id
           value: $(params.reservation_id)
         - name: pr-revision
@@ -279,8 +279,8 @@ spec:
           value: $(params.login_image_name)
         - name: management_image_name
           value: $(params.management_image_name)
-        - name: cluster_id
-          value: $(params.cluster_id)
+        - name: cluster_name
+          value: $(params.cluster_name)
         - name: reservation_id
           value: $(params.reservation_id)
         - name: pr-revision

.tekton/hpcaas/hpcaas-pr-pipeline/listener-git-pr-status.yaml

@@ -55,7 +55,7 @@ spec:
     - name: management_image_name
       description: Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster management nodes. By default, the solution uses a RHEL88 base image with additional software packages mentioned [here](https://cloud.ibm.com/docs/ibm-spectrum-lsf#create-custom-image). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering.
       default: ""
-    - name: cluster_id
+    - name: cluster_name
       description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifer for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
       default: ""
     - name: reservation_id
@@ -169,8 +169,8 @@ spec:
             value: $(params.login_image_name)
           - name: management_image_name
             value: $(params.management_image_name)
-          - name: cluster_id
-            value: $(params.cluster_id)
+          - name: cluster_name
+            value: $(params.cluster_name)
           - name: reservation_id
             value: $(params.reservation_id)
           - name: us_east_zone

.tekton/hpcaas/hpcaas-regression-pipeline/hpcaas-pipeline-git-trigger.yaml

@@ -62,7 +62,7 @@ spec:
     - name: management_image_name
       description: Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster management nodes. By default, the solution uses a RHEL88 base image with additional software packages mentioned [here](https://cloud.ibm.com/docs/ibm-spectrum-lsf#create-custom-image). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering.
       default: ""
-    - name: cluster_id
+    - name: cluster_name
       description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifer for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
       default: ""
     - name: reservation_id
@@ -214,8 +214,8 @@ spec:
           value: $(params.login_image_name)
         - name: management_image_name
           value: $(params.management_image_name)
-        - name: cluster_id
-          value: $(params.cluster_id)
+        - name: cluster_name
+          value: $(params.cluster_name)
         - name: reservation_id
           value: $(params.reservation_id)
         - name: us_east_zone
@@ -288,8 +288,8 @@ spec:
           value: $(params.login_image_name)
         - name: management_image_name
           value: $(params.management_image_name)
-        - name: cluster_id
-          value: $(params.cluster_id)
+        - name: cluster_name
+          value: $(params.cluster_name)
         - name: reservation_id
           value: $(params.reservation_id)
         - name: us_east_zone
@@ -362,8 +362,8 @@ spec:
           value: $(params.login_image_name)
         - name: management_image_name
           value: $(params.management_image_name)
-        - name: cluster_id
-          value: $(params.cluster_id)
+        - name: cluster_name
+          value: $(params.cluster_name)
         - name: reservation_id
           value: $(params.reservation_id)
         - name: us_east_zone
@@ -436,8 +436,8 @@ spec:
           value: $(params.login_image_name)
         - name: management_image_name
           value: $(params.management_image_name)
-        - name: cluster_id
-          value: $(params.cluster_id)
+        - name: cluster_name
+          value: $(params.cluster_name)
         - name: reservation_id
           value: $(params.reservation_id)
         - name: us_east_zone

.tekton/hpcaas/hpcaas-regression-pipeline/listener-git-trigger.yaml

@@ -62,7 +62,7 @@ spec:
     - name: management_image_name
       description: Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster management nodes. By default, the solution uses a RHEL88 base image with additional software packages mentioned [here](https://cloud.ibm.com/docs/ibm-spectrum-lsf#create-custom-image). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering.
       default: ""
-    - name: cluster_id
+    - name: cluster_name
       description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifer for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
       default: ""
     - name: reservation_id
@@ -182,8 +182,8 @@ spec:
             value: $(params.login_image_name)
           - name: management_image_name
             value: $(params.management_image_name)
-          - name: cluster_id
-            value: $(params.cluster_id)
+          - name: cluster_name
+            value: $(params.cluster_name)
           - name: reservation_id
             value: $(params.reservation_id)
           - name: us_east_zone
@@ -259,8 +259,8 @@ spec:
       value: $(params.management_image_name)
     - name: reservation_id
       value: $(params.reservation_id)
-    - name: cluster_id
-      value: $(params.cluster_id)
+    - name: cluster_name
+      value: $(params.cluster_name)
     - name: us_east_zone
       value: $(params.us_east_zone)
     - name: us_east_cluster_id
@@ -350,7 +350,7 @@ spec:
       value: $(event.ref)
     - name: resource_group
       value: $(event.ref)
-    - name: cluster_id
+    - name: cluster_name
       value: $(event.ref)
     - name: compute_image_name_rhel
       value: $(event.ref)

.tekton/hpcaas/hpcaas_task/hpcaas-task-infra-rhel.yaml

@@ -53,7 +53,7 @@ spec:
     - name: login_image_name
       description: Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster login node. By default, the solution uses a RHEL 8-6 OS image with additional software packages mentioned [here](https://cloud.ibm.com/docs/hpc-spectrum-LSF#create-custom-image). The solution also offers, Ubuntu 22-04 OS base image (hpcaas-lsf10-ubuntu2204-compute-v2). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering.
       default: ""
-    - name: cluster_id
+    - name: cluster_name
       description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifer for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
       default: ""
     - name: reservation_id
@@ -127,6 +127,10 @@ spec:
             name: $(params.continuous-delivery-context-secret)
             key: $(params.ibmcloud-apikey-secret-key)
             optional: true
+      - name: BUILD_NUMBER
+        valueFrom:
+          fieldRef:
+            fieldPath: metadata.annotations['devops.cloud.ibm.com/build-number']
       - name: PIPELINE_DEBUG
         value: $(params.pipeline-debug)
       - name: REVISION
@@ -141,8 +145,8 @@ spec:
         value: $(params.compute_image_name_rhel)
       - name: login_image_name
         value: $(params.login_image_name)
-      - name: cluster_id
-        value: $(params.cluster_id)
+      - name: cluster_name
+        value: $(params.cluster_name)
       - name: reservation_id
         value: $(params.reservation_id)
       - name: us_east_zone

.tekton/hpcaas/hpcaas_task/hpcaas-task-negative.yaml

@@ -53,7 +53,7 @@ spec:
     - name: login_image_name
       description: Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster login node. By default, the solution uses a RHEL 8-6 OS image with additional software packages mentioned [here](https://cloud.ibm.com/docs/hpc-spectrum-LSF#create-custom-image). The solution also offers, Ubuntu 22-04 OS base image (hpcaas-lsf10-ubuntu2204-compute-v2). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering.
       default: ""
-    - name: cluster_id
+    - name: cluster_name
       description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifer for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
       default: ""
     - name: reservation_id
@@ -127,6 +127,10 @@ spec:
             name: $(params.continuous-delivery-context-secret)
             key: $(params.ibmcloud-apikey-secret-key)
             optional: true
+      - name: BUILD_NUMBER
+        valueFrom:
+          fieldRef:
+            fieldPath: metadata.annotations['devops.cloud.ibm.com/build-number']
       - name: PIPELINE_DEBUG
         value: $(params.pipeline-debug)
       - name: REVISION
@@ -141,8 +145,8 @@ spec:
         value: $(params.compute_image_name_rhel)
       - name: login_image_name
         value: $(params.login_image_name)
-      - name: cluster_id
-        value: $(params.cluster_id)
+      - name: cluster_name
+        value: $(params.cluster_name)
       - name: reservation_id
         value: $(params.reservation_id)
       - name: us_east_zone

.tekton/hpcaas/hpcaas_task/hpcaas-task-pr-rhel.yaml

@@ -51,7 +51,7 @@ spec:
     - name: login_image_name
       description: Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster login node. By default, the solution uses a RHEL 8-6 OS image with additional software packages mentioned [here](https://cloud.ibm.com/docs/hpc-spectrum-LSF#create-custom-image). The solution also offers, Ubuntu 22-04 OS base image (hpcaas-lsf10-ubuntu2204-compute-v2). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering.
       default: ""
-    - name: cluster_id
+    - name: cluster_name
       description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifer for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
       default: ""
     - name: reservation_id
@@ -101,6 +101,10 @@ spec:
             name: $(params.continuous-delivery-context-secret)
             key: $(params.ibmcloud-apikey-secret-key)
             optional: true
+      - name: BUILD_NUMBER
+        valueFrom:
+          fieldRef:
+            fieldPath: metadata.annotations['devops.cloud.ibm.com/build-number']
       - name: PIPELINE_DEBUG
         value: $(params.pipeline-debug)
       - name: PR_REVISION
@@ -120,8 +124,8 @@ spec:
           value: $(params.compute_image_name_rhel)
         - name: login_image_name
           value: $(params.login_image_name)
-        - name: cluster_id
-          value: $(params.cluster_id)
+        - name: cluster_name
+          value: $(params.cluster_name)
         - name: reservation_id
           value: $(params.reservation_id)
         - name: cos_region

.tekton/hpcaas/hpcaas_task/hpcaas-task-pr-ubuntu.yaml

@@ -51,7 +51,7 @@ spec:
     - name: login_image_name
       description: Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster login node. By default, the solution uses a RHEL 8-6 OS image with additional software packages mentioned [here](https://cloud.ibm.com/docs/hpc-spectrum-LSF#create-custom-image). The solution also offers, Ubuntu 22-04 OS base image (hpcaas-lsf10-ubuntu2204-compute-v2). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering.
       default: ""
-    - name: cluster_id
+    - name: cluster_name
       description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifer for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
       default: ""
     - name: reservation_id
@@ -101,6 +101,10 @@ spec:
             name: $(params.continuous-delivery-context-secret)
             key: $(params.ibmcloud-apikey-secret-key)
             optional: true
+      - name: BUILD_NUMBER
+        valueFrom:
+          fieldRef:
+            fieldPath: metadata.annotations['devops.cloud.ibm.com/build-number']
       - name: PIPELINE_DEBUG
         value: $(params.pipeline-debug)
       - name: PR_REVISION
@@ -120,8 +124,8 @@ spec:
           value: $(params.compute_image_name_ubuntu)
         - name: login_image_name
           value: $(params.login_image_name)
-        - name: cluster_id
-          value: $(params.cluster_id)
+        - name: cluster_name
+          value: $(params.cluster_name)
         - name: reservation_id
           value: $(params.reservation_id)
         - name: cos_region

.tekton/hpcaas/hpcaas_task/hpcaas-task-region.yaml

@@ -53,7 +53,7 @@ spec:
     - name: login_image_name
       description: Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster login node. By default, the solution uses a RHEL 8-6 OS image with additional software packages mentioned [here](https://cloud.ibm.com/docs/hpc-spectrum-LSF#create-custom-image). The solution also offers, Ubuntu 22-04 OS base image (hpcaas-lsf10-ubuntu2204-compute-v2). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering.
       default: ""
-    - name: cluster_id
+    - name: cluster_name
       description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifer for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
       default: ""
     - name: reservation_id
@@ -127,6 +127,10 @@ spec:
             name: $(params.continuous-delivery-context-secret)
             key: $(params.ibmcloud-apikey-secret-key)
             optional: true
+      - name: BUILD_NUMBER
+        valueFrom:
+          fieldRef:
+            fieldPath: metadata.annotations['devops.cloud.ibm.com/build-number']
       - name: PIPELINE_DEBUG
         value: $(params.pipeline-debug)
       - name: REVISION
@@ -141,8 +145,8 @@ spec:
         value: $(params.compute_image_name_rhel)
       - name: login_image_name
         value: $(params.login_image_name)
-      - name: cluster_id
-        value: $(params.cluster_id)
+      - name: cluster_name
+        value: $(params.cluster_name)
       - name: reservation_id
         value: $(params.reservation_id)
       - name: us_east_zone