On 5/27/2014 4:44 PM, Vishvananda Ishaya wrote:
I’m not sure that this is the right approach. We really have to add the old
extension back for compatibility, so it might be best to simply keep that
extension instead of adding a new way to do it.
Vish
On May 27, 2014, at 1:31 PM, Cazzolato, Sergio J <[email protected]>
wrote:
I have created a blueprint to add this functionality to nova.
https://review.openstack.org/#/c/94519/
-----Original Message-----
From: Vishvananda Ishaya [mailto:[email protected]]
Sent: Tuesday, May 27, 2014 5:11 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] nova default quotas
Phil,
You are correct and this seems to be an error. I don't think in the earlier ML
thread[1] that anyone remembered that the quota classes were being used for
default quotas. IMO we need to revert this removal as we (accidentally) removed
a Havana feature with no notification to the community. I've reactivated a
bug[2] and marked it critcal.
Vish
[1] http://lists.openstack.org/pipermail/openstack-dev/2014-February/027574.html
[2] https://bugs.launchpad.net/nova/+bug/1299517
On May 27, 2014, at 12:19 PM, Day, Phil <[email protected]> wrote:
Hi Vish,
I think quota classes have been removed from Nova now.
Phil
Sent from Samsung Mobile
-------- Original message --------
From: Vishvananda Ishaya
Date:27/05/2014 19:24 (GMT+00:00)
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [nova] nova default quotas
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 <[email protected]>
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
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
The reverted series for nova on master is here [1].
Once that's merged I can work on backporting the revert for the API
change to stable/icehouse, which will be a little tricky given conflicts
from master.
[1]
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:restore-quota-class,n,z
--
Thanks,
Matt Riedemann
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
