I am not sure we'll ever get cross-project consensus to be honest.
We can rely on something like ospurge, that cleans up tenant resources from a project by using the project's API, but this may lead to a lot of chattiness, and to potential unrecoverable errors.
If we assumed that we can have an API exposed by Neutron that purges the resources from a single tenant, this can be done a lot more effectively. It's handy to have it, but not strictly necessary. If someone were to propose an implementation (as a service plugin perhaps), we could look at its merits.
I am not sure we'll ever get cross-project consensus to be honest.
We can rely on something like ospurge, that cleans up tenant resources from a project by using the project's API, but this may lead to a lot of chattiness, and to potential unrecoverable errors.
If we assumed that we can have an API exposed by Neutron that purges the resources from a single tenant, this can be done a lot more effectively. It's handy to have it, but not strictly necessary. If someone were to propose an implementation (as a service plugin perhaps), we could look at its merits.