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

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:

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

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

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

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

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

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

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

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:

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

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