Greetings all -

Today Barbican provides a “soft” delete of resources – they remain in our 
database, tagged as deleted.

We are looking at adding quotas 
 and that introduces some pain for testing or usage patterns with many 
create/delete cycles as the quota (which includes the soft deleted resources) 
would fill up quickly making the project unusable.

Would like to gather some thoughts on how others handle this situation – making 
all deletes hard deletes isn’t an option due to things like audit trails.

OpenStack Development Mailing List (not for usage questions)

Reply via email to