Preparing for deployment

Perform the following tasks before deploying BMC Helix IT Operations Management. When you perform the installation, individual components might require additional pre-installation steps. 

Related topics

TaskActionReference
1

Install and set up BMC Discovery version 23.3.

Important: BMC Discovery is optional if you are deploying only BMC Helix Continuous Optimization

Setting up BMC Discovery
2

Make sure that 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 Open link  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.
For example, for the Network Time Protocol (NTP), use the following command on each node:

yum -y install ntp ntpdate ntp-doc; chkconfig ntpd on; ntpdate pool.ntp.org ; systemctl start ntpd

If you are using BMC Helix Operations Management and BMC Discovery, make sure that you use the same NTP server for both applications.

  • CentCentOS, RHEL, CoreOS, Fedora:

    ~]# yum install ntp

    See  the Red Hat documentation Open link  for the post-installation steps.

  • Ubuntu:

    apt-get install ntp

    See  the Ubuntu documentation Open link  for the post-installation steps.

  • Photon OS (VMWare)

    tdnf install ntp

    See  the VMWare documentation Open link  for the post-installation steps.

Rancher documentation Open link

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 before deployment. 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 Open link

6Create the NFS StorageClass and Block StorageClass in the cluster.
  • For an example NFS StorageClass provider, see  the Kubernetes documentation here Open link .

  • For an example Block StorageClass provider, see  the Ceph CSI documentation here Open link .

7Download the deployment manager and container images required to perform the deployment.Downloading the deployment manager
8Prepare for password encryption.Preparing for password encryption
9

Configure the deployment files.

Configuration file settings

10

To enable BMC Helix Logging, go to helix-on-prem-deployment-manager-<release_version>/ configs /deployment.config file, set the value of the parameter BMC_HELIX_LOGGING as yes.

If you do not want to enable BMC Helix Logging, perform the following steps

  1. In the helix-on-prem-deployment-manager-<release_version>/ configs /deployment.config file, make sure the value of the parameter BMC_HELIX_LOGGING is set to no.
  2. In the helix-on-prem-deployment-manager/configs/bmc-helix-logging.config file, set the values of the parameter ENABLE_LOG_SHIPPER_IN_PODS to false.

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.

Using custom CA signed certificates

12Deploy the NGINX Ingress controller.Deploying and configuring the ingress controller for OpenShift or Kubernetes
13

Create a namespace for deploying BMC Helix IT Operations Management. 

After creating the namespace, make sure that you have restricted the pod security admission enabled for the namespace.  If you are an BMC Helix IT Service Management customer, then you must make sure that you have baseline pod security admission enabled for the namespace. 

Creating a namespace for deploying BMC Helix IT Operations Management

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: 

Important

Set the URLs in the Domain Name Server (DNS) and make sure that the URLs are unique.

Property in the infra.config fileFormat to create URLsExampleTo be set in the load balancer
LB_HOST

<a unique string>.$DOMAIN

Validate the URL on any internet browser. The following message should appear:

Default backend - 404

LB_HOST=lb.mydomain.bmc.comYES
TMS_LB_HOST<a unique string>.$DOMAINTMS_LB_HOST=tms.mydomain.bmc.comYES
KIBANA_LB_HOST<a unique string>.$DOMAINKIBANA_LB_HOST= kibana-private-poc.mydomain.bmc.comYES
MINIO_LB_HOST<a unique string>.$DOMAINMINIO_LB_HOST = minio.mydomain.bmc.comYES

MINIO_API_LB_HOST 

<a unique string>.$DOMAINMINIO_API_LB_HOST= minio-api.mydomain.bmc.comYES
Tenant URL$COMPANY_NAME-$TENANT_TYPE-$ENVIRONMENT.$DOMAINpurplekite-tyrion-dev.mydomain.bmc.comYES

(BMC Helix Operations Management only) BMC Discovery URL

$COMPANY_NAME-disc-$TENANT_TYPE-$ENVIRONMENT.$DOMAIN

purplekite-disc-tyrion-dev.mydomain.bmc.comNO

BMC Helix Continuous Optimization URL

$COMPANY_NAME-optimize-$TENANT_TYPE-$ENVIRONMENT.$DOMAINpurplekite-optimize-tyrion-dev.mydomain.bmc.comNO

Was this page helpful? Yes No Submitting... Thank you

Comments