Reply to Message

View discussion in a popup

Replying to:
peetz
Leadership
Leadership

Greetings,

I cannot really answer your question, but I want to comment on what you did and ask some questions back ...

Regarding your scripting work for adjusting resource pools I want to make you aware of a new feature in vSphere 7.0 called "scalable shares". It is supposed to solve exactly the problem that you now solve by scripting and continuously adjusting the resource pools' shares. Read about it here: vSphere 7 DRS Scalable Shares Deep Dive - frankdenneman.nl  and here: vSphere 7 and DRS Scalable Shares, how are they calculated? | Yellow Bricks

Regarding your stretched cluster setup and assigning VMs to sites with DRS rules I'm curious to know why exactly you are doing this. vSAN stretched clusters use a feature called "Read locality" that ensures that their storage read accesses are always served from the site that they are running on (to avoid reads crossing the site-interlink). Storage write access will always cross the site-interlink, because each objects need to be stored on both sites (unless you use PFTT=0 to have a VM stored on one site only). Read about read locality here: Read Locality in vSAN Stretched Clusters | vSAN Stretched Cluster Guide | VMware​. Of course there are other reasons why you might want to pin your VMs to one site, but avoiding site-interlink traffic is not one of them.

As I said I cannot answer your question how resource pools are affected by DRS affinity rules, but let's try to pull in the gurus on this subject: FDenneman01  and depping Can you comment, Frank or Duncan?

- Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de