Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of hari.kannan@citrix.com
 designates 66.165.176.63 as permitted sender)
From: Hari Kannan <hari.kannan@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Wed, 9 Jan 2013 23:12:36 -0800
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+AAAAIfgAAAL9VAAABZx4AAADuHwAADJ07gAARz3WAAAFrLfAAAR8T8AK1pIUAAMvKCZAAPGGcoAAAVgtgAACG3KAAS50BIAAB6kaw
Message-ID: 
 <6E004C34C1C59E45A35B4338808BC315013014D31AE7@SJCPMAILBOX01.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>
 <2529883E7B666F4E8F21F85AADA43CA7010C8F171804@BANPMAILBOX01.citrite.net>
 <2529883E7B666F4E8F21F85AADA43CA7010C8F171C2F@BANPMAILBOX01.citrite.net>
 <6E004C34C1C59E45A35B4338808BC315013014D3180C@SJCPMAILBOX01.citrite.net>
 <B1DF26ECC0458748AC97CECE2DA98D41012FA385EDB2@SJCPMAILBOX01.citrite.net>
 <2529883E7B666F4E8F21F85AADA43CA7010C8F171E75@BANPMAILBOX01.citrite.net>
 <2529883E7B666F4E8F21F85AADA43CA7010C8F17211F@BANPMAILBOX01.citrite.net>
In-Reply-To: 
 <2529883E7B666F4E8F21F85AADA43CA7010C8F17211F@BANPMAILBOX01.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

Hi Koushik,

I have a question/concern -

The "limitations" are multi-dimensional - for example, vSphere 5.0 clusters=
 hosting linked clone pools are limited to 8 ESXi hosts when using VMFS dat=
astores and 32 ESXi hosts when using only NFS datastores. In 5.1, they made=
 both 32 hosts. I think 4.0 had a different set of values.=20

In other words, the host limits are hypervisor type, hypervisor version, st=
orage technology etc. i.e. we cant set the hard limit as 32 as 5.0 did not =
support it for VMFS..

Hari

-----Original Message-----
From: Koushik Das [mailto:koushik.das@citrix.com]=20
Sent: Wednesday, January 9, 2013 10:30 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: [PROPOSAL] Raise cluster size limit to 16 on VMware

To clarify some more.

What I have suggested is to have a max. hosts per cluster limit based on sp=
ecific HV version. For e.g. for Vmware

Version 4.0 will have a max. limit of X (i.e. in any CS Vmware 4.0 cluster,=
 the max. number of hosts that can be added is X) Version 4.1 will have a m=
ax. limit of Y Version 5.0 will have a max. limit of Z

Based on the vmware specification X, Y, Z are all 32. As part of best pract=
ices (in documentation) all the limitations discussed as to why the limit w=
as set to 8 earlier can be mentioned. The idea is that CS shouldn't impose =
any artificial restrictions and rely only on HV specifications to the exten=
t possible.

For any new supported version another entry can be added to the hypervisor_=
capabilities table.

As Alex mentioned, the admin is free to decide on the number of hosts that =
needs to be added in a cluster as long as the hard max. limits are not exce=
eded.

-Koushik

> -----Original Message-----
> From: Koushik Das [mailto:koushik.das@citrix.com]
> Sent: Tuesday, January 08, 2013 11:45 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [PROPOSAL] Raise cluster size limit to 16 on VMware
>=20
> See inline
>=20
> -Koushik
>=20
> > -----Original Message-----
> > From: Alex Huang [mailto:Alex.Huang@citrix.com]
> > Sent: Tuesday, January 08, 2013 11:24 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: RE: [PROPOSAL] Raise cluster size limit to 16 on VMware
> >
> > Koushik,
> >
> > I believe what you pointed out there is the maximum limit for the
> hypervisor.
>=20
> Yes. Maximum based on the HV version.
>=20
> >
> > Hari,
> >
> > What's the point of the admin setting these values?  Afterall, he's=20
> > the one who's adding hosts himself?  If he wants more, why should cs=20
> > stop
> him?
> >
> > --Alex
> >
> > > -----Original Message-----
> > > From: Hari Kannan [mailto:hari.kannan@citrix.com]
> > > Sent: Tuesday, January 08, 2013 9:44 AM
> > > To: cloudstack-dev@incubator.apache.org
> > > Subject: RE: [PROPOSAL] Raise cluster size limit to 16 on VMware
> > >
> > > Hi Koushik,
> > >
> > > Can you please elaborate
> > >
> > > a) how the admin gets to set this value?
>=20
> Why should the admin be allowed to change these values? These are the=20
> max. limit supported by the specific HV based on the version.
>=20
> > > b) is this value set on a per cluster basis? If so, what is the defau=
lt value?
>=20
> It's not per cluster.
>=20
> > >
> > > Hari
> > >
> > > -----Original Message-----
> > > From: Koushik Das [mailto:koushik.das@citrix.com]
> > > Sent: Monday, January 7, 2013 4:57 AM
> > > To: cloudstack-dev@incubator.apache.org
> > > Subject: RE: [PROPOSAL] Raise cluster size limit to 16 on VMware
> > >
> > > Didn't see any feedback, so am assuming that the approach seems=20
> > > reasonable. I will go ahead and start with the implementation. Not=20
> > > planning to write a FS as this is a small feature and the below=20
> > > mail
> > summarizes it.
> > >
> > > -Koushik
> > >
> > > > -----Original Message-----
> > > > From: Koushik Das [mailto:koushik.das@citrix.com]
> > > > Sent: Thursday, January 03, 2013 5:26 PM
> > > > To: cloudstack-dev@incubator.apache.org
> > > > Subject: RE: [PROPOSAL] Raise cluster size limit to 16 on VMware
> > > >
> > > > So based on the discussions would it be fair to conclude that=20
> > > > this should be handled by adding some column like 'max_host_per_clu=
ster'
> > > > in hypervisor_capabilities table. Currently the following=20
> > > > version entries are present for Vmware. For each version an=20
> > > > appropriate value can be associated based on the limitations/actual=
 supported.
> > > > For other HVs where this setting is not applicable some dummy=20
> > > > 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=20
> > > > > VMware
> > > > >
> > > > > +1
> > > > >
> > > > > The more we move these types of things out of configuration=20
> > > > > and into component specific references the better.
> > > > >
> > > > > --Alex
> > > > >
> > > > > > -----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=20
> > > > > > VMware
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I'd recommend removing any hard limits from CS and introduce=20
> > > > > > a variable like "max.guest.limit" on the Hypervisor Capabilitie=
s page.
> > > > > > This value could default to 8, but should the admin decide=20
> > > > > > otherwise could be set to anything.
> > > > > >
> > > > > > Regards
> > > > > >
> > > > > > Tamas Monos                                               DDI  =
       +44(0)2034687012
> > > > > > Chief Technical                                             Off=
ice    +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=20
> > > > > > VMware
> > > > > >
> > > > > > On Thu, Dec 20, 2012 at 1:54 AM, Koushik Das=20
> > > > > > <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=20
> > > > > > for ESX
> > > > 5.1.
> > > > > > Any specific reason to make it 16? Also it needs to be seen=20
> > > > > > that this limit works across all supported ESX versions.
> > > > > > >
> > > > > > > -Koushik
> > > > > > >
> > > > > >
> > > > > > Yes - the different versions having different limits=20
> > > > > > complicates things a
> > > > bit.
> > > > > > 5.1 =3D 32, 5.0 =3D 16 4.x =3D 8?
> > > > > >
> > > > > > --David
> > > > > >