Manage Quantum Quota Driver

[Daneyon Hansen]

The default Quantum quota driver contains the following bug which does not allow users to manage quotas:

https://bugs.launchpad.net/tripleo/+bug/1188651

Here is an example of the issue from the CLI:

root@control01:~# quantum quota-show
+---------------------+-------+
| Field | Value |
+---------------------+-------+
| floatingip | 50 |
| network | 10 |
| port | 50 |
| router | 10 |
| security_group | 10 |
| security_group_rule | 100 |
| subnet | 10 |
+---------------------+-------+

root@control01:~# quantum quota-update --port 70
{"QuantumError": "Access was denied to this resource."}

After changing the default quota driver in quantum.conf to:

quota_driver = quantum.db.quota_db.DbQuotaDriver

root@control01:~# quantum quota-update --port 70
+---------------------+-------+
| Field | Value |
+---------------------+-------+
| floatingip | 90 |
| network | 10 |
| port | 70 |
| router | 10 |
| security_group | 10 |
| security_group_rule | 100 |
| subnet | 10 |
+---------------------+-------+

The quantum::quota class currently contains a parameter for managing the quota driver. We should expose the driver parameter and set the default to 'quantum.db.quota_db.DbQuotaDriver' in our core/site manifests.

[Mark T. Voelker (mvoelker)]

Just to clarify, I believe the quantum.quota.ConfDriver is behaving as expected. This is a request to switch to a more featureful quota driver. Correct?

[Daneyon Hansen (danehans)]

I'm new to the quota driver, but it seems like this is unexpected behavior. You are unable to manage quotas when using the default driver.

[Mark T. Voelker (mvoelker)]

I believe you can manage them: you just have to do it through quantum.conf since quotas are the same for all tenants and that's where they're specified. That's essentially how I read that TripleO bug report you linked to and the corresponding docs that it points to (Grizzly versions rather than trunk linked below):

http://docs.openstack.org/grizzly/openstack-network/admin/content/cfg_quotas_common.html

http://docs.openstack.org/grizzly/openstack-network/admin/content/cfg_quotas_per_tenant.html

[Daneyon Hansen (danehans)]

Good point, I only tried managing quotas through the CLI. I just tested the q.conf approach and that works too. However, using the q.conf approach will give the same quotas to all tenants. I think most customers want per tenant quotas.

[Mark T. Voelker (mvoelker)]

Yeah, I'm fine with switching drivers. I just wanted to clarify for triage purposes whether you were requesting a new feature, requesting a workaround to an upstream bug, or saying there was a bug in COI itself (e.g. something we were doing wrong that was causing Quantum to misbehave). Sounds like it's the former and should be pretty simple to implement.

[Mark T. Voelker (mvoelker)]

Moving to h.0 due to https://bugs.launchpad.net/bugs/1189671 which indicates that DbQuotaDriver will be the new default in Havana.

[Mark T. Voelker (mvoelker)]

As mentioned above, DbQuotaDriver is now the default driver as of Hanava. It is also now the default in puppet-neutron, so this is now remedied.