Unable to modify quotas for router or floatingip with DB quota driver

[Kalle Happonen]

I'm using the following drivers for quantum quotas
quota_driver = quantum.extensions._quotav2_driver.DbQuotaDriver

I can modify some of the quotas, e.g.

 quantum quota-update --tenant-id basictenant --network 3
which: no gedit in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
which: no kate in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
+------------+-------+
| Field | Value |
+------------+-------+
| floatingip | 50 |
| network | 3 |
| port | 50 |
| router | 10 |
| subnet | 10 |
+------------+-------+

But when I try to modify floatingip or router, I get a message like this

quantum quota-update --tenant-id basictenant --floatingip 3
which: no gedit in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
which: no kate in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
usage: quantum quota-update [-h] [-f {html,json,shell,table,yaml}] [-c COLUMN]
                            [--variable VARIABLE] [--prefix PREFIX]
                            [--request-format {json,xml}]
                            [--tenant-id tenant-id] [--network networks]
                            [--subnet subnets] [--port ports]
                            ...
quantum quota-update: error: unrecognized arguments: --floatingip

So it seems that the quota driver is somewhat aware of the floatingip and router quotas (at least it displays them), but the usage message seems to indicate it doesn't know of them.

[Akihiro Motoki (amotoki)]

To update the limits of L3 resource (router, floating IP), we need to specify new values of the quotas after '--'.
quantum quota-update --tenant_id 6f88036c45344d9999a1f971e4882723 -- --floatingip 20

Admin guide has examples how to modify per-tenant quota. I hope it will help you.
http://docs.openstack.org/folsom/openstack-network/admin/content/cfg_quotas_per_tenant.html

Of cource, I agree that such command line options are very confusing and we need to fix it.

[Akihiro Motoki (amotoki)]

This bug is a client-side bug, so I moved it from quantum to quantumclient.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/17343

[Kalle Happonen (kalle-happonen)]

Yes, I should RTFM :). But true it's a bit confusing, and thanks for fixing it.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/17343
Committed: http://github.com/openstack/python-quantumclient/commit/45c471899ba30b7db970b27976f749a16a2fdb92
Submitter: Jenkins
Branch: master

commit 45c471899ba30b7db970b27976f749a16a2fdb92
Author: Akihiro MOTOKI <email address hidden>
Date: Mon Dec 3 20:10:38 2012 +0900

    Add --router and --floatingip to quota-update options.

    Fixes bug 1085820

    Change-Id: I333b21414ec159cbf8474d47bd8ba3c6bd3cf8ad