Stanley, We are large VSphere shop with ACS. While dVswitch support is coming out in 4.2, we've backported the code from 4.2 into 4.1 and have been running it for some time now.
We've also backported other features that are beneficial to VMWare like ability to append a hostname to VM name in vSphere. We are using tags and in some cases zones when networks don't overlap due to security/compliance. For example, I have QA 1 environment, which consists of high compute cluster and standard compute. While all QA1 hypervisors in both clusters can see the same resources, we tag the high compute hypervisors for VMs that need 2 CPUs+, and standard goes to standard 1CPU vms. We have to adhere to strict compliance, so we do customize CS to some extent. QA2 env has a same setup as QA1 except it has different network and storage - in this case we treat it as a separate zone - while I can use tags - I think in this case - it becomes too cumbersome. If interested I can share the codebase and pre-build RPMs for 4.1 we are running in house. Regards ilya > -----Original Message----- > From: Ahmad Emneina [mailto:aemne...@gmail.com] > Sent: Wednesday, May 15, 2013 2:18 PM > To: Stanley Kaytovich > Cc: users@cloudstack.apache.org > Subject: Re: Working with clouds on multiple ESX hosts > > I forgot to reply all so the group see's my answer: > i see. so for trunk2, you want to trunk your zone vlans (that were defined in > cloudstack for the advanced,guest networks) to it. you should see the > portgroup being created on vswitch1, for the guest network. if that vlan is > present on all hosts, and switchports, you should be good to go. > > > On Tue, May 14, 2013 at 3:45 PM, Stanley Kaytovich > <stanl...@qwertyc.com>wrote: > > > Ahmad, > > > > Each host has a total of 8 physical nics. > > > > 2 Nics for management (vswitch0) (trunk1) > > 4 nics for public (vswitch1) (trunk2) > > 2 10gbe nics for storage (separate switch) > > 0 nics for guests - also tried 1 separate nic and got same results > > > > -Stan > > > > Ahmad Emneina <aemne...@gmail.com> wrote: > > > > > > I was talking about physical switchports and trunks. How many nics do > > your esx hosts have? Do the vSwitches correspond to different pysical > > nics, or do they all map to 1 nic? > > > > > > On Tue, May 14, 2013 at 2:42 PM, Stanley Kaytovich > > <stanl...@qwertyc.com > > >wrote: > > > > > Ahmad, > > > > > > Actually, I misspoke, there are 6 ports on each host, but our switch > > > only allows 8 ports in a trunk. If I understand you correctly, I > > > created a > > trunk > > > on our switch for vSwitch1 (8 ports). > > > > > > Below is our vSwitch configuration in CloudStack/vCenter: > > > > > > vSwitch0 - management (excluded from trunk) > > > vSwitch1 - public > > > vSwitch2 - storage (excluded from trunk) > > > vSwitch3 - guests (excluded from trunk) > > > > > > Regards, > > > Stan > > > > > > -----Original Message----- > > > From: Ahmad Emneina [mailto:aemne...@gmail.com] > > > Sent: Tuesday, May 14, 2013 5:30 PM > > > To: Cloudstack users mailing list > > > Subject: Re: Working with clouds on multiple ESX hosts > > > > > > what vlans are you trunking to the hosts? what vlans are you using > > > in cloudstack as your zone vlans? > > > > > > > > > On Tue, May 14, 2013 at 2:22 PM, Stanley Kaytovich > > > <stanl...@qwertyc.com > > > >wrote: > > > > > > > Ahmad, > > > > > > > > I configured trunking on the switch for 8 ports. Each host has 4 > > > > physical NICs, so 8 ports are in a trunk on the switch. Still no > > > > network connectivity. > > > > > > > > :-/ > > > > > > > > > > > > -----Original Message----- > > > > From: Ahmad Emneina [mailto:aemne...@gmail.com] > > > > Sent: Tuesday, May 14, 2013 4:35 PM > > > > To: Cloudstack users mailing list > > > > Subject: Re: Working with clouds on multiple ESX hosts > > > > > > > > Sounds like youre not trunking the zone vlans to all the > > > > switchports your hosts connect to. Can you verify the vlans are > > > > trunked, then see if your networking starts working? > > > > > > > > > > > > On Tue, May 14, 2013 at 1:28 PM, Stanley Kaytovich > > > > <stanl...@qwertyc.com > > > > >wrote: > > > > > > > > > Hello, > > > > > > > > > > This is more of a general question pertaining to best practices > > > > > of how everyone works with multiple ESX hosts in a cloudstack > > > > > zone. It seems that if a VM instance resides on a different host > > > > > from other instances, there is no networking ability on the > > > > > alienated instance(s). Since the hosts are chosen automatically, > > > > > occasionally instances are created on an alternate host and the > > > > > instance boots up without networking. Adding a tag in the > > > > > computer offering is a way of forcing instances to be created on > > > > > a particular hosts, though that > > > > requires additional offerings for every host. > > > > > > > > > > Using a dvSwitch would be great, though on 4.0.2 I do not > > > > > believe it is supported or I am unable to find any documentation > > > > > to prove me > > > > otherwise. > > > > > > > > > > What is the best practice or workaround for this? > > > > > > > > > > - Stan > > > > > > > > > > > > > >
