+1 The more we move these types of things out of configuration and into component specific references the better.
--Alex > -----Original Message----- > From: Tamas Monos [mailto:tam...@veber.co.uk] > Sent: Thursday, December 20, 2012 8:10 AM > To: cloudstack-dev@incubator.apache.org > Subject: RE: [PROPOSAL] Raise cluster size limit to 16 on VMware > > Hi, > > I'd recommend removing any hard limits from CS and introduce a variable like > "max.guest.limit" on the Hypervisor Capabilities page. > This value could default to 8, but should the admin decide otherwise could be > set to anything. > > Regards > > Tamas Monos DDI > +44(0)2034687012 > Chief Technical Office > +44(0)2034687000 > Veber: The Hosting Specialists Fax +44(0)871 522 7057 > http://www.veber.co.uk > > Follow us on Twitter: www.twitter.com/veberhost > Follow us on Facebook: www.facebook.com/veberhost > > -----Original Message----- > From: David Nalley [mailto:da...@gnsa.us] > Sent: 20 December 2012 15:25 > To: cloudstack-dev@incubator.apache.org > Subject: Re: [PROPOSAL] Raise cluster size limit to 16 on VMware > > On Thu, Dec 20, 2012 at 1:54 AM, Koushik Das <koushik....@citrix.com> > wrote: > > This http://www.vmware.com/pdf/vsphere5/r51/vsphere-51- > configuration-maximums.pdf mentions that the max. can be 32 for ESX 5.1. > Any specific reason to make it 16? Also it needs to be seen that this limit > works across all supported ESX versions. > > > > -Koushik > > > > Yes - the different versions having different limits complicates things a bit. > 5.1 = 32, 5.0 = 16 4.x = 8? > > --David >
