Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of koushik.das@citrix.com
 designates 203.166.19.134 as permitted sender)
From: Koushik Das <koushik.das@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Thu, 3 Jan 2013 17:25:37 +0530
Subject: RE: [PROPOSAL] Raise cluster size limit to 16 on VMware
Thread-Topic: [PROPOSAL] Raise cluster size limit to 16 on VMware
Thread-Index: 
 Ac3eIlFgC3ddb5UTQ0O7BPe7YRn8BQAHbA+AAAAIfgAAAL9VAAABZx4AAADuHwAADJ07gAARz3WAAAFrLfAAAR8T8AK1pIUA
Message-ID: 
 <2529883E7B666F4E8F21F85AADA43CA7010C8F171804@BANPMAILBOX01.citrite.net>
References: 
 <61AE1E2837A06D4A8E98B796183842D401293587B4FE@SJCPMAILBOX01.citrite.net>
 <CCF79D59.2480C%kelven.yang@citrix.com>
 <2529883E7B666F4E8F21F85AADA43CA7010C8EB1BD33@BANPMAILBOX01.citrite.net>
 <CAKprHVa9o_rjiPpMisVwpg=zg_Br1M=ZAt09DXSvdMNVZHfY+w@mail.gmail.com>
 <CE854734D1A2D941BA87A532AA5DB06440282C29@AMXPRD0610MB388.eurprd06.prod.outlook.com>
 <B1DF26ECC0458748AC97CECE2DA98D41012FA385E083@SJCPMAILBOX01.citrite.net>
In-Reply-To: 
 <B1DF26ECC0458748AC97CECE2DA98D41012FA385E083@SJCPMAILBOX01.citrite.net>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

So based on the discussions would it be fair to conclude that this should b=
e handled by adding some column like 'max_host_per_cluster' in hypervisor_c=
apabilities table. Currently the following version entries are present for =
Vmware. For each version an appropriate value can be associated based on th=
e limitations/actual supported. For other HVs where this setting is not app=
licable some dummy value, say (-1) can be entered.

hv_type	hv_version
VMware	default
VMware	4.0
VMware	4.1
VMware	5.0

Let me know if there is a consensus on this.

Thanks,
Koushik

> -----Original Message-----
> From: Alex Huang [mailto:Alex.Huang@citrix.com]
> Sent: Thursday, December 20, 2012 10:08 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [PROPOSAL] Raise cluster size limit to 16 on VMware
>=20
> +1
>=20
> The more we move these types of things out of configuration and into
> component specific references the better.
>=20
> --Alex
>=20
> > -----Original Message-----
> > From: Tamas Monos [mailto:tamasm@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:david@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.das@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 =3D 32, 5.0 =3D 16 4.x =3D 8?
> >
> > --David
> >