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 BBF89E62F for ; Wed, 2 Jan 2013 21:17:18 +0000 (UTC) Received: (qmail 6385 invoked by uid 500); 2 Jan 2013 21:17:18 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 6356 invoked by uid 500); 2 Jan 2013 21:17:18 -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 6343 invoked by uid 99); 2 Jan 2013 21:17:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jan 2013 21:17:18 +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 hari.kannan@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 Jan 2013 21:17:12 +0000 X-IronPort-AV: E=Sophos;i="4.84,398,1355097600"; d="scan'208";a="2329680" Received: from sjcpmailmx01.citrite.net ([10.216.14.74]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/RC4-MD5; 02 Jan 2013 21:16:51 +0000 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.72]) by SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi; Wed, 2 Jan 2013 13:16:50 -0800 From: Hari Kannan To: "cloudstack-dev@incubator.apache.org" CC: Kelven Yang Date: Wed, 2 Jan 2013 13:16:49 -0800 Subject: RE: [PROPOSAL] Configurable setting to use linked clones or not on VMware Thread-Topic: [PROPOSAL] Configurable setting to use linked clones or not on VMware Thread-Index: Ac3pLicC1zY5ys3sQ6qpY32VSi8ZQgAAAvSQ Message-ID: <6E004C34C1C59E45A35B4338808BC315013014D31246@SJCPMAILBOX01.citrite.net> References: <6E004C34C1C59E45A35B4338808BC31501301476DDB1@SJCPMAILBOX01.citrite.net> <6E004C34C1C59E45A35B4338808BC315013014D3123D@SJCPMAILBOX01.citrite.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Hi Chip, The admin (Operator) will first have to make this an option of the service = (compute) offering if he want to provide this. Then the end-user gets to ch= oose if he wants it or not. This is what I understood of David's suggestion= , which I seconded - sounds OK? Hari -----Original Message----- From: Chip Childers [mailto:chip.childers@sungard.com]=20 Sent: Wednesday, January 2, 2013 1:08 PM To: cloudstack-dev@incubator.apache.org Cc: Kelven Yang Subject: Re: [PROPOSAL] Configurable setting to use linked clones or not on= VMware On Wed, Jan 2, 2013 at 4:04 PM, Hari Kannan wrote: > I agree with David's suggestion of making it 2 way - service (compute)=20 > offering as well as letting the user to select Just to be clear... I'm against letting users select a feature like this w= ithout the operator making the decision to explicitly enable it somehow. A= s long as that's considered, I'm good with this. > Hari > > -----Original Message----- > From: David Nalley [mailto:david@gnsa.us] > Sent: Wednesday, January 2, 2013 8:54 AM > To: cloudstack-dev@incubator.apache.org > Cc: Kelven Yang > Subject: Re: [PROPOSAL] Configurable setting to use linked clones or=20 > not on VMware > > On Wed, Jan 2, 2013 at 11:44 AM, Chip Childers wrote: >> On Wed, Jan 2, 2013 at 11:37 AM, David Nalley wrote: >>> On Wed, Jan 2, 2013 at 11:10 AM, Chip Childers=20 >>> wrote: >>>> On Wed, Dec 19, 2012 at 2:31 PM, Hari Kannan = wrote: >>>>> Hello All, >>>>> >>>>> >>>>> >>>>> I wish to propose a better VM sync in CloudStack - I have added=20 >>>>> some details=20 >>>>> here>>>> u >>>>> rable+setting+to+use+linked+clones+or+not+on+VMware> along with a >>>>> JIRA ticket 670 >>>>> >>>>> Please review and comment >>>>> >>>>> Hari Kannan >>>> >>>> +1 to the concept. >>>> >>>> Same question as other emails: what release are you thinking for this? >>>> Is someone taking this work on? >>>> >>>> I pulled out your question on the design page, and have some thoughts: >>>> >>>>> Should this be at a template level or account level or VM level?? >>>> >>>> Isn't this something that's more infrastructure centric? i.e.: >>>> linked clone functionality is provided by the hypervisor, and=20 >>>> really is an operator decision (not a user decision). Should the=20 >>>> configuration reflect that, instead of leaking the infra=20 >>>> implementation details to the end user? >>>> >>> >>> I don't know that this is truly infra-specific - why not make it=20 >>> part of the service offering; like local storage. Admin has to=20 >>> configure it, but user gets the option of choosing it. >>> >>> --David >>> >> >> That's reasonable... the concern I have is that I'm not interested=20 >> in the end user selecting this without the operator agreeing to=20 >> offering it. Service offerings are certainly a way to accomplish=20 >> that goal, while also allowing users to decide when to use it. >> >> -chip > > My concern is that I don't want it to be boolean for an entire swath of i= nfra - there are use cases for both. > > --David >