On 1/15/2017 12:53 AM, Joshua Harlow wrote:
Cascading deletes,
Ie when a tenant/project/user is removed from keystone there should be
someway to say deny that request if that tenant/project/user has active
resources or there should be a away to cascade that delete through the
rest of those resources (so they are deleted also).
FWIW there is an older thread about this very same thing:
http://lists.openstack.org/pipermail/openstack-operators/2015-February/006118.html
Maybe it becomes a product or architecture work group item to start
thinking about? For stuff like this there is really no traction until
some individual takes it on themselves to start pushing that boulder.
--
Thanks,
Matt Riedemann
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
