[openstack-dev] [trove]

Michael Basnight mbasnight at gmail.com
Tue Oct 8 15:14:08 UTC 2013


> On Oct 8, 2013, at 4:16 AM, Denis Makogon <dmakogon at mirantis.com> wrote:
> 
> Hi, guys, i'd like to make few questions clear to all of us.
> 
> First one is resource clean-up in Trove.
> 
> According to few previous meetings we decided not to rollback each of resources which is under trove-quota-management controll.

Correct. The delete call will clean up a tenants resources. 

> 
> Let's go deeper. I'm going to cover security groups rollback process if instance didn't became active.
> 
> As compute instance part security groups are controled be Tenants Quotas, so if quota is exceeded there is no chanse to create new one.

As you stated, we covered this. The only way the user would see this was if their trove limits were higher than their nova limits. That would constitute a bad configuration on the part of the operator, not something we would try to deal with in code. The delete call removes resources. 




More information about the OpenStack-dev mailing list