Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume Not Removed on Instance Delete

2016-06-29 Thread Fox, Kevin M 
Thanks for the pointers. These look good, and I'll keep an eye on them. :)

Kevin

From: Peter Stachowski [pe...@tesora.com]
Sent: Wednesday, June 29, 2016 5:06 AM
To: OpenStack Development Mailing List (not for usage questions); Ali Adil
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete

Hi Kevin,

There are a few blueprints in Trove that might address your use case.  See 
https://blueprints.launchpad.net/trove/+spec/snapshot-as-backup-strategy or 
maybe https://blueprints.launchpad.net/trove/+spec/volume-delete-on-terminate . 
 If neither is entirely correct, please feel free to submit a new one.

Thanks!
Peter

From: Fox, Kevin M [mailto:kevin@pnnl.gov]
Sent: June-28-16 7:10 PM
To: OpenStack Development Mailing List (not for usage questions); Ali Adil
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete

To me, one of the benefits of cinder is the ability to have the volume outlast 
the vm. So, for example, if you knew a yum upgrade went bad on the vm, but the 
db data is safe, it would be nice to be able to just delete the vm and have 
trove relaunch using the existing volume, not having to import all the data 
again. Or the host it was running on died but the volume is ok. It would be 
very nice if Trove supported this use case.

Thanks,
Kevin

From: Peter Stachowski [pe...@tesora.com]
Sent: Tuesday, June 28, 2016 3:39 PM
To: OpenStack Development Mailing List (not for usage questions); Ali Adil
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete
Hi Will,

Trove is a managed database service.  Once you delete the database, all 
associated volumes with it are also deleted, as is the Nova instance.  One of 
the key benefits of using Trove is that you don’t have to manage 
servers/volumes/security_groups etc.  Also, depending on the provider’s 
implementation, the volume may not be visible to the end user and thus would 
just be left lying around using up resources if it isn’t deleted by Trove 
(while potentially having the use charged back to the end user).  This is the 
case that is being addressed – having a volume left undeleted even if the Nova 
instance is gone (or in this case didn’t start successfully).

Thanks,
Peter


From: Will Zhou [mailto:zzxw...@gmail.com]
Sent: June-28-16 10:55 AM
To: OpenStack Development Mailing List (not for usage questions); Ali Adil
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete

Hi Scott, many thanks for your figuration.  Thanks and +1 for your nomination 
to nova core:)

Hi aadil, we should DETACH the volume, instead of DELETE. Please help enhance 
your code which is really a helpful fix to the bug. Thanks.

On Tue, Jun 28, 2016 at 10:51 PM D'Angelo, Scott 
> wrote:
If a volume is attached to an instance, and the instance is deleted, the volume 
will be DETACHED, but the volume will still exist, it will NOT be DELETED.

It is up to the volume owner to delete the volume if they wish.


From: Will Zhou >
Sent: Tuesday, June 28, 2016 8:43:51 AM
To: aa...@tesora.com; OpenStack Development Mailing 
List (not for usage questions)
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete

Hi all,

I'd like to make sure should the volume, which is attached to an instance, be 
detached or be deleted after the instance is deleted? Thanks.


On Tue, Jun 28, 2016 at 10:16 PM Ali Asgar Adil (Code Review) 
>>
 wrote:
Ali Asgar Adil has posted comments on this change.

Change subject: Ophaned Volume Not Removed on Instance Delete
..


Patch Set 1:

In what situation would a nova instance be in "available" state. Also, we are 
are deleting the instance so we would want the volume to be deleted as well not 
detached.

--
To view, visit https://review.openstack.org/334722
To unsubscribe, visit https://review.openstack.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: Ie921a8ff2851e2d9d76a3c3836945c750f090c4e
Gerrit-PatchSet: 1
Gerrit-Project: openstack/trove
Gerrit-Branch: master
Gerrit-Owner: Ali Asgar Adil 
>>
Gerrit-Reviewer: Ali Asgar Adil 
>>
Gerrit-Reviewer: Jenkins
Gerrit-Reviewer: zzxwill 
>>
Gerrit-HasComments: No

Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume Not Removed on Instance Delete

2016-06-29 Thread Peter Stachowski 
Hi Kevin,

There are a few blueprints in Trove that might address your use case.  See 
https://blueprints.launchpad.net/trove/+spec/snapshot-as-backup-strategy or 
maybe https://blueprints.launchpad.net/trove/+spec/volume-delete-on-terminate . 
 If neither is entirely correct, please feel free to submit a new one.

Thanks!
Peter

From: Fox, Kevin M [mailto:kevin@pnnl.gov]
Sent: June-28-16 7:10 PM
To: OpenStack Development Mailing List (not for usage questions); Ali Adil
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete

To me, one of the benefits of cinder is the ability to have the volume outlast 
the vm. So, for example, if you knew a yum upgrade went bad on the vm, but the 
db data is safe, it would be nice to be able to just delete the vm and have 
trove relaunch using the existing volume, not having to import all the data 
again. Or the host it was running on died but the volume is ok. It would be 
very nice if Trove supported this use case.

Thanks,
Kevin

From: Peter Stachowski [pe...@tesora.com]
Sent: Tuesday, June 28, 2016 3:39 PM
To: OpenStack Development Mailing List (not for usage questions); Ali Adil
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete
Hi Will,

Trove is a managed database service.  Once you delete the database, all 
associated volumes with it are also deleted, as is the Nova instance.  One of 
the key benefits of using Trove is that you don’t have to manage 
servers/volumes/security_groups etc.  Also, depending on the provider’s 
implementation, the volume may not be visible to the end user and thus would 
just be left lying around using up resources if it isn’t deleted by Trove 
(while potentially having the use charged back to the end user).  This is the 
case that is being addressed – having a volume left undeleted even if the Nova 
instance is gone (or in this case didn’t start successfully).

Thanks,
Peter


From: Will Zhou [mailto:zzxw...@gmail.com]
Sent: June-28-16 10:55 AM
To: OpenStack Development Mailing List (not for usage questions); Ali Adil
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete

Hi Scott, many thanks for your figuration.  Thanks and +1 for your nomination 
to nova core:)

Hi aadil, we should DETACH the volume, instead of DELETE. Please help enhance 
your code which is really a helpful fix to the bug. Thanks.

On Tue, Jun 28, 2016 at 10:51 PM D'Angelo, Scott 
> wrote:
If a volume is attached to an instance, and the instance is deleted, the volume 
will be DETACHED, but the volume will still exist, it will NOT be DELETED.

It is up to the volume owner to delete the volume if they wish.


From: Will Zhou >
Sent: Tuesday, June 28, 2016 8:43:51 AM
To: aa...@tesora.com; OpenStack Development Mailing 
List (not for usage questions)
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete

Hi all,

I'd like to make sure should the volume, which is attached to an instance, be 
detached or be deleted after the instance is deleted? Thanks.


On Tue, Jun 28, 2016 at 10:16 PM Ali Asgar Adil (Code Review) 
>>
 wrote:
Ali Asgar Adil has posted comments on this change.

Change subject: Ophaned Volume Not Removed on Instance Delete
..


Patch Set 1:

In what situation would a nova instance be in "available" state. Also, we are 
are deleting the instance so we would want the volume to be deleted as well not 
detached.

--
To view, visit https://review.openstack.org/334722
To unsubscribe, visit https://review.openstack.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: Ie921a8ff2851e2d9d76a3c3836945c750f090c4e
Gerrit-PatchSet: 1
Gerrit-Project: openstack/trove
Gerrit-Branch: master
Gerrit-Owner: Ali Asgar Adil 
>>
Gerrit-Reviewer: Ali Asgar Adil 
>>
Gerrit-Reviewer: Jenkins
Gerrit-Reviewer: zzxwill 
>>
Gerrit-HasComments: No
--

-
?
???
Mobile: 13701280947
?WeChat: 472174291

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume Not Removed on Instance Delete

2016-06-29 Thread Peter Stachowski 
Hi Will,

Any time.  ☺  If there is specific functionality that you think is missing and 
would like to see added to Trove, please enter a blueprint.  Thanks!

Peter

From: Will Zhou [mailto:zzxw...@gmail.com]
Sent: June-29-16 12:53 AM
To: OpenStack Development Mailing List (not for usage questions); Ali Adil
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete

Hi Peter,

I got the point and I realize that I am wrong about the fix. Thanks for the 
clarification.
On Wed, Jun 29, 2016 at 6:42 AM Peter Stachowski 
> wrote:
Hi Will,

Trove is a managed database service.  Once you delete the database, all 
associated volumes with it are also deleted, as is the Nova instance.  One of 
the key benefits of using Trove is that you don’t have to manage 
servers/volumes/security_groups etc.  Also, depending on the provider’s 
implementation, the volume may not be visible to the end user and thus would 
just be left lying around using up resources if it isn’t deleted by Trove 
(while potentially having the use charged back to the end user).  This is the 
case that is being addressed – having a volume left undeleted even if the Nova 
instance is gone (or in this case didn’t start successfully).

Thanks,
Peter


From: Will Zhou [mailto:zzxw...@gmail.com]
Sent: June-28-16 10:55 AM
To: OpenStack Development Mailing List (not for usage questions); Ali Adil

Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete

Hi Scott, many thanks for your figuration.  Thanks and +1 for your nomination 
to nova core:)

Hi aadil, we should DETACH the volume, instead of DELETE. Please help enhance 
your code which is really a helpful fix to the bug. Thanks.

On Tue, Jun 28, 2016 at 10:51 PM D'Angelo, Scott 
> wrote:
If a volume is attached to an instance, and the instance is deleted, the volume 
will be DETACHED, but the volume will still exist, it will NOT be DELETED.

It is up to the volume owner to delete the volume if they wish.


From: Will Zhou >
Sent: Tuesday, June 28, 2016 8:43:51 AM
To: aa...@tesora.com; OpenStack Development Mailing 
List (not for usage questions)
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete

Hi all,

I'd like to make sure should the volume, which is attached to an instance, be 
detached or be deleted after the instance is deleted? Thanks.


On Tue, Jun 28, 2016 at 10:16 PM Ali Asgar Adil (Code Review) 
>>
 wrote:
Ali Asgar Adil has posted comments on this change.

Change subject: Ophaned Volume Not Removed on Instance Delete
..


Patch Set 1:

In what situation would a nova instance be in "available" state. Also, we are 
are deleting the instance so we would want the volume to be deleted as well not 
detached.

--
To view, visit https://review.openstack.org/334722
To unsubscribe, visit https://review.openstack.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: Ie921a8ff2851e2d9d76a3c3836945c750f090c4e
Gerrit-PatchSet: 1
Gerrit-Project: openstack/trove
Gerrit-Branch: master
Gerrit-Owner: Ali Asgar Adil 
>>
Gerrit-Reviewer: Ali Asgar Adil 
>>
Gerrit-Reviewer: Jenkins
Gerrit-Reviewer: zzxwill 
>>
Gerrit-HasComments: No
--

-
?
???
Mobile: 13701280947
?WeChat: 472174291

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--

-

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--

-
​
周正喜
Mobile: 13701280947
​WeChat: 472174291
__
OpenStack Development Mailing List (not for usage

Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume Not Removed on Instance Delete

2016-06-28 Thread Will Zhou 
Hi Peter,

I got the point and I realize that I am wrong about the fix. Thanks for the
clarification.

On Wed, Jun 29, 2016 at 6:42 AM Peter Stachowski  wrote:

> Hi Will,
>
>
>
> Trove is a managed database service.  Once you delete the database, all
> associated volumes with it are also deleted, as is the Nova instance.  One
> of the key benefits of using Trove is that you don’t have to manage
> servers/volumes/security_groups etc.  Also, depending on the provider’s
> implementation, the volume may not be visible to the end user and thus
> would just be left lying around using up resources if it isn’t deleted by
> Trove (while potentially having the use charged back to the end user).
> This is the case that is being addressed – having a volume left undeleted
> even if the Nova instance is gone (or in this case didn’t start
> successfully).
>
>
>
> Thanks,
>
> Peter
>
>
>
>
>
> *From:* Will Zhou [mailto:zzxw...@gmail.com]
> *Sent:* June-28-16 10:55 AM
> *To:* OpenStack Development Mailing List (not for usage questions); Ali
> Adil
>
>
> *Subject:* Re: [openstack-dev] Change in openstack/trove[master]: Ophaned
> Volume Not Removed on Instance Delete
>
>
>
> Hi Scott, many thanks for your figuration.  Thanks and +1 for your
> nomination to nova core:)
>
>
>
> Hi aadil, we should DETACH the volume, instead of DELETE. Please help
> enhance your code which is really a helpful fix to the bug. Thanks.
>
>
>
> On Tue, Jun 28, 2016 at 10:51 PM D'Angelo, Scott 
> wrote:
>
> If a volume is attached to an instance, and the instance is deleted, the
> volume will be DETACHED, but the volume will still exist, it will NOT be
> DELETED.
>
> It is up to the volume owner to delete the volume if they wish.
>
> 
> From: Will Zhou 
> Sent: Tuesday, June 28, 2016 8:43:51 AM
> To: aa...@tesora.com; OpenStack Development Mailing List (not for usage
> questions)
> Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned
> Volume Not Removed on Instance Delete
>
> Hi all,
>
> I'd like to make sure should the volume, which is attached to an instance,
> be detached or be deleted after the instance is deleted? Thanks.
>
>
> On Tue, Jun 28, 2016 at 10:16 PM Ali Asgar Adil (Code Review) <
> rev...@openstack.org> wrote:
> Ali Asgar Adil has posted comments on this change.
>
> Change subject: Ophaned Volume Not Removed on Instance Delete
> ..
>
>
> Patch Set 1:
>
> In what situation would a nova instance be in "available" state. Also, we
> are are deleting the instance so we would want the volume to be deleted as
> well not detached.
>
> --
> To view, visit https://review.openstack.org/334722
> To unsubscribe, visit https://review.openstack.org/settings
>
> Gerrit-MessageType: comment
> Gerrit-Change-Id: Ie921a8ff2851e2d9d76a3c3836945c750f090c4e
> Gerrit-PatchSet: 1
> Gerrit-Project: openstack/trove
> Gerrit-Branch: master
> Gerrit-Owner: Ali Asgar Adil >
> Gerrit-Reviewer: Ali Asgar Adil  >>
> Gerrit-Reviewer: Jenkins
> Gerrit-Reviewer: zzxwill >
> Gerrit-HasComments: No
> --
>
> -
> ?
> ???
> Mobile: 13701280947>
> ?WeChat: 472174291
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> --
>
>
>
> -
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 

-
​
周正喜
Mobile: 13701280947
​WeChat: 472174291
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume Not Removed on Instance Delete

2016-06-28 Thread Fox, Kevin M 
To me, one of the benefits of cinder is the ability to have the volume outlast 
the vm. So, for example, if you knew a yum upgrade went bad on the vm, but the 
db data is safe, it would be nice to be able to just delete the vm and have 
trove relaunch using the existing volume, not having to import all the data 
again. Or the host it was running on died but the volume is ok. It would be 
very nice if Trove supported this use case.

Thanks,
Kevin

From: Peter Stachowski [pe...@tesora.com]
Sent: Tuesday, June 28, 2016 3:39 PM
To: OpenStack Development Mailing List (not for usage questions); Ali Adil
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete

Hi Will,

Trove is a managed database service.  Once you delete the database, all 
associated volumes with it are also deleted, as is the Nova instance.  One of 
the key benefits of using Trove is that you don’t have to manage 
servers/volumes/security_groups etc.  Also, depending on the provider’s 
implementation, the volume may not be visible to the end user and thus would 
just be left lying around using up resources if it isn’t deleted by Trove 
(while potentially having the use charged back to the end user).  This is the 
case that is being addressed – having a volume left undeleted even if the Nova 
instance is gone (or in this case didn’t start successfully).

Thanks,
Peter


From: Will Zhou [mailto:zzxw...@gmail.com]
Sent: June-28-16 10:55 AM
To: OpenStack Development Mailing List (not for usage questions); Ali Adil
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete

Hi Scott, many thanks for your figuration.  Thanks and +1 for your nomination 
to nova core:)

Hi aadil, we should DETACH the volume, instead of DELETE. Please help enhance 
your code which is really a helpful fix to the bug. Thanks.

On Tue, Jun 28, 2016 at 10:51 PM D'Angelo, Scott 
> wrote:
If a volume is attached to an instance, and the instance is deleted, the volume 
will be DETACHED, but the volume will still exist, it will NOT be DELETED.

It is up to the volume owner to delete the volume if they wish.


From: Will Zhou >
Sent: Tuesday, June 28, 2016 8:43:51 AM
To: aa...@tesora.com; OpenStack Development Mailing 
List (not for usage questions)
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete

Hi all,

I'd like to make sure should the volume, which is attached to an instance, be 
detached or be deleted after the instance is deleted? Thanks.


On Tue, Jun 28, 2016 at 10:16 PM Ali Asgar Adil (Code Review) 
>>
 wrote:
Ali Asgar Adil has posted comments on this change.

Change subject: Ophaned Volume Not Removed on Instance Delete
..


Patch Set 1:

In what situation would a nova instance be in "available" state. Also, we are 
are deleting the instance so we would want the volume to be deleted as well not 
detached.

--
To view, visit https://review.openstack.org/334722
To unsubscribe, visit https://review.openstack.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: Ie921a8ff2851e2d9d76a3c3836945c750f090c4e
Gerrit-PatchSet: 1
Gerrit-Project: openstack/trove
Gerrit-Branch: master
Gerrit-Owner: Ali Asgar Adil 
>>
Gerrit-Reviewer: Ali Asgar Adil 
>>
Gerrit-Reviewer: Jenkins
Gerrit-Reviewer: zzxwill 
>>
Gerrit-HasComments: No
--

-
?
???
Mobile: 13701280947
?WeChat: 472174291

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--

-
​
周正喜
Mobile: 13701280947
​WeChat: 472174291
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume Not Removed on Instance Delete

2016-06-28 Thread Peter Stachowski 
Hi Will,

Trove is a managed database service.  Once you delete the database, all 
associated volumes with it are also deleted, as is the Nova instance.  One of 
the key benefits of using Trove is that you don’t have to manage 
servers/volumes/security_groups etc.  Also, depending on the provider’s 
implementation, the volume may not be visible to the end user and thus would 
just be left lying around using up resources if it isn’t deleted by Trove 
(while potentially having the use charged back to the end user).  This is the 
case that is being addressed – having a volume left undeleted even if the Nova 
instance is gone (or in this case didn’t start successfully).

Thanks,
Peter


From: Will Zhou [mailto:zzxw...@gmail.com]
Sent: June-28-16 10:55 AM
To: OpenStack Development Mailing List (not for usage questions); Ali Adil
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete

Hi Scott, many thanks for your figuration.  Thanks and +1 for your nomination 
to nova core:)

Hi aadil, we should DETACH the volume, instead of DELETE. Please help enhance 
your code which is really a helpful fix to the bug. Thanks.

On Tue, Jun 28, 2016 at 10:51 PM D'Angelo, Scott 
> wrote:
If a volume is attached to an instance, and the instance is deleted, the volume 
will be DETACHED, but the volume will still exist, it will NOT be DELETED.

It is up to the volume owner to delete the volume if they wish.


From: Will Zhou >
Sent: Tuesday, June 28, 2016 8:43:51 AM
To: aa...@tesora.com; OpenStack Development Mailing 
List (not for usage questions)
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete

Hi all,

I'd like to make sure should the volume, which is attached to an instance, be 
detached or be deleted after the instance is deleted? Thanks.


On Tue, Jun 28, 2016 at 10:16 PM Ali Asgar Adil (Code Review) 
>>
 wrote:
Ali Asgar Adil has posted comments on this change.

Change subject: Ophaned Volume Not Removed on Instance Delete
..


Patch Set 1:

In what situation would a nova instance be in "available" state. Also, we are 
are deleting the instance so we would want the volume to be deleted as well not 
detached.

--
To view, visit https://review.openstack.org/334722
To unsubscribe, visit https://review.openstack.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: Ie921a8ff2851e2d9d76a3c3836945c750f090c4e
Gerrit-PatchSet: 1
Gerrit-Project: openstack/trove
Gerrit-Branch: master
Gerrit-Owner: Ali Asgar Adil 
>>
Gerrit-Reviewer: Ali Asgar Adil 
>>
Gerrit-Reviewer: Jenkins
Gerrit-Reviewer: zzxwill 
>>
Gerrit-HasComments: No
--

-
?
???
Mobile: 13701280947
?WeChat: 472174291

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--

-
​
周正喜
Mobile: 13701280947
​WeChat: 472174291
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume Not Removed on Instance Delete

2016-06-28 Thread D'Angelo, Scott 
If a volume is attached to an instance, and the instance is deleted, the volume 
will be DETACHED, but the volume will still exist, it will NOT be DELETED.

It is up to the volume owner to delete the volume if they wish.


From: Will Zhou 
Sent: Tuesday, June 28, 2016 8:43:51 AM
To: aa...@tesora.com; OpenStack Development Mailing List (not for usage 
questions)
Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume 
Not Removed on Instance Delete

Hi all,

I'd like to make sure should the volume, which is attached to an instance, be 
detached or be deleted after the instance is deleted? Thanks.


On Tue, Jun 28, 2016 at 10:16 PM Ali Asgar Adil (Code Review) 
> wrote:
Ali Asgar Adil has posted comments on this change.

Change subject: Ophaned Volume Not Removed on Instance Delete
..


Patch Set 1:

In what situation would a nova instance be in "available" state. Also, we are 
are deleting the instance so we would want the volume to be deleted as well not 
detached.

--
To view, visit https://review.openstack.org/334722
To unsubscribe, visit https://review.openstack.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: Ie921a8ff2851e2d9d76a3c3836945c750f090c4e
Gerrit-PatchSet: 1
Gerrit-Project: openstack/trove
Gerrit-Branch: master
Gerrit-Owner: Ali Asgar Adil >
Gerrit-Reviewer: Ali Asgar Adil >
Gerrit-Reviewer: Jenkins
Gerrit-Reviewer: zzxwill >
Gerrit-HasComments: No
--

-
?
???
Mobile: 13701280947
?WeChat: 472174291

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume Not Removed on Instance Delete

2016-06-28 Thread Will Zhou 
Hi Scott, many thanks for your figuration.  Thanks and +1 for your
nomination to nova core:)

Hi aadil, we should DETACH the volume, instead of DELETE. Please help
enhance your code which is really a helpful fix to the bug. Thanks.

On Tue, Jun 28, 2016 at 10:51 PM D'Angelo, Scott 
wrote:

> If a volume is attached to an instance, and the instance is deleted, the
> volume will be DETACHED, but the volume will still exist, it will NOT be
> DELETED.
>
> It is up to the volume owner to delete the volume if they wish.
>
> 
> From: Will Zhou 
> Sent: Tuesday, June 28, 2016 8:43:51 AM
> To: aa...@tesora.com; OpenStack Development Mailing List (not for usage
> questions)
> Subject: Re: [openstack-dev] Change in openstack/trove[master]: Ophaned
> Volume Not Removed on Instance Delete
>
> Hi all,
>
> I'd like to make sure should the volume, which is attached to an instance,
> be detached or be deleted after the instance is deleted? Thanks.
>
>
> On Tue, Jun 28, 2016 at 10:16 PM Ali Asgar Adil (Code Review) <
> rev...@openstack.org> wrote:
> Ali Asgar Adil has posted comments on this change.
>
> Change subject: Ophaned Volume Not Removed on Instance Delete
> ..
>
>
> Patch Set 1:
>
> In what situation would a nova instance be in "available" state. Also, we
> are are deleting the instance so we would want the volume to be deleted as
> well not detached.
>
> --
> To view, visit https://review.openstack.org/334722
> To unsubscribe, visit https://review.openstack.org/settings
>
> Gerrit-MessageType: comment
> Gerrit-Change-Id: Ie921a8ff2851e2d9d76a3c3836945c750f090c4e
> Gerrit-PatchSet: 1
> Gerrit-Project: openstack/trove
> Gerrit-Branch: master
> Gerrit-Owner: Ali Asgar Adil >
> Gerrit-Reviewer: Ali Asgar Adil  >>
> Gerrit-Reviewer: Jenkins
> Gerrit-Reviewer: zzxwill >
> Gerrit-HasComments: No
> --
>
> -
> ?
> ???
> Mobile: 13701280947
> ?WeChat: 472174291
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 

-
​
周正喜
Mobile: 13701280947
​WeChat: 472174291
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume Not Removed on Instance Delete

2016-06-28 Thread Will Zhou 
Hi all,

I'd like to make sure should the volume, which is attached to an instance,
be *detached* or be *deleted* after the instance is deleted? Thanks.


On Tue, Jun 28, 2016 at 10:16 PM Ali Asgar Adil (Code Review) <
rev...@openstack.org> wrote:

> Ali Asgar Adil has posted comments on this change.
>
> Change subject: Ophaned Volume Not Removed on Instance Delete
> ..
>
>
> Patch Set 1:
>
> In what situation would a nova instance be in "available" state. Also, we
> are are deleting the instance so we would want the volume to be deleted as
> well not detached.
>
> --
> To view, visit https://review.openstack.org/334722
> To unsubscribe, visit https://review.openstack.org/settings
>
> Gerrit-MessageType: comment
> Gerrit-Change-Id: Ie921a8ff2851e2d9d76a3c3836945c750f090c4e
> Gerrit-PatchSet: 1
> Gerrit-Project: openstack/trove
> Gerrit-Branch: master
> Gerrit-Owner: Ali Asgar Adil 
> Gerrit-Reviewer: Ali Asgar Adil 
> Gerrit-Reviewer: Jenkins
> Gerrit-Reviewer: zzxwill 
> Gerrit-HasComments: No
>
-- 

-
​
周正喜
Mobile: 13701280947
​WeChat: 472174291
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev