Deploying cluster nodes

Last Updated : Jun 23, 2022 |

About this task

The steps in this procedure use the vSphere web client connected to vCenter.

Before you begin

  • Deploy the Cluster Control Manager.

  • Collect the required node information needed for deployment.

Procedure

  1. Log in to vCenter using an account that has deployment permissions.
  2. Access the target folder for deploying the cluster node virtual machines.
  3. Use the Cluster Node OVA to deploy either one VM (for a non-HA single-node deployment) or three or more VMs (for an HA deployment with three master nodes).

    Use the values from the table of required node information that you collected.

    A centralized storage array with thin provisioning and no encryption is required.

    Note:

    After deploying one cluster node, if you have user permission in vCenter, you can clone and customize the second and third cluster nodes. For the third cluster node, the disk size must be set to 0 as only the 2 controller or master nodes require disk. If you have used clone option, you need to delete the 2nd disk (360GB) associated with your third cluster node virtual machine.

  4. Repeat the deployment instructions for the remaining cluster nodes, if applicable.

    CPU and Memory resource values can be found in deployment properties worksheet in the Avaya_Oceana_Application_Deployment_<ReleaseNumber>.xlsm spreadsheet. Hard disk size depends on the number of agents selected in the deployment spreadsheet.

    You can manually set the resource footprint by editing the VM settings after OVA is deployed. Ensure cluster node 1 and 2 are deployed with correct disk size for disk 2. This value must match the Disk Storage Requirement(GB) value on the deployment properties sheet in the Avaya_Oceana_Application_Deployment_<ReleaseNumber>.xlsm spreadsheet.

    Important:

    Cluster Node 3 Disk 2 must be set to 0.

  5. If you are deploying with high availability enabled, you must create an anti-affinity rule in vCenter for the cluster nodes.

    Create the anti-affinity rule before powering on the VMs after initial OVA deployment to prevent a hot migration.

    1. Navigate to your vCenter cluster.
    2. In the Configure tab, select Configuration > VM/Host rules > Create VM/Host Rule.
    3. Create a name for the anti-affinity rule.
    4. Select enable rule.
    5. Type Separate Virtual Machines.
    6. Add all the cluster nodes to the list.
    7. Click OK.
  6. Power on all cluster node VMs.

    All CSP cluster node VMs are powered on and available for solution deployment.