Deploy BMC Helix IT Operations Management in a multitenant environment
Scenario 1: Service providers with multiple customers sharing one BMC Helix Platform
A service provider organization wants to install BMC Helix IT Operations Managementfor three of their customers. A system administrator creates a shared cluster to host the production environments on the same BMC Helix Platform services. The administrator uses the tctl utily and creates three BMC Helix Platform tenants: Tenant 1, Tenant 2, and Tenant 3. The administrator then installs BMC Helix IT Operations Management for each tenant by using the deployment pipelines.
Data segregation and access are enforced. Data for each tenant in the BMC Helix Platform is not visible to other tenants. The logging data stored in Elasticsearch can be filtered by the tenant, but is not segregated.
This configuration is suitable where customers of the service provider do not have access to the Kubernetes administration functions.
The following image shows the BMC Helix IT Service Management installation on a multitenant BMC Helix Platform:
Scenario 2: Non-production systems sharing one BMC Helix Platform
An organization wants to install BMC Helix IT Operations Management for in-house development and testing. A system administrator creates a cluster to host the development and QA environments that use the same BMC Helix Platform services. The administrator uses the tctl utility and creates two BMC Helix Platform tenants: Dev Tenant and QA Tenant. The administrator then installs BMC Helix IT Operations Management for the Dev Tenant and the QA Tenant by using deployment pipelines.
The following image shows a shared development and QA cluster: