Deploying BMC Helix IT Operations Management
Before you begin
Download the deployment manager, the hotfix itom-drs-predeploy-hotfix-23.2.02.002-2, or the hotfix itom-predeploy-hotfix-23.2.02.002-6.
For more information, see Downloading-the-deployment-manager.
Perform all the steps listed in the Preparing-for-deployment topic.
To apply the hotfix
The following table lists the prerequisites to apply the hotfixes:
Supported Kubernetes versions | Supported Helm version | Hotfix | Description |
---|---|---|---|
1.23.x – 1.25.x | 3.11 | itom-drs-predeploy-hotfix-23.2.02.002-2 | Download and apply the hotfix itom-drs-predeploy-hotfix-23.2.02.002-2 to prevent the certificate issue caused when OpenSSL fails to pull the client root certificate. |
1.24.x – 1.26.x | 3.12 | itom-predeploy-hotfix-23.2.02.002-6 | itom-predeploy-hotfix-23.2.02.002-6 is a cumulative hotfix. |
- Back up the following files:
- helix-on-prem-deployment-manager directory/deployment-manager.sh
- commons/preinstall-checker.sh
- helix-on-prem-deployment-manager directory/configs/infra.config
- (Only if you are applying the hotfix itom-predeploy-hotfix-23.2.02.002-6) configs/helix-chart-version.config
- Copy the hotfix to your workspace directory.
- To extract the contents of the hotfix to the workspace directory, run the following command:
To extract the contents of the itom-drs-predeploy-hotfix-23.2.02.002-2.tar.gz file to the workspace directory, run the following command:
tar -xvf itom-drs-predeploy-hotfix-23.2.02.002-2.tar.gzTo extract the contents of the itom-predeploy-hotfix-23.2.02.002-6.tar.gz file to the workspace directory, run the following command:
tar -xvf itom-predeploy-hotfix-23.2.02.002-6.tar.gzThe deployment-manager.sh, preinstall-checker.sh and infra.config files are replaced.
You can now run the deployment manager.
To deploy BMC Helix IT Operations Management
- Log in to the controller or bastion machine from where the Kubernetes cluster is accessible.
- Configure the properties in the helix-on-prem-deployment-manager/configs/infra.config and helix-on-prem-deployment-manager/configs/deployment.config files.
For more information, see Configuration-file-settings.You can also refer to the following topics for application-specific configurations: Install the product by running the following command:
./deployment-manager.sh
The deployment manager generates a new secret.config and secretkey.json files in the common/certs directory.
The secrets.txt file is deleted.
The deployment manager will now use the secret.config and secretkey.json files for deploying all products.