Comment 3 for bug 1771582

I see that we should really create a new description of this "cross project issue", and leave out technical solutions as discussed in Denver.

Personally, using something like ospurge could be fine, if it's something that is under maintenance (especially security maintenance) and something "official", if not it will be hard to put into production. Could be that it's functionality is moved into the openstack client as well. What I know of right now regarding ospurge is that that's not the case, please correct me if I'm wrong.

Also, same functionality should be available for the web REST API to serve operators that integrate that way.