Maintaining referential integrity in (users|projects)_terminate

[Be-El]

Both XYZ_terminate method remove the keystone entities (not sure whether these methods are actually used in the code...).

Removing a project usually does not remove the project's resource like VMs, networks, routers, floating IPs... All these resources will be orphaned after removal.

Either

• remove the functions if they are not used. Otherwise developers might want to use them in their own stuff without checking the code...

• implement the correct functionality. The command line client offers a 'project purge' call, which should do the right[tm] things

• put a BIG FAT warning in the documentation to inform developers that these methods are not what they are looking for....

And correctly implementing this functionality is kind of difficult, since depending on the cloud setup you might have different kind of resources (s3/swift buckets, heat stacks, magnum based kubernetes clusters....).

[pbelmann]

And correctly implementing this functionality is kind of difficult, since depending on the cloud setup you might have different kind of resources (s3/swift buckets, heat stacks, magnum based kubernetes clusters....).

I agree. For this we will have to allow a cloud site to extend the module for cloud specific clean up functionality.