Preparing for deployment
Task | Action | Reference |
1 | Install and set up BMC Discovery version 24.3 or later. Important: BMC Discovery is optional if you are deploying only BMC Helix Continuous Optimization. | |
2 | Make sure all the ports that are related to Kubernetes are open on the worker and master nodes. Use the following command for each port firewall-cmd --permanent --add-port portNumber/tcp | Kubernetes documentation and the Kubernetes cluster management documentation for the application that you are using. |
3 | Install the time synchronization protocol to synchronize the date and time on all nodes.
yum -y install ntp ntpdate ntp-doc; chkconfig ntpd on; ntpdate pool.ntp.org ; systemctl start ntpd
| |
4 | Set up a private Docker registry if your Kubernetes cluster does not have internet access. We recommend Harbor. | Setting-up-a-Harbor-registry-in-a-local-network-and-synchronizing-it-with-BMC-DTR Setting-up-a-Harbor-registry-in-an-air-gapped-environment-and-synchronizing-it-with-BMC-DTR |
5 | For all worker nodes, set the sysctl -w vm.max_map_count parameter to 262144. Run the following commands on the worker node: sysctl -w vm.max_map_count=262144 echo vm.max_map_count=262144 > /etc/sysctl.d/es-custom.conf | Elasticsearch documentation |
6 | Create the NFS StorageClass and Block StorageClass in the cluster. |
|
7 | Download the deployment manager and container images required to perform the deployment. | Downloading-the-deployment-manager |
8 | Prepare for password encryption. | Preparing-for-password-encryption |
9 | Enable the nodes for data lake components | Enabling the nodes for data lake components |
10 | Configure the deployment files. | Configuration-file-settings |
11 | If you want to deploy BMC Helix ITOM with custom CA certificates, add the custom CA certificates in the helix-on-prem-deployment-manager/commons/certs/custom_cacert.pem. | |
12 | Deploy the NGINX Ingress controller. Starting with BMC Helix ITOM version 24.3, we support NGINX Plus Ingress Controller. You can use either the enterprise version of the NGINX Plus Ingress Controller or the open-source version. | |
13 | Create a namespace for deploying BMC Helix IT Operations Management. | |
14 | Install the Health Check Tool to identify potential issues that may impact the installation of BMC Helix products. | Installing the Health Check Tool |
Creating URLs to access BMC Helix IT Operations Management applications
Before starting the deployment, we recommend that you create the following URLs by using the values that you set in the infra.config file:
Where to go from here
- Deploying-BMC-Helix-IT-Operations-Management.
- Deploying-BMC-Helix-IT-Operations-Management-in-an-Amazon-Elastic-Kubernetes-Service-cluster.
- Deploying-BMC-Helix-IT-Operations-Management-in-an-Azure-Kubernetes-Service-cluster.
- Deploying-BMC-Helix-IT-Operations-Management-in-a-Google-Kubernetes-Engine-cluster.
- Deploying-BMC-Helix-IT-Operations-Management-in-a-multitenant-environment.