Hi Corey, Correct, you create 3 physical networks. ACS knows which VDS to use based on the traffic label (as per last email).
Cheers Alex -----Original Message----- From: Corey, Mike <mike.co...@sap.com.INVALID> Sent: 11 May 2021 16:09 To: users@cloudstack.apache.org Subject: RE: VMware VDS Specifics Thanks Alex, So what I've have now are 4 VDS. When I'm going through the Add Zone wizard, do I create 3 physical networks - one for each traffic type - Guest, Management, Storage? If so, how do I link the CloudStack physical network to the correct VMware VDS? "When adding a zone, you need to set up one or more physical networks. Each network corresponds to a NIC on the hypervisor. Each physical network can carry one or more types of traffic, with certain restrictions on how they may be combined. Add or remove one or more traffic types onto each physical network." From: Alex Mattioli <alex.matti...@shapeblue.com> Sent: Tuesday, May 11, 2021 4:57 AM To: users@cloudstack.apache.org Subject: RE: VMware VDS Specifics Hi Mike, ACS doesn't touch the uplink assignments already created. But you can't really tell it which uplinks to set in a portgroup, so when it creates the Storage portgroup it might not use the desired uplinks, it will be using the default uplinks set on ESX. You could wait for ACS to create the portgroup, check which uplinks it uses and then change the others accordingly (annoying, I know) The way I'd carve those 8 NICs would be: VDS _Management - 2 uplinks, with your management portgroups and management vmk VDS_Guest - 2 uplinks, for ACS to create guest networks. VDS_Storage - 2 uplinks, with your NFS vmk and ACS's storage portgroup and your vMotion vmk (which you can then set to use whatever uplinks are not the default, you can check after ACS has created the storage portgroup) Alternatively you can create a 4th VDS, something like VDS_OOB - 2 uplinks with the vMotion vmk. (In my case I've used that in production for monitoring and backups, but could be for vMotion as well). Hope that helps, Btw, what bandwidth do you have on those links? Cheers, Alex From: Corey, Mike <mike.co...@sap.com<mailto:mike.co...@sap.com>> Sent: 10 May 2021 22:15 To: Alex Mattioli <alex.matti...@shapeblue.com<mailto:alex.matti...@shapeblue.com>> Subject: VMware VDS Specifics Hi Alex, I'm about to run through my first 4.15 zone setup but want to make sure I have my VDS lined up. I have 8 uplinks broken out: (2) vmk0, (2) vmotion, (2) NFS, (2) guest traffic. I have two VDS configured; one for "management" port groups and one for guest VM traffic port groups. On the management VDS, there are six uplinks and I have uplink assignments for each of the kernel traffic types...meaning I segregate vmk0 to 2 uplinks, NFS is on 2 other uplinks, and vmotion on 2 other uplinks. The guest vm VDS is simple with two uplinks assigned to the public and private port groups. My concern/question is how will CloudStack handle this layout and will it "respect" how I have the VDS port group to uplink assignments? When it creates the storage port group for example will I be able to assign the uplinks dedicated for storage traffic on my hosts? Mike Corey Technology Senior Consultant, IT CS CTW Operation & Virtualization Service US SAP AMERICA, INC. 3999 West Chester Pike, Newtown Square, 19073 United States T +1 610 661 0905, M +1 484 274 2658, E mike.co...@sap.com<mailto:mike.co...@sap.com> [cid:image001.png@01D74653.1E63B600]
