DRS and Anti-affinity Rules in VMware vSphere Environments

Overview

This guide explains the DRS Configuration and Anti-affinity rules within VMware vSphere environments.

DRS VM overrides is used to disable vMotion for controllers, and anti-affinity is used to prevent the placement of the controllers or SEs on the same hypervisor.

Note: DRS and anti-affinity rules are not applicable for Avi Vantage installed on VMC on AWS.

Configuring DRS within VMware vSphere Environments

It is recommended to set DRS to Manual/Disabled for Controllers. The cluster HA will take care of the control plane. However, DRS can vMotion multiple controllers at the same time, hence it has to be disabled for Controllers.

Note: Although vMotion for the SEs is supported, it is recommended to use the host and datastore scoping along with virtual service migration functionality native to the platform.

Configuring DRS for Avi Service Engines and Controllers

It is recommended to create a DRS rule/exception (VM Overrides) to exclude the SEs from vMotion. It can only be created after the SE VMs have been created. The DRS rule does not accept a partial match, so the full name of the SE VM needs to be used (once the SE VM has been created).

Configuring Anti-Affinity Rules for Avi Service Engines and Controllers

You should use an anti-affinity host rules to avoid controllers or service engines share the same hypervisor.