Mailing
List (not for usage questions) openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] oslo removal of use_tpool conf option
On Apr 17, 2014, at 4:26 PM, Joshua Harlow harlo...@yahoo-inc.com wrote:
Just an honest question (no negativity intended I swear!).
If a configuration
It looks to me like this was removed in oslo in commit
a33989e7a2737af757648099cc1af6c642b6e016, which was synced with nova
in 605749ca12af969ac122008b4fa14904df68caf7 (however, I can't see the
change being listed in the commit message for nova, which I assume is
a process failure). That change
Just an honest question (no negativity intended I swear!).
If a configuration option exists and only works with a patched eventlet why is
that option an option to begin with? (I understand the reason for the patch,
don't get me wrong).
Most users would not be able to use such a configuration
On Apr 17, 2014, at 4:26 PM, Joshua Harlow harlo...@yahoo-inc.com wrote:
Just an honest question (no negativity intended I swear!).
If a configuration option exists and only works with a patched eventlet why
is that option an option to begin with? (I understand the reason for the
patch,
I do agree with Chris that process-wise, there was a failure and we
need a way to ensure that it does not happen again. (There was a
config option lost in the shuffle w/o a deprecation period)
On Thu, Apr 17, 2014 at 7:59 PM, Chris Behrens cbehr...@codestud.com wrote:
On Apr 17, 2014, at 4:26
@lists.openstack.org
Subject: Re: [openstack-dev] oslo removal of use_tpool conf option
On Apr 17, 2014, at 4:26 PM, Joshua Harlow
harlo...@yahoo-inc.commailto:harlo...@yahoo-inc.com wrote:
Just an honest question (no negativity intended I swear!).
If a configuration option exists and only works
