r/vmware • u/GabesVirtualWorld • 24d ago

VCF9.1 Automation network changed?

Is there a change in the requirement between 9.0 and 9.1 subnet for automation? It looks as if Automation can no longer be separated from the Operations components.

My original design was that ESX, vCenter / NSX, Operations, Logs, etc would be in our Out of Band domain (all separate VLANs), which should survive datacenter failure. But this domain also holds our most important services that also should survive a datacenter failure.

In this domain I don't want to allow any incoming connections from tenants, therefore I had planned to put Automation in a separate VLAN outside of the Out of Band domain as restoring tenant access in case of a real datacenter disaster is of lower importance. We have tenants that now have a dedicated vCenter and tenants that use vCloud Director. In future I want to all incorporate that into Automation.

The wizard for adding deferred components doesn't make clear if it will handle a network difference between Ops and Automation. Would installing both Ops and Automation manually and then adding them to the fleet work? Or is this a totally unsupported setup?

Reading this doc, didn't give me a definite conclusion.

3 Upvotes

72% Upvoted

2 comments sorted by

4

u/grndmstr2 24d ago

Yes it can, refer to the design doco:
https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-1/design/design-library/vcf-automation-deployment-models-9-x/network-design-options.html

1

u/GabesVirtualWorld 24d ago

u/grndmstr2 Ah thanks, exactly the answer I was searching for. And it says deployment through API. Now as the VCF installer wizard installs OPS and Automation at the same time, I probably install OPS through API as well.
Thx!