Space banner

   

This documentation supports an earlier version of BMC Helix IT Operations Management on-premises deployment.

To view the documentation for the latest version, select 22.4 from the Product version picker.

Deploying BMC Helix IT Operations Management

Use the container images to deploy BMC Helix IT Operations Management.

You can deploy the following BMC Helix IT Operations Management components in the stand-alone mode:

  • BMC Helix Operations Management
  • BMC Helix AIOps with BMC Helix Intelligent Automation
  • BMC Helix Continuous Optimization



Before you begin

Create a namespace and configure the ingress controller before deploying the product. Perform the following actions:

Important

Only the root user is supported for deployment.


  1. Create a namespace by running the following command. The namespace must be a DNS-1123 label. That is, it must consist of lowercase alphanumeric characters or '-', and must start and end with an alphanumeric character.

    kubectl create ns <namespace>
  2. Verify that nothing is installed in the namespace in which you plan to deploy the product. Perform the following steps:

    1. Run the following command:

      kubectl get all -n <namespace_created_earlier_in_this_procedure>
    2. Make sure that the following message is displayed:

      No resources found.

  3. Configure the ingress controller. Perform the following steps:

    1. Identify the configmap name by running the following command:

      kubectl get all -n <ingress_nginx_namespace>
    2. Change the configmap name to use the configmap in your environment by running the following command:

      kubectl edit cm <ingress_nginx_configmap> -n  <ingress_nginx_namespace>
      
      data:
        enable-underscores-in-headers: "true"
        proxy-body-size: 250m
        server-name-hash-bucket-size: "1024"
        ssl-redirect: "false"
        use-forwarded-headers: "true"
  4. If you are deploying BMC Helix AIOps, perform the following steps:
    1. Open the ../products/aiops/aiops.json file.
    2. Under the ml-model-mgmt-service entry, replace image.org with containers[0].org.
    3. Save and close the file.

For EFK logging

Create a namespace called bmc-helix-logging by using the following command:

kubectl create ns bmc-helix-logging

The Elasticsearch, FluentD, and Kibana services are installed in this namespace. These services are required to access logs from the pods that are running on BMC Helix Platform.

For more information, see Preparing for BMC Helix logging.


To deploy BMC Helix IT Operations Management

  1. Log in to the controller or bastion machine from where the Kubernetes cluster is accessible.

  2. Go to the directory where you downloaded the deployment manager from the EPD and give the execute permission to the helix-on-prem-deployment-manager-<release_version>.sh file.

  3. Self-extract the deployment manager. Run the following command:

    ./helix-on-prem-deployment-manager-<release_version>.sh
    
    
    cd helix-on-prem-deployment-manager

  4. Configure the properties in the helix-on-prem-deployment-manager/config/infra.config and helix-on-prem-deployment-manager/config/deployment.config files.

    For more information, see the following topics:

  5. To install the product, run the following command:

    ./deployment-manager.sh

    To run the deployment in the background, run the following command:

    nohup ./deployment-manager.sh </dev/null &

    To view the logs during installation, run the following command:

    tail -f logs/deployment.log

After the installation, you can see the Elasticsearch, Fluentd, and Kibana pods in the bmc-helix-logging namespace. You can access Kibana with the following URL:

http://<masternodeio>:5601/ 

All installation logs are located in the following directory:

helix-on-prem-deployment-manager/logs


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

Comments