System requirements

Before you deploy the product, make sure that your environment meets the hardware and software requirements.

Container platform

Docker

Container orchestration

The following cluster environments are supported:

• Kubernetes 1.18 or 1.19
• OpenShift 4.6

Package manager

Helm 3.2.3 is supported.

Container host operating system

BMC Helix Operations Management has no specific host operating system requirements and may be deployed on any of the x86_64 GNU/Linux operating systems that support Kubernetes 1.18 or 1.19, including the following operating systems:

• Ubuntu 16.04+
• Debian 9+
• Fedora 25+
• HypriotOS v1.0.1+
• CentOS 7
• RHEL 7
• Photon OS
• CoreOS 7+

BMC has verified the following host operating systems:

• CentOS 7.x
• RHEL 7.x
• Photon OS 3.x

Host operating system Bash shell

Bash Shell 4.2 or later is supported.

Docker registry

Direct access to BMC's Docker Trusted Repository (DTR) at https://containers.bmc.com is available. To obtain the key for the BMC DTR, access the BMC Electronic Product Distribution (EPD) web site with your registered email ID, and download the container shell script. Individual keys are generated for each user ID. 

Load balancer

An F5 load balancer is supported. Any other load balancer with the following capabilities is also supported:

• Support for SSL offloading
• X-Forwarded- Headers Upstream of Ingress is allowed
• Support for reverse Proxy http back to https
• Support for unaltered response redirects

Ingress controller

nginx-ingress-controller 0.32 is supported.

For information about deploying the ingress controller, see Deploying K8 ingress controller for OpenShift or Kubernetes.

Persistent storage

Kubernetes Storage Class that supports high performance IOPS.

Both NFS and Block Storage are required.

Storage performance

• Write & Read Latency 1ms
• Throughput: Write 30 MBPS/Read 80MBPS
• IOPS: Write 5K / Read 15K

User permission

The cluster admin permission is required to deploy the product.

Security certificates

The following security certificates are supported:

• DigiCert
• R3

Other CA or self-signed certificates are not supported.

Additional requirements

In addition to the hardware and software requirements, make sure that your environment meets the following requirements:

• Swap must be turned off.
• BMC DTR token to download the artifacts from containers.bmc.com.
• Https access to containers.bmc.com from the K8s cluster to pull the container images. Add the EPD token to the cluster.
• Trusted CA SSL certificate (client root certificate).

• NFS mount point:

  1. Create a folder under the NFS mount point. Use the resulting complete path to populate the NFS_MOUNT_PATH property in the configs/infra.config during deployment.

  2. Grant permissions on the folder that you created. Use the following commands:
     chown 786:998 <NFS_MOUNT_PATH>
chmod +x <NFS_MOUNT_PATH>
• BMC Discovery 21.05 appliance. For more information, see Setting up a BMC Discovery appliance.
  For installation information, see the  BMC Discovery documentation .
• All nodes configured with static IP.
  

• The following URLs configured in the load balancer and with a DNS entry. The property names will be used in the infra.config and deployment.config files during deployment.
  Make sure that the following URLs are in the same domain.

  Description	Format	Example	Must be configured in the load balancer?	Must have a DNS entry?	File name	Property name
  Host for Helix RSSO	<any unique string>.$DOMAIN	mycomputer.lab.bmc.com	Yes	Yes	configs/infra.config	LB_HOST
  Host for tenant management system	<any unique string>.$DOMAIN	mycomputer.lab.bmc.com	Yes	Yes	configs/infra.config	TMS_LB_HOST
  MinIO storage URL	<any unique string>.$DOMAIN	mycomputer.lab.bmc.com	Yes	Yes	configs/infra.config	MINIO_LB_HOST
  Tenant URL	$COMPANY_NAME-$TENANT_TYPE-$ENVIRONMENT.$DOMAIN	acme-private-poc.lab.bmc.com	Yes	Yes	configs/deployment.config for ENVIRONMENT and configs/infra.config for the others	COMPANY_NAME TENANT_TYPE ENVIRONMENT DOMAIN
  Discovery Appliance URL	$COMPANY_NAME-disc-$TENANT_TYPE-$ENVIRONMENT.$DOMAIN	acme-disc-private-poc.lab.bmc.com	No	Yes	configs/deployment.config for ENVIRONMENT and configs/infra.config for the others	COMPANY_NAME TENANT_TYPE ENVIRONMENT DOMAIN
  Note: $DOMAIN in the format refers to the domain being used. In the examples, it is lab.bmc.com.

Database and data source versions

The BMC Helix Operations Management data lake tier comprises of the following database servers and data sources: