A compute cluster is a combination of sites managed by a regional or central site.


  1. Click Domains under Infrastructure Automation.
  2. Click the Compute Cluster icon.
  3. Click Add.

    The Add Domain page appears.

  4. On the Add Domain page, provide the required information.
  5. To enable the provisioning of the site, click the button corresponding to Enabled. You cannot perform any operation on a disabled site.




    The name of the site.

    Minimum number of hosts

    Minimum number of hosts required for the site. The number of hosts cannot be less than 4 or more than 64.

    Select Host Profile

    Select the host profile from the drop-down list. The selected Host profile gets associated with each host in the compute cluster domain.

    Parent Site

    The management or workload domain that manages the cluster. Select from the drop-down menu.


    The location of the compute cluster.


    Enter the keyword to search a location.


    Latitude of the compute cluster location. The details are automatically added when you select the location. You can also modify the latitude manually.


    Longitude of the compute cluster location. The details are automatically added when you select the location. You can also modify the longitude manually.


    You can modify the service settings and the proxy settings for each site. These configurations override the global configuration available in Global Configuration tab on Configuration page. For more details on service and proxy parameters, see Configure Global Settings.

    vSphere SSO Domain is available for local settings and not for global settings. To configure the vSphere SSO Domain for a domain, enable the Override and enter the required information in the corresponding Override Value.


    The default value of vSphere SSO Domain is vsphere.local.


    Not applicable. The compute cluster uses the licenses of parent site.


    • For a compute cluster, you can activate the NSX services. For certain workloads, if you do not require these services, you can deactivate these services.

    • To use the network services of the parent site, click the Share Transport Zones With Parent button.

    • You can use the vSAN or localstore. Select the value from the drop-down menu.

    Click Enabled button to activate or deactivate the Networking or Storage services.

  6. You can add new CSI categories or use the existing categories from the VMware VSphere server. You can also create tags corresponding to the CSI categories. To add the CSI Categories information, add the required information under Settings.
    • To configure the CSI Categories, enable the Override for the CSI Tagging under Settings, and Override Value.

    • Once added, you cannot edit or remove the CSI configuration.

    • For a vSAN disabled compute cluster, ensure that the CSI Zone tag name must contain {hostname}. For example, <text_identifier>-{hostname}.



    Use Existing

    Whether to use the existing categories set in the underlying the VMware VSphere server. Click the corresponding button to activate or deactivate the option.


    When using the Use Existing, ensure that you provide the values for both the region and the zone categories as set in the underlying VMware vSphere server.

    • When creating a Zone category in VMware VSphere, choose Hosts and Clusters under Associable Object Types.

    • When creating a Region category in VMware VSphere, choose Datacentre under Associable Object Types.


    The CSI category for the data center.


    The CSI category for the compute clusters or hosts.

    CSI Region Tag

    The CSI tagging for the data center.

    CSI Zone Tag

    The CSI tagging for the compute clusters or hosts.

  7. Add the Switch Configuration information. Click plus icon to add more switches and uplinks.




    The name of the switch.


    Select the network interface card (NIC) for the compute cluster under Uplinks.


    A cell site requires a minimum of two NICs to communicate. The uplinks must match the actual configuration across all ESXi servers.

  8. Add the Networks information.
    • For vMotion and vSAN, the IP pool should be equal to the total number of ESXi hosts. If you do not provision the appliances, vSAN, nsxHostOverlay, nsxEdgeOverlay, uplinks are optional.

    • You can click + sign under Networks to create additional VLAN or overlay network to connect with additional applications.




    The name of the network.

    Segment Type

    Segment type of the network. Select the value from the list.

    Network Type

    The type of the network.


    The switch details that the sites use for network access.


    VLAN ID for the network.


    MTU length (in bytes) for the network.

    Prefix Length

    Prefix the length for each packet for the network.

    Gateway Address

    The gateway address for the network.

  9. (Optional) Add the Appliance Overrides information. Ensure that the appliance names match the actual names entered in DNS. If they do not match, you can change the name.

    For NSX-Edge cluster configuration:

    • To override the Edge form factor, select the Size from the drop-down menu.

    • To override the HA, select Tier0Mode from the drop-down menu.

    • You can override the values of vSAN NFS and NSX Edge Cluster for the compute cluster and deactivate the deployment of vSAN NFS and NSX Edge Cluster for the compute cluster.




    Whether to override the current values.

    Appliance Type

    The type of the appliance.


    The name of the appliance.

    Name Override

    The new name of the appliance to override the previous name of appliance.

    IP Index

    IP index of the appliance. The value is the fourth octet of the IP address. The initial three octets are populated from the network address provided in the domain.

    VMware Telco Cloud Automation uses IP index to calculate the IP address of the appliance. It adds the IP Index to the base address of the management network to obtain the IP address of the appliance.


    The IP index depends on management subnet prefix length. Ensure that you provide IP index values within the IP range dictated by that subnet prefix length. For example, if you use the subnet prefix length of 24, then the subnet has 254 IPs. Hence, the IP index value cannot exceed 254. If you use the prefix length of 27 or 28, then the subnet has 30 or 14 IPs, respectively. The IP index values must then not exceed 30 or 14, respectively. Ensure that you check the values before adding the IP index.


    Whether the appliance is enabled and available for operations.