feat: IBM Spectrum LSF DA

BREAKING CHANGE: IBM Spectrum LSF deployable architecture: Spectrum LSF enables High-Performance Computing (HPC) clusters by using LSF as the HPC scheduling software. This solution employs a deployable architecture to provision and configure IBM Cloud resources.
IBM Cloud Activity Tracker Event Routing: This is a platform service which manages the auditing events at the account-level by configuring targets and routes that define where auditing data is routed.
Multiple static worker node profile support: This solution supports the creation of static compute nodes by leveraging different instance type profiles based on resource requirements.
PAC High Availability (HA) support: This allows LSF Application Center to run on all deployed management nodes, use a cross availability zone instance of the IBM Cloud® Database for MySQL as the backend database, and use an IBM Cloud® Application Load Balancer for VPC (ALB) as the VPC load balancer.
IBM Storage Scale support: By using Storage Scale as your storage solution, you first set up a Storage Scale cluster, and then integrate a list of values from the Storage Scale deployment with the IBM Spectrum LSF cluster deployment. This provides more performance and scalability than standard file storage solutions.
IBM Cloud Monitoring: This is a cloud-native and container-intelligence management system that is included as part of your IBM Cloud architecture.
IBM Cloud Logs: This is a scalable logging service which is designed to persist logs while providing users with robust capabilities for querying, tailing, and visualizing their logs efficiently.

Co-authored-by: Nupur Goyal <nupurgoyal@Nupurs-MacBook-Pro.local>

Author: nupurg-ibm

.secrets.baseline

@@ -1,9 +1,9 @@
 {
   "exclude": {
-    "files": "go.sum|^.secrets.baseline$",
+    "files": "acceptance-test/package-lock.json|test/go.sum|go.sum|^.secrets.baseline$",
     "lines": null
   },
-  "generated_at": "2024-04-08T15:16:34Z",
+  "generated_at": "2025-02-12T12:53:44Z",
   "plugins_used": [
     {
       "name": "AWSKeyDetector"

.tekton/README.md

@@ -1,5 +1,5 @@
 
-# IBM Cloud HPC - OnePipeline(Tekton)
+# IBM Cloud HPC - Tekton
 
 ## Prerequisites
 
@@ -24,7 +24,7 @@ https://cloud.ibm.com/devops/getting-started?env_id=ibm:yp:eu-de
 6. On Build your own toolchain page, provide Toolchain name, Resource Group, Region
 7. Click Create it will create pipeline.
 
-## Actions on the OnePipeline
+## Actions on the Tekton
 
 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 the PR_TEST and OTHER_TEST testcases

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

@@ -18,7 +18,7 @@ spec:
     - name: pr-revision
       description: the commit id/sha for the PullRequest
       default: ""
-    - name: git-access-token
+    - name: git_access_token
       description: the token to access the git repository for the clone operations
       default: ""
     - name: properties-file
@@ -57,6 +57,9 @@ 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: 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
       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: ""
@@ -72,6 +75,24 @@ spec:
     - name: cos_instance_crn
       description: The cos instance crn.
       default: ""
+    - name: cos_api_key
+      description: The cos account api key.
+      default: ""
+    - name: hpc_custom_reports_repo
+      description: The HPC custom reports storage repository.
+      default: ""
+    - name: hpc_custom_reports_branch
+      description: The HPC custom reports storage repository branch.
+      default: "main"
+    - name: git_user_name
+      description: The git user name.
+      default: ""
+    - name: git_user_email
+      description: The git user email.
+      default: ""
+    - name: solution
+      description: Provide the value for the solution that is needed for the support of lsf and HPC.
+      default: "hpcaas"
   workspaces:
     - name: pipeline-ws
   tasks:
@@ -109,8 +130,8 @@ spec:
           value: $(params.pr-branch)
         - name: pr-revision
           value: $(params.pr-revision)
-        - name: git-access-token
-          value: $(params.git-access-token)
+        - name: git_access_token
+          value: $(params.git_access_token)
         - name: directory-name
           value: $(params.directory-name)
         - name: properties-file
@@ -168,6 +189,8 @@ spec:
           value: $(params.resource_group)
         - name: pr-revision
           value: $(params.pr-revision)
+        - name: solution
+          value: $(params.solution)
     - name: wes-hpc-da-rhel-pr
       runAfter: [git-clone, pre-requisites-install, ssh-key-creation]
       taskRef:
@@ -178,6 +201,8 @@ spec:
       params:
         - name: repository
           value: $(params.repository)
+        - name: git_access_token
+          value: $(params.git_access_token)
         - name: pipeline-debug
           value: $(params.pipeline-debug)
         - name: ssh_keys
@@ -196,6 +221,8 @@ spec:
           value: $(params.compute_image_name_ubuntu)
         - name: login_image_name
           value: $(params.login_image_name)
+        - name: management_image_name
+          value: $(params.management_image_name)
         - name: cluster_id
           value: $(params.cluster_id)
         - name: reservation_id
@@ -208,6 +235,18 @@ spec:
           value: $(params.cos_bucket)
         - name: cos_instance_crn
           value: $(params.cos_instance_crn)
+        - name: cos_api_key
+          value: $(params.cos_api_key)
+        - name: hpc_custom_reports_repo
+          value: $(params.hpc_custom_reports_repo)
+        - name: hpc_custom_reports_branch
+          value: $(params.hpc_custom_reports_branch)
+        - name: git_user_name
+          value: $(params.git_user_name)
+        - name: git_user_email
+          value: $(params.git_user_email)
+        - name: solution
+          value: $(params.solution)
     - name: wes-hpc-da-ubuntu-pr
       runAfter: [git-clone, pre-requisites-install, ssh-key-creation]
       taskRef:
@@ -218,6 +257,8 @@ spec:
       params:
         - name: repository
           value: $(params.repository)
+        - name: git_access_token
+          value: $(params.git_access_token)
         - name: pipeline-debug
           value: $(params.pipeline-debug)
         - name: ssh_keys
@@ -236,6 +277,8 @@ spec:
           value: $(params.compute_image_name_ubuntu)
         - name: login_image_name
           value: $(params.login_image_name)
+        - name: management_image_name
+          value: $(params.management_image_name)
         - name: cluster_id
           value: $(params.cluster_id)
         - name: reservation_id
@@ -248,6 +291,18 @@ spec:
           value: $(params.cos_bucket)
         - name: cos_instance_crn
           value: $(params.cos_instance_crn)
+        - name: cos_api_key
+          value: $(params.cos_api_key)
+        - name: hpc_custom_reports_repo
+          value: $(params.hpc_custom_reports_repo)
+        - name: hpc_custom_reports_branch
+          value: $(params.hpc_custom_reports_branch)
+        - name: git_user_name
+          value: $(params.git_user_name)
+        - name: git_user_email
+          value: $(params.git_user_email)
+        - name: solution
+          value: $(params.solution)
     - name: ssh-key-deletion
       runAfter: [wes-hpc-da-rhel-pr, wes-hpc-da-ubuntu-pr]
       taskRef:
@@ -260,8 +315,16 @@ spec:
           value: $(params.pipeline-debug)
         - name: pr-revision
           value: $(params.pr-revision)
-    - name: inspect-wes-hpc-infra-log
-      runAfter: [git-clone, set-git-pr-running, wes-hpc-da-rhel-pr, wes-hpc-da-ubuntu-pr]
+        - name: solution
+          value: $(params.solution)
+    - name: error-check-on-hpcaas-pr-infra-log
+      runAfter:
+        [
+          git-clone,
+          set-git-pr-running,
+          wes-hpc-da-rhel-pr,
+          wes-hpc-da-ubuntu-pr,
+        ]
       workspaces:
         - name: workspace
           workspace: pipeline-ws
@@ -271,27 +334,27 @@ spec:
             description: The git repo will be cloned onto the volume backing this workspace
             mountPath: /artifacts
         steps:
-          - name: error-check-on-pr-rhel-log
+          - name: error-pr-rhel-suite
             onError: continue
             image: icr.io/continuous-delivery/pipeline/pipeline-base-ubi:latest
             workingDir: "/artifacts"
             command: ["/bin/bash", "-c"]
             args:
               - |
                 #!/bin/bash
-                LOG_FILE="pipeline-pr-rhel*"
+                LOG_FILE_NAME="hpcaas-pr-rhel-suite.json"
                 source .tekton/scripts/issue_track.sh
-                issue_track "${LOG_FILE}" "PR"
-          - name: error-check-on-pr-ubuntu-log
+                issue_track "${LOG_FILE_NAME}" "PR"
+          - name: error-pr-ubuntu-suite
             image: icr.io/continuous-delivery/pipeline/pipeline-base-ubi:latest
             workingDir: "/artifacts"
             command: ["/bin/bash", "-c"]
             args:
               - |
                 #!/bin/bash
-                LOG_FILE="pipeline-pr-ubuntu*"
+                LOG_FILE_NAME="hpcaas-pr-ubuntu-suite.json"
                 source .tekton/scripts/issue_track.sh
-                issue_track "${LOG_FILE}" "PR"
+                issue_track "${LOG_FILE_NAME}" "PR"
   finally:
     - name: set-git-commit-status
       taskRef:
@@ -309,6 +372,6 @@ spec:
         - name: description
           value: $(params.description)
         - name: state
-          value: "$(tasks.inspect-wes-hpc-infra-log.status)"
+          value: "$(tasks.error-check-on-hpcaas-pr-infra-log.status)"
         - name: pipeline-debug
           value: $(params.pipeline-debug)

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

@@ -6,7 +6,7 @@ metadata:
   name: triggertemplate-git-pr-status
 spec:
   params:
-    - name: git-access-token
+    - name: git_access_token
       description: the token to access the git repository for the clone operations
     - name: repository
       description: The git repo
@@ -52,6 +52,9 @@ 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: 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
       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: ""
@@ -94,6 +97,24 @@ spec:
     - name: cos_instance_crn
       description: The cos instance crn.
       default: ""
+    - name: cos_api_key
+      description: The cos account api key.
+      default: ""
+    - name: hpc_custom_reports_repo
+      description: The HPC custom reports storage repository.
+      default: ""
+    - name: hpc_custom_reports_branch
+      description: The HPC custom reports storage repository branch.
+      default: "main"
+    - name: git_user_name
+      description: The git user name.
+      default: ""
+    - name: git_user_email
+      description: The git user email.
+      default: ""
+    - name: solution
+      description: Provide the value for the solution that is needed for the support of lsf and HPC.
+      default: "hpcaas"
   resourcetemplates:
     - apiVersion: v1
       kind: PersistentVolumeClaim
@@ -114,8 +135,8 @@ spec:
         pipelineRef:
           name: pipeline-git-pr-status
         params:
-          - name: git-access-token
-            value: $(params.git-access-token)
+          - name: git_access_token
+            value: $(params.git_access_token)
           - name: repository
             value: $(params.repository)
           - name: branch
@@ -146,6 +167,8 @@ spec:
             value: $(params.compute_image_name_ubuntu)
           - name: login_image_name
             value: $(params.login_image_name)
+          - name: management_image_name
+            value: $(params.management_image_name)
           - name: cluster_id
             value: $(params.cluster_id)
           - name: reservation_id
@@ -174,12 +197,22 @@ spec:
             value: $(params.cos_bucket)
           - name: cos_instance_crn
             value: $(params.cos_instance_crn)
+          - name: cos_api_key
+            value: $(params.cos_api_key)
+          - name: hpc_custom_reports_repo
+            value: $(params.hpc_custom_reports_repo)
+          - name: hpc_custom_reports_branch
+            value: $(params.hpc_custom_reports_branch)
+          - name: git_user_name
+            value: $(params.git_user_name)
+          - name: git_user_email
+            value: $(params.git_user_email)
+          - name: solution
+            value: $(params.solution)
         workspaces:
           - name: pipeline-ws
             persistentVolumeClaim:
               claimName: $(params.triggerName)-$(uid)-pvc
-...
-
 ---
 apiVersion: tekton.dev/v1beta1
 kind: TriggerBinding
@@ -199,8 +232,6 @@ spec:
       value: "$(event.pull_request.head.sha)"
     - name: triggerName
       value: "github-pullrequest"
-...
-
 ---
 apiVersion: tekton.dev/v1beta1
 kind: EventListener
@@ -212,4 +243,3 @@ spec:
         name: triggerbinding-git-pr-status-github-pr
       template:
         name: triggertemplate-git-pr-status
-...