Are you aware that there is already a way to do this through the cli using quota-class-update? http://docs.openstack.org/user-guide-admin/content/cli_set_quotas.html (near the bottom) Are you suggesting that we also add the ability to use just regular quota-update? I’m not sure i see the need for both. Vish On May 20, 2014, at 9:52 AM, Cazzolato, Sergio J <sergio.j.cazzolato at intel.com> wrote: > I would to hear your thoughts about an idea to add a way to manage the default quota values through the API. > > The idea is to use the current quota api, but sending ''default' instead of the tenant_id. This change would apply to quota-show and quota-update methods. > > This approach will help to simplify the implementation of another blueprint named per-flavor-quotas > > Feedback? Suggestions? > > > Sergio Juan Cazzolato > Intel Software Argentina > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: Message signed with OpenPGP using GPGMail URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140527/74cfaf4d/attachment.pgp>