Deploying BMC Helix IT Operations Management in a multitenant environment


With a multitenant architecture, you can share your infrastructure among multiple tenants. A multitenant architecture maximizes resource usage and helps make scaling easy. Multitenancy is supported in BMC Helix IT Operations Management version 22.2.01 or later.

You can onboard multiple tenants by using the tctl utility. For more information, see Administering.

Important

You cannot offboard any tenant.

Perform the following steps to deploy BMC Helix IT Operations Management in a multitenant environment.

Step

Action

1.

2.

 

To deploy BMC Discovery

Important

Ensure that you deploy separate BMC Discovery for each tenant.

  1. Configure the following settings for each BMC Discovery :

    Setting

    Description or reference

    Name resolution settings

    For more information, see Configuring name resolution settings.

    Time synchronization

    For more information, see Performing time synchronization.

    DNS alias of BMC Discovery

    Format:
    <company>-disc-<type>-<environment>.<domain>

    DNS entries for the new tenant

    Format:

    <company>-<type>-<environment>.<domain>

    Only for custom signed or self-signed certificates

    Import the CA bundle into the single sign-on settings of the appliance. This action ensures that an error does not occur when the appliance makes the SSL connection to BMC Helix Single Sign-on.

  2. In the deployment namespace, open the smart-graph-tenant-config configmap for editing by running the following command:

    kubectl -n <namespace> edit cm smart-graph-tenant-config

     

  3. In the data section, add the new BMC Discovery address.

    smarGraph_configmap_edit.png
     
  4. (Optional) Add additional tenants to the configmap as follows:

    smarGraph_configmap_moreClient.png
     

    Important

    While adding additional tenants to the configmap make sure that each tenant name is distinct.

 

To deploy BMC Helix IT Operations Management in a multitenant environment

  1. Log in to tctl.
    For more information, see Downloading-and-configuring-the-tctl-utility.
  2. Create the tenant.json file by using the following details as an example. This file is used to create the tenant. 

    {
    "name": "york",
    "email": "jsmith@bmc.com",
    "first_name": "John",
    "last_name": "Smith",
    "phone": "1234678",
    "environment": "small",
    "domain": "york-private-small.bmc.com",
    "description": "York",
    "country": "United Kingdom",
    "login_id": "hannah_admin",
    "type": "LICENSE"
    }

    For information about the parameters in this file, see Configuration-file-settings.

    Important

    In this file, the property "name" refers to the "TENANT_NAME".

  3. Run the following command to create a new tenant:

    tctl create tenant -f tenant.json

    The email address specified in the JSON file receives the following emails:

    • An email for license activation
    • An email for setting the password for the initial user
  4. Activate the tenant by using link in the email that was just received.
  5. Verify the active services.
    1. To see the list of services that are activated on the new tenant, run the following command:

      tctl get tenant-service <tenant_id>    

      Expected output:

      get_tenant_service.png

    2. To activate a service on the new tenant, run the following command:

      tctl activate service <tenant_id> -i <service-id>

      For example, the following image shows the Discovery service activated for the new tenant:

      activate_service_discov.png
       

Important

While registering a multi-tenant:

  • The value of Tenant type and Domain name cannot be changed. These values are assigned when the URL is created. If the user wants to assign a new value for Tenant type and Domain name, a new URL must be created.
  • The user can change the values of Company name and Environment.

 

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*