Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E92C39DE1 for ; Wed, 2 May 2012 17:08:42 +0000 (UTC) Received: (qmail 10685 invoked by uid 500); 2 May 2012 17:08:42 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 10614 invoked by uid 500); 2 May 2012 17:08:42 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 10606 invoked by uid 99); 2 May 2012 17:08:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 May 2012 17:08:42 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Alena.Prokharchyk@citrix.com designates 66.165.176.63 as permitted sender) Received: from [66.165.176.63] (HELO SMTP02.CITRIX.COM) (66.165.176.63) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 May 2012 17:08:36 +0000 X-IronPort-AV: E=Sophos;i="4.75,518,1330923600"; d="scan'208";a="193073564" Received: from sjcpmailmx01.citrite.net ([10.216.14.74]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/RC4-MD5; 02 May 2012 13:07:41 -0400 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.73]) by SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi; Wed, 2 May 2012 10:07:40 -0700 From: Alena Prokharchyk To: "cloudstack-dev@incubator.apache.org" , Salvatore Orlando , Kevin Kluge Date: Wed, 2 May 2012 10:07:38 -0700 Subject: Re: Add zone -- why hypervisor Thread-Topic: Add zone -- why hypervisor Thread-Index: Ac0ohhTDmeU/MTAwSFazJxnskaRYUQ== Message-ID: In-Reply-To: <61AE1E2837A06D4A8E98B796183842D40116B82AD1A3@SJCPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.0.120402 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Kevin,=20 We use it for both: 1) Add the first cluster in the zone 2) Configure network labels for the first cluster's hypervisor (physical network page) Hypervisor network labels have to be configured before we add the first host to the cluster. I can see why the placement might seem confusing, but we need to know the first hypervisor type before we start configuring physical network. -Alena. On 5/2/12 9:56 AM, "Kevin Kluge" wrote: >Alena are you saying this is needed for the physical network step? Or >only in the add-cluster step at the end? > >I find the current placement and text quite confusing. It sounds like I >am saying this zone will be of this hypervisor type, which I know is not >true. > > >> -----Original Message----- >> From: Alena Prokharchyk [mailto:Alena.Prokharchyk@citrix.com] >> Sent: Wednesday, May 02, 2012 8:51 AM >> To: cloudstack-dev@incubator.apache.org; Salvatore Orlando >> Subject: Re: Add zone -- why hypervisor >>=20 >> Not quite correct. It's used as a hypervisor for the first cluster you >>setup >> during "Add zone". It defines the hypervisor type for the host and >>network >> labels that you also setup during the add zone process. >>=20 >> We don't use this setting as default anywhere else after the zone is >>created. >>=20 >> -Alena. >>=20 >> On 5/2/12 6:40 AM, "Salvatore Orlando" >> wrote: >>=20 >> >I believe it is used as a default setting for all clusters in the zone. >> >But then you are still free to override that setting for specific >> >clusters. >> > >> >Salvatore >> > >> >> -----Original Message----- >> >> From: Kevin Kluge [mailto:Kevin.Kluge@citrix.com] >> >> Sent: 02 May 2012 14:06 >> >> To: cloudstack-dev@incubator.apache.org >> >> Subject: Add zone -- why hypervisor >> >> >> >> When you add a zone in 3.0.x there is a field for Hypervisor. Why is >> >>that? >