Open Stack

On 07/25/2013 08:24 PM, Joshua Harlow wrote:
> You mean process/forking API right?
>
> Honestly I'd sort of think the whole limits.py that is this
> rate-limiting could also be turned off by default (or a log warn message
> occurs) when multi-process nova-api is used since the control for that
> paste module actually returns the currently enforced limits (and how
> much remaining) and on repeated calls to different processes those
> values will actually be different . This adds to the confusion that this
> rate-limiting in-memory/process solution creates which does also seem bad.
>
> https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/limits.py
>
> Maybe we should not have that code in nova in the future, idk.

+10. Like using SSL in the Python daemons, it doesn't belong in a 
production Nova deployment. This kind of thing is more appropriate to 
handle in some external terminator, IMO.

Best,
-jay