Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

2015-02-25 Thread Joe Gordon
On Sat, Feb 21, 2015 at 5:03 AM, Tim Bell tim.b...@cern.ch wrote: A few inline comments and a general point How do we handle scenarios like volumes when we have a per-component janitor rather than a single co-ordinator ? To be clean, 1. nova should shutdown the instance 2. nova should

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

2015-02-25 Thread Matt Joyce
Wondering if heat should be performing this orchestration. Would provide for a more pluggable front end to the action set. -matt On Feb 25, 2015 2:37 PM, Joe Gordon joe.gord...@gmail.com wrote: On Sat, Feb 21, 2015 at 5:03 AM, Tim Bell tim.b...@cern.ch wrote: A few inline comments and a

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

2015-02-25 Thread Dolph Mathews
On Wed, Feb 25, 2015 at 5:42 PM, Zane Bitter zbit...@redhat.com wrote: On 25/02/15 15:37, Joe Gordon wrote: On Sat, Feb 21, 2015 at 5:03 AM, Tim Bell tim.b...@cern.ch mailto:tim.b...@cern.ch wrote: A few inline comments and a general point How do we handle scenarios like

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

2015-02-25 Thread Zane Bitter
On 25/02/15 19:15, Dolph Mathews wrote: On Wed, Feb 25, 2015 at 5:42 PM, Zane Bitter zbit...@redhat.com mailto:zbit...@redhat.com wrote: On 25/02/15 15:37, Joe Gordon wrote: On Sat, Feb 21, 2015 at 5:03 AM, Tim Bell tim.b...@cern.ch mailto:tim.b...@cern.ch

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

2015-02-25 Thread Dolph Mathews
On Wed, Feb 25, 2015 at 3:02 PM, Matt Joyce m...@nycresistor.com wrote: Wondering if heat should be performing this orchestration. I wouldn't expect heat to have access to everything that needs to be cleaned up. Would provide for a more pluggable front end to the action set. -matt On

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

2015-02-25 Thread Zane Bitter
On 25/02/15 15:37, Joe Gordon wrote: On Sat, Feb 21, 2015 at 5:03 AM, Tim Bell tim.b...@cern.ch mailto:tim.b...@cern.ch wrote: A few inline comments and a general point How do we handle scenarios like volumes when we have a per-component janitor rather than a single co-ordinator

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

2015-02-21 Thread Tim Bell
A few inline comments and a general point How do we handle scenarios like volumes when we have a per-component janitor rather than a single co-ordinator ? To be clean, 1. nova should shutdown the instance 2. nova should then ask the volume to be detached 3. cinder could then perform the

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

2015-02-19 Thread Ian Cordasco
On 2/2/15, 15:41, Morgan Fainberg morgan.fainb...@gmail.com wrote: On February 2, 2015 at 1:31:14 PM, Joe Gordon (joe.gord...@gmail.com) wrote: On Mon, Feb 2, 2015 at 10:28 AM, Morgan Fainberg morgan.fainb...@gmail.com wrote: I think the simple answer is yes. We (keystone) should emit

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

2015-02-02 Thread Joe Gordon
On Mon, Feb 2, 2015 at 10:28 AM, Morgan Fainberg morgan.fainb...@gmail.com wrote: I think the simple answer is yes. We (keystone) should emit notifications. And yes other projects should listen. The only thing really in discussion should be: 1: soft delete or hard delete? Does the service

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

2015-02-02 Thread Morgan Fainberg
On February 2, 2015 at 1:31:14 PM, Joe Gordon (joe.gord...@gmail.com) wrote: On Mon, Feb 2, 2015 at 10:28 AM, Morgan Fainberg morgan.fainb...@gmail.com wrote: I think the simple answer is yes. We (keystone) should emit notifications. And yes other projects should listen. The only thing really

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

2015-02-02 Thread Morgan Fainberg
I think the simple answer is yes. We (keystone) should emit notifications. And yes other projects should listen. The only thing really in discussion should be: 1: soft delete or hard delete? Does the service mark it as orphaned, or just delete (leave this to nova, cinder, etc to discuss) 2: