When VCF Management Services (VCFMS) was introduced in VCF 9.1.0, its virtual machine sizing was optimized to accommodate the largest optional Day-N service. This reduced the likelihood of requiring a rollout to a larger VM size as additional services were enabled. However, for environments that did not deploy these optional Day-N services, some VCFMS virtual machines could be larger than necessary.

With VCF 9.1.1, VCFMS sizing has been optimized for the initial Day-0 deployment. In addition, individual VCFMS components have been further right-sized to ensure that each service reserves only the resources it requires, improving overall resource utilization. For example, a Simple (non-HA) deployment, you will now have one less VCFMS Worker Node (12 vCPU / 24GB memory).

It is important to note that the right-sized VCFMS worker nodes and component sizing are automatically applied for new VCF 9.1.1 deployments, but they are not automatically applied to existing deployments that are upgraded to VCF 9.1.1.

With that said, users who upgrade to VCF 9.1.1 can still realize the benefits of the reduced VCFMS footprint by running a post-upgrade script that produces the same end state as a new VCF 9.1.1 deployment. For those interested, you can also use the VCF Inspector Fling which will include the post-upgrade script workflow, so you can simply perform that using that tool as well.
[Read more...]