Hi Matt, Adding from a more practical experience side of things (I've implemented a rather large ACS deployed across 17 datacenters around the world, so had quite a bit of experience with that)
Assuming it's VMWare I'd echo what Rohit said and say that you really should go with dVS. I'd say that as a minimum you need 4x10Gb NICS (ideally 25Gb nowadays, but that depends a lot on the kind of traffic you expect to have). I'd segregate those in at least two dVSs, one for storage and one for everything else. If you have more NICs then you could go for 3 dVSs using the 3rd to segregate customer traffic from management. I'd recommend keeping it a simple L2 topology and let ESX load-balance the uplinks (the default policy works pretty well), you can then decide if you want to use active/backup or active/active per portgroup. You'll need to choose VLANs for Storage and for Management and let ACS know those when creating your Zone, all over VLANs come from your public IP ranges and the VLAN range you select for customers, those will automatically created by ACS. In your Storage dVS you'll end up with just a couple port groups and in the other you'll have a mgmt. portgroup (where your mgmt. VMKernel interface reside) plus one for each public IP range you add to ACS plus one per customer network. One thing to take in consideration is how many virtual ports your switch can handle (depends highly on make/model), if you setup 4k VLANs on all ports in a 48port switch you can easily overload it, so testing the limits of your switch is rather important. Hope this answers your question, if you have any more questions I'll be happy to help, I have some diagrams I can share, just need to find them. Cheers, Alex -----Original Message----- From: Rohit Yadav <rohit.ya...@shapeblue.com> Sent: 27 April 2021 12:25 To: users@cloudstack.apache.org Subject: Re: VMware vSS, vDS recommended setups Hi Matt, Our best practices, networking and use of VMware are documented here: http://docs.cloudstack.apache.org/en/latest/conceptsandterminology/choosing_deployment_architecture.html#best-practices http://docs.cloudstack.apache.org/en/latest/conceptsandterminology/network_setup.html http://docs.cloudstack.apache.org/en/latest/installguide/hypervisor/vsphere.html In newer environments, I would suggest considering distributed vswitches. All other best practices of vSphere/vCenter should in general be followed, as CloudStack VMware plugin orchestrates most of things via vCenter (vim apis). If you're just starting out exploring CloudStack and haven't fixed on storage and hypervisor, you may want to consider your requirements and CloudStack support: http://docs.cloudstack.apache.org/en/latest/conceptsandterminology/choosing_deployment_architecture.html#choosing-a-hypervisor Regards. ________________________________ From: Matthew Ritchie <ritchie...@gmail.com> Sent: Tuesday, April 27, 2021 15:38 To: users@cloudstack.apache.org <users@cloudstack.apache.org> Subject: VMware vSS, vDS recommended setups Hi all, Is there a best practices guide regarding the VMware vSS and vDS setup for Cloudstack? Maybe some recommendations based on your experience for the number of physical NICs on hosts, VLAN ID settings for the port groups, number of port groups etc.? I understand that this is a generic question and the answer depends on one's plan, but I am thinking that there may exist a minimal recommended setup as a baseline. best, Matt PS Maybe it is a good idea to gather some baseline network setups for the supported hosts... rohit.ya...@shapeblue.com www.shapeblue.com 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK @shapeblue
