A recommendation could be (in the docs), that clusters > X hosts use a DVS (Nexus 1KV or VMware's DVS). Those switching approaches obviously limit the port profile creation to 1 switch target for the cluster (the DVS control plane, i.e. the VSM or Virtual Center).
On Thu, Dec 20, 2012 at 1:18 PM, Kelven Yang <kelven.y...@citrix.com> wrote: > There is another constraint that comes into play when cluster size becomes > large, for example 32 hosts. We use standard vSwitch in default > implementation, in order to support out-of-band vMotion (may be activated > by DRS), when we deploy a VM, we actually will program all the vSwitches > within the cluster, and this takes time, bigger the cluster, longer the > time. So 16 hosts per cluster sounds a good balance even if the hard limit > from vSphere is 32. > > Kelven > > On 12/20/12 10:05 AM, "Will Chan" <will.c...@citrix.com> wrote: > >>Correct. In vsphere 5.1, this limitation was lifted to support up to 32 >>hosts. >> >>> -----Original Message----- >>> From: David Nalley [mailto:da...@gnsa.us] >>> Sent: Thursday, December 20, 2012 8:55 AM >>> To: cloudstack-dev@incubator.apache.org >>> Subject: Re: [PROPOSAL] Raise cluster size limit to 16 on VMware >>> >>> On Thu, Dec 20, 2012 at 11:52 AM, Chip Childers >>> <chip.child...@sungard.com> wrote: >>> > Sorry, should have been more clear in my question. What's the math >>> > that got you to 8? >>> > >>> >>> No math involved. >>> It was a VMFS limitation around number of hosts that could >>>simultaneously >>> use a linked clone disk image. >>> >>> --David > >
