Re: [openstack-dev] [Heat] fine grained quotas
On Thu, Jun 19, 2014 at 10:21:14PM +, Randall Burt wrote: > On Jun 19, 2014, at 4:17 PM, Clint Byrum wrote: > > > I was made aware of the following blueprint today: > > > > http://blueprints.launchpad.net/heat/+spec/add-quota-api-for-heat > > http://review.openstack.org/#/c/96696/14 > > > > Before this goes much further.. I want to suggest that this work be > > cancelled, even though the code looks excellent. The reason those limits > > are in the config file is that these are not billable items and they > > have a _tiny_ footprint in comparison to the physical resources they > > will allocate in Nova/Cinder/Neutron/etc. > > > > IMO we don't need fine grained quotas in Heat because everything the > > user will create with these templates will cost them and have its own > > quota system. The limits (which I added) are entirely to prevent a DoS > > of the engine. > > What's more, I don't think this is something we should expose via API other > than to perhaps query what those quota values are. It is possible that some > provider would want to bill on number of stacks, etc (I personally agree with > Clint here), it seems that is something that could/should be handled external > to Heat itself. I do think we need a read API for the config file "absolute limits", which is why I raised this a while back: https://blueprints.launchpad.net/heat/+spec/limits-api This has been implemented by Huangtianhua, on top of the quota series: https://review.openstack.org/#/c/99589/ I agree more use-case discussion about the quota functionality would be useful, so far the main arguments for the functionality I've heard are: 1. "Rally needs it" - I'm not yet clear exactly why, can anyone explain? 2. Other projects have this API As has been highlighted, the second point may be of questionable relevance due to the lack of a direct correlation between e.g the number of stacks and the resources consumed. This is related to another recent discussion, where replacing the nested stack depth limit with a recursive resource count was discussed. If we're going to have quotas in heat, then personally I think just one limit which is total number of resources (per tenant) would be a good starting point, rather than making everything configurable, which could make things confusing for users and operators. Steve ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Heat] fine grained quotas
Excerpts from Randall Burt's message of 2014-06-19 15:21:14 -0700: > On Jun 19, 2014, at 4:17 PM, Clint Byrum wrote: > > > I was made aware of the following blueprint today: > > > > http://blueprints.launchpad.net/heat/+spec/add-quota-api-for-heat > > http://review.openstack.org/#/c/96696/14 > > > > Before this goes much further.. I want to suggest that this work be > > cancelled, even though the code looks excellent. The reason those limits > > are in the config file is that these are not billable items and they > > have a _tiny_ footprint in comparison to the physical resources they > > will allocate in Nova/Cinder/Neutron/etc. > > > > IMO we don't need fine grained quotas in Heat because everything the > > user will create with these templates will cost them and have its own > > quota system. The limits (which I added) are entirely to prevent a DoS > > of the engine. > > What's more, I don't think this is something we should expose via > API other than to perhaps query what those quota values are. It is > possible that some provider would want to bill on number of stacks, etc > (I personally agree with Clint here), it seems that is something that > could/should be handled external to Heat itself. Far be it from any of us to dictate a single business model. However, Heat is a tool which encourages consumption of billable resources by making it easier to tie them together. This is why FedEx gives away envelopes and will come pick up your packages for free. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Heat] fine grained quotas
On Jun 19, 2014, at 4:17 PM, Clint Byrum wrote: > I was made aware of the following blueprint today: > > http://blueprints.launchpad.net/heat/+spec/add-quota-api-for-heat > http://review.openstack.org/#/c/96696/14 > > Before this goes much further.. I want to suggest that this work be > cancelled, even though the code looks excellent. The reason those limits > are in the config file is that these are not billable items and they > have a _tiny_ footprint in comparison to the physical resources they > will allocate in Nova/Cinder/Neutron/etc. > > IMO we don't need fine grained quotas in Heat because everything the > user will create with these templates will cost them and have its own > quota system. The limits (which I added) are entirely to prevent a DoS > of the engine. What's more, I don't think this is something we should expose via API other than to perhaps query what those quota values are. It is possible that some provider would want to bill on number of stacks, etc (I personally agree with Clint here), it seems that is something that could/should be handled external to Heat itself. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
