Updating main branch with the latest contents of private repo develop branch

.catalog-onboard-pipeline.yaml

@@ -2,13 +2,13 @@
 apiVersion: v1
 offerings:
 # below is an example of a Deployable Architecture (DA) solution
-- name: terraform-ibm-modules-terraform-ibm-hpc-ad6e71e # must match the offering name in the ibm_catalog.json
+- name: deploy-arch-ibm-hpc # must match the offering name in the ibm_catalog.json
   kind: solution
-  catalog_id: fe9d2e76-5ada-44af-821f-b437dcc80f71
-  offering_id: 468c5a1c-1f1d-4e5a-b5b3-ec646b1bd298
+  catalog_id: 8611e025-10b2-488e-8261-a7f584a5114b
+  offering_id: bf3c07f8-5a62-4289-8ea0-94dbb2b410e6
   # list all of the variations (flavors) you have included in the ibm_catalog.json
   variations:
-    - name: advanced
+    - name: Cluster-with-LSF-v10.1.0.14
       mark_ready: false # have pipeline mark as visible if validation passes
       install_type: fullstack # ensure value matches what is in ibm_catalog.json (fullstack or extension)
       destroy_resources_on_failure: false # defaults to false if not specified so resources can be inspected to debug failures during validation

.gitignore

@@ -15,6 +15,7 @@ crash.log
 # to change depending on the environment.
 #
 *.tfvars
+*.ini
 
 # Ignore files for local testing
 test.tf
@@ -51,3 +52,6 @@ terraform.rc
 
 # Visual Studio Code
 .vscode/
+
+# tweaks used locally
+localtweak__*.tf

.secrets.baseline

@@ -3,7 +3,7 @@
     "files": "go.sum|^.secrets.baseline$",
     "lines": null
   },
-  "generated_at": "2023-12-09T05:22:51Z",
+  "generated_at": "2024-04-08T15:16:34Z",
   "plugins_used": [
     {
       "name": "AWSKeyDetector"

.tekton/README.md

@@ -0,0 +1,42 @@
+
+# IBM Cloud HPC - OnePipeline(Tekton)
+
+## Prerequisites
+
+Ensure the following are configured on your DevOps:
+
+- **IBM Cloud Account**
+- **Continuous Delivery**
+- **Access role with resource_group**
+
+## Link for setup DevOps
+```
+https://cloud.ibm.com/devops/getting-started?env_id=ibm:yp:eu-de
+```
+
+## Set up Your Go Project
+
+1. Login to IBMCloud
+2. Navigate to Navigation Menu on Left hand side and expand. Then go to DevOps → Toolchains
+3. On the Toolchain page select Resource Group and Location where Toolchain has to create
+4. Click Create toolchain and it will redirect to Create a Toolchain page
+5. After successfull redirect to Toolchain Template collections, select Build your own toolchain
+6. On Build your own toolchain page, provide Toolchain name, Resource Group, Region
+7. Click Create it will create pipeline.
+
+## Actions on the OnePipeline
+
+1. When PR raised to the develop branch from feature branch, pipeline with trigger and it will run PR_TEST related testcases on top of feature branch
+2. When Commit/Push happens to develop branch, pipeline will trigger and it will run all PR_TEST and OTHER_TEST testcases
+
+### Setup required parameters to run pipeline
+
+1. ibmcloud-api
+2. ssh_keys
+3. cluster_prefix
+4. zones
+5. resource_group
+6. cluster_id
+7. reservation_id
+
+For additional assistance, contact the project maintainers.

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

@@ -0,0 +1,170 @@
+---
+apiVersion: tekton.dev/v1beta1
+kind: TriggerTemplate
+args: [--allow-multiple-documents]
+metadata:
+  name: triggertemplate-git-pr-status
+spec:
+  params:
+    - name: git-access-token
+      description: the token to access the git repository for the clone operations
+    - name: repository
+      description: The git repo
+      default: " "
+    - name: branch
+      description: the branch for the git repo
+    - name: directory-name
+      default: "."
+    - name: pr-repository
+      description: The source git repo for the PullRequest
+      default: " "
+    - name: pr-branch
+      description: The source branch for the PullRequest
+      default: " "
+    - name: pr-revision
+      description: the commit id/sha for the PullRequest
+      default: " "
+    - name: triggerName
+      default: "git-pr-process"
+    - name: pipeline-debug
+      default: "0"
+    - name: ssh_keys
+      default: ""
+      description: List of names of the SSH keys that is configured in your IBM Cloud account, used to establish a connection to the IBM Cloud HPC bastion and login node. Ensure that the SSH key is present in the same resource group and region where the cluster is being provisioned. If you do not have an SSH key in your IBM Cloud account, create one by according to [SSH Keys](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys).
+    - name: zones
+      default: ""
+      description: IBM Cloud zone names within the selected region where the IBM Cloud HPC cluster should be deployed. Two zone names are required as input value and supported zones for eu-de are eu-de-2, eu-de-3 and for us-east us-east-1, us-east-3. The management nodes and file storage shares will be deployed to the first zone in the list. Compute nodes will be deployed across both first and second zones, where the first zone in the list will be considered as the most preferred zone for compute nodes deployment. [Learn more](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-in-a-different-region#get-zones-using-the-cli).
+    - name: cluster_prefix
+      description: Prefix that is used to name the IBM Cloud HPC cluster and IBM Cloud resources that are provisioned to build the IBM Cloud HPC cluster instance. You cannot create more than one instance of the IBM Cloud HPC cluster with the same name. Ensure that the name is unique.
+      default: cicd-wes
+    - name: resource_group
+      description: Resource group name from your IBM Cloud account where the VPC resources should be deployed. Note. If the resource group value is set as null, automation creates two different RG with the name (workload-rg and service-rg). For additional information on resource groups, see [Managing resource groups](https://cloud.ibm.com/docs/account?topic=account-rgs).
+      default: Default
+    - name: remote_allowed_ips
+      default: ""
+      description: Comma-separated list of IP addresses that can access the IBM Cloud HPC cluster instance through an SSH interface. For security purposes, provide the public IP addresses assigned to the devices that are authorized to establish SSH connections (for example, [\"169.45.117.34\"]). To fetch the IP address of the device, use [https://ipv4.icanhazip.com/](https://ipv4.icanhazip.com/).
+    - name: compute_image_name_rhel
+      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 dynamic compute nodes. 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-v1). 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: compute_image_name_ubuntu
+      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 dynamic compute nodes. 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-v1). 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: 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
+      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
+      description: Ensure that you have received the reservation ID from IBM technical sales. Reservation ID is a unique identifier to distinguish different IBM Cloud HPC service agreements. It must start with a letter and can only contain letters, numbers, hyphens (-), or underscores (_).
+      default: ""
+    - name: us_east_reservation_id
+      description: Ensure that you have received the reservation ID from IBM technical sales. Reservation ID is a unique identifier to distinguish different IBM Cloud HPC service agreements. It must start with a letter and can only contain letters, numbers, hyphens (-), or underscores (_).
+      default: ""
+    - name: eu_de_reservation_id
+      description: Ensure that you have received the reservation ID from IBM technical sales. Reservation ID is a unique identifier to distinguish different IBM Cloud HPC service agreements. It must start with a letter and can only contain letters, numbers, hyphens (-), or underscores (_).
+      default: ""
+    - name: us_south_reservation_id
+      description: Ensure that you have received the reservation ID from IBM technical sales. Reservation ID is a unique identifier to distinguish different IBM Cloud HPC service agreements. It must start with a letter and can only contain letters, numbers, hyphens (-), or underscores (_).
+      default: ""
+  resourcetemplates:
+    - apiVersion: v1
+      kind: PersistentVolumeClaim
+      metadata:
+        name: $(params.triggerName)-$(uid)-pvc
+      spec:
+        resources:
+          requests:
+            storage: 5Gi
+        volumeMode: Filesystem
+        accessModes:
+          - ReadWriteOnce
+    - apiVersion: tekton.dev/v1beta1
+      kind: PipelineRun
+      metadata:
+        name: $(params.triggerName)-$(uid)
+      spec:
+        pipelineRef:
+          name: pipeline-git-pr-status
+        params:
+          - name: git-access-token
+            value: $(params.git-access-token)
+          - name: repository
+            value: $(params.repository)
+          - name: branch
+            value: $(params.branch)
+          - name: pr-repository
+            value: $(params.pr-repository)
+          - name: pr-branch
+            value: $(params.pr-branch)
+          - name: pr-revision
+            value: $(params.pr-revision)
+          - name: pipeline-debug
+            value: $(params.pipeline-debug)
+          - name: directory-name
+            value: $(params.directory-name)
+          - name: ssh_keys
+            value: $(params.ssh_keys)
+          - name: zones
+            value: $(params.zones)
+          - name: cluster_prefix
+            value: $(params.cluster_prefix)
+          - name: resource_group
+            value: $(params.resource_group)
+          - name: remote_allowed_ips
+            value: $(params.remote_allowed_ips)
+          - name: compute_image_name_rhel
+            value: $(params.compute_image_name_rhel)
+          - name: compute_image_name_ubuntu
+            value: $(params.compute_image_name_ubuntu)
+          - name: login_image_name
+            value: $(params.login_image_name)
+          - name: cluster_id
+            value: $(params.cluster_id)
+          - name: reservation_id
+            value: $(params.reservation_id)
+          - name: us_east_reservation_id
+            value: $(params.us_east_reservation_id)
+          - name: eu_de_reservation_id
+            value: $(params.eu_de_reservation_id)
+          - name: us_south_reservation_id
+            value: $(params.us_south_reservation_id)
+        workspaces:
+          - name: pipeline-ws
+            persistentVolumeClaim:
+              claimName: $(params.triggerName)-$(uid)-pvc
+...
+
+---
+apiVersion: tekton.dev/v1beta1
+kind: TriggerBinding
+metadata:
+  name: triggerbinding-git-pr-status-github-pr
+spec:
+  params:
+    - name: repository
+      value: "$(event.pull_request.base.repo.clone_url)"
+    - name: branch
+      value: "$(event.pull_request.base.ref)"
+    - name: pr-repository
+      value: "$(event.pull_request.head.repo.clone_url)"
+    - name: pr-branch
+      value: "$(event.pull_request.head.ref)"
+    - name: pr-revision
+      value: "$(event.pull_request.head.sha)"
+    - name: triggerName
+      value: "github-pullrequest"
+...
+
+---
+apiVersion: tekton.dev/v1beta1
+kind: EventListener
+metadata:
+  name: eventlistener-git-pr-status-github-pr
+spec:
+  triggers:
+    - binding:
+        name: triggerbinding-git-pr-status-github-pr
+      template:
+        name: triggertemplate-git-pr-status
+...