Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BFC2110987 for ; Thu, 7 Nov 2013 21:16:13 +0000 (UTC) Received: (qmail 63639 invoked by uid 500); 7 Nov 2013 21:16:13 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 63607 invoked by uid 500); 7 Nov 2013 21:16:13 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 63599 invoked by uid 99); 7 Nov 2013 21:16:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Nov 2013 21:16:13 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mike.tutkowski@solidfire.com designates 209.85.214.178 as permitted sender) Received: from [209.85.214.178] (HELO mail-ob0-f178.google.com) (209.85.214.178) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Nov 2013 21:16:09 +0000 Received: by mail-ob0-f178.google.com with SMTP id va2so663479obc.37 for ; Thu, 07 Nov 2013 13:15:48 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=Xk81RgrRIsLx7vxoDodcUzqC7YUrn5LmRJHlNZVXl3o=; b=AsJnF/NB0q+RvZGvNH9JzJ3rw2gkMkrPCSRkvuS2pbZ/QLgwxGNCOsWYNleoUr/1jt nfmA5IUQ4UHD8K37sxufEmzw8d2Ifms19hbBtsdpTdUPGakah/zaeoJv9OZaEwkAjZ6r 5V1ICDOlO6lrZPQ6QV6rtDG6x4EKMLFi8dAn/NPo/ip6jnWm0RrzI2ItY/Q3qulYY/UA 7K3vsSocSWy55RqRu4v2UwufIbR0T4rzdi0zFP9jo6ZsWhtshkBD8LTImVEobv5Nh0sd n876Y/27bSNgBoD4iWA/H7uz+Sk7lGunNf6Swj7Jnkcofphr+WhyeVfMHhSFZ8RvQMhN c/jg== X-Gm-Message-State: ALoCoQkujcZp5wputo4dGI4BKVyenows7I4Z5Mx6gByOwLmzAwYSRo3gHA6i327eObmsHhBwhMNP MIME-Version: 1.0 X-Received: by 10.182.143.103 with SMTP id sd7mr41876obb.70.1383858948305; Thu, 07 Nov 2013 13:15:48 -0800 (PST) Received: by 10.182.79.130 with HTTP; Thu, 7 Nov 2013 13:15:48 -0800 (PST) In-Reply-To: <068997F3-481A-4974-A81D-A83F1D10C55C@netapp.com> References: <068997F3-481A-4974-A81D-A83F1D10C55C@netapp.com> Date: Thu, 7 Nov 2013 14:15:48 -0700 Message-ID: Subject: Re: Bug? Should we allow detaching volumes when VMs have snapshots From: Mike Tutkowski To: "dev@cloudstack.apache.org" Content-Type: multipart/alternative; boundary=e89a8ff1ce9e09268b04ea9cc521 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8ff1ce9e09268b04ea9cc521 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I can see the appeal in consistent behavior, but I'm not sure we want CloudStack to always follow a least-common-denominator approach. Personally I recommend we leave XenServer's functionality here as is. On Thu, Nov 7, 2013 at 6:14 AM, SuichII, Christopher wrote: > Thanks for replying, Kelvin. > > Now, should we only not allow this on VMWare, or should we prohibit it on > XenServer as well. It appears to work fine on XenServer, but it may be a > good idea to have a consistent experience, regardless of hypervisor. > > -Chris > -- > Chris Suich > chris.suich@netapp.com > NetApp Software Engineer > Data Center Platforms =E2=80=93 Cloud Solutions > Citrix, Cisco & Red Hat > > On Nov 6, 2013, at 9:09 PM, Kelven Yang wrote: > > > We should dis-allow detaching volume from VM when it has VM snapshots. > > VMware keeps VM snapshot meta information at VM basis, disk membership > > change behind its back will cause problem and it does not provide > official > > API to manipulate at volume level for a VM snapshot. > > > > This is a bug > > > > Kelven > > > > On 11/6/13, 5:58 AM, "SuichII, Christopher" > wrote: > > > >> Bumping this. I believe we need the imput of a VMWare expert, please. > >> > >> -Chris > >> -- > >> Chris Suich > >> chris.suich@netapp.com > >> NetApp Software Engineer > >> Data Center Platforms =C2=AD Cloud Solutions > >> Citrix, Cisco & Red Hat > >> > >> On Nov 5, 2013, at 1:46 PM, Mike Tutkowski < > mike.tutkowski@solidfire.com> > >> wrote: > >> > >>> OK, well, depending on if we can or can't get a VMware person to chim= e > >>> in > >>> on this issue, we may have to disallow disks from being detached from > >>> VMware VMs with snapshots in 4.3. > >>> > >>> > >>> On Tue, Nov 5, 2013 at 11:44 AM, SuichII, Christopher < > >>> Chris.Suich@netapp.com> wrote: > >>> > >>>> Correct. > >>>> > >>>> #6 FAILS with VMWare and SUCCEEDS with Xen > >>>> > >>>> -- > >>>> Chris Suich > >>>> chris.suich@netapp.com > >>>> NetApp Software Engineer > >>>> Data Center Platforms =C2=AD Cloud Solutions > >>>> Citrix, Cisco & Red Hat > >>>> > >>>> On Nov 5, 2013, at 1:35 PM, Mike Tutkowski > >>>> > >>>> wrote: > >>>> > >>>>> I assume 6 fails with VMware, as well? > >>>>> > >>>>> Is Xen OK with 6? > >>>>> > >>>>> > >>>>> On Tue, Nov 5, 2013 at 11:26 AM, SuichII, Christopher < > >>>>> Chris.Suich@netapp.com> wrote: > >>>>> > >>>>>> FWIW, after looking into this more with Xen, when the VM is restor= ed > >>>>>> in > >>>>>> step 4, it simply no longer has the volume attached, so this appea= rs > >>>>>> to > >>>>>> really be a VMWare issue. Any VMWare experts out there know how we > >>>>>> can > >>>>>> handle this? > >>>>>> > >>>>>> -Chris > >>>>>> -- > >>>>>> Chris Suich > >>>>>> chris.suich@netapp.com > >>>>>> NetApp Software Engineer > >>>>>> Data Center Platforms =C2=AD Cloud Solutions > >>>>>> Citrix, Cisco & Red Hat > >>>>>> > >>>>>> On Nov 5, 2013, at 1:05 PM, SuichII, Christopher < > >>>> Chris.Suich@netapp.com> > >>>>>> wrote: > >>>>>> > >>>>>>> We currently don=C2=B9t allow volumes to be attached to VMs with > >>>>>>> snapshots > >>>>>> and allowing volumes to be detached causes quite a bug: > >>>>>>> > >>>>>>> 1) Attach a data disk to a VM > >>>>>>> 2) Snapshot the VM > >>>>>>> 3) Detach the data disk > >>>>>>> 4) Attempt to restore the VM from the snapshot =E2=80=B9 FAILS si= nce the > >>>>>>> data > >>>>>> disk is no longer there, although it is expected to be > >>>>>>> 5) Attempt to re-attach the volume to the VM =E2=80=B9 FAILS sinc= e you > >>>>>>> cannot > >>>>>> attach volumes to VMs with snapshots > >>>>>>> 6) Attempt to delete the VM snapshot =E2=80=B9 FAILS since the da= ta disk is > >>>>>>> no > >>>>>> longer there, although it is expected to be > >>>>>>> > >>>>>>> I have verified the above steps on VMWare, however Xen does not > >>>>>>> appear > >>>>>> to fail on step 4, presumably because VMWare handles snapshots qui= te > >>>>>> differently than Xen. > >>>>>>> > >>>>>>> Does anyone else have any thoughts on whether this is a bug or no= t? > >>>> IMO, > >>>>>> on VMWare, this set of steps can get users into a state where they > >>>>>> can > >>>> no > >>>>>> longer attach new data disks to their VM, so it appears to be a bu= g > >>>>>> of > >>>> some > >>>>>> kind. > >>>>>>> > >>>>>>> -Chris > >>>>>>> -- > >>>>>>> Chris Suich > >>>>>>> chris.suich@netapp.com > >>>>>>> NetApp Software Engineer > >>>>>>> Data Center Platforms =C2=AD Cloud Solutions > >>>>>>> Citrix, Cisco & Red Hat > >>>>>>> > >>>>>> > >>>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> *Mike Tutkowski* > >>>>> *Senior CloudStack Developer, SolidFire Inc.* > >>>>> e: mike.tutkowski@solidfire.com > >>>>> o: 303.746.7302 > >>>>> Advancing the way the world uses the > >>>>> cloud > >>>>> * * > >>>> > >>>> > >>> > >>> > >>> -- > >>> *Mike Tutkowski* > >>> *Senior CloudStack Developer, SolidFire Inc.* > >>> e: mike.tutkowski@solidfire.com > >>> o: 303.746.7302 > >>> Advancing the way the world uses the > >>> cloud > >>> * * > >> > > > > --=20 *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkowski@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud *=E2=84=A2* --e89a8ff1ce9e09268b04ea9cc521--