[Openstack-operators] Fwd: [openstack-dev] [all] config options not correctly deprecated
spasquier at mirantis.com
Fri Nov 14 09:50:49 UTC 2014
For those who aren't scrutinizing the openstack-dev mailing list, Derek
Higgins from the TripleO team found an "interesting" behavior in
oslo.config: it doesn't log warnings when deprecated options are used .
I'm pretty sure that at some point, deprecated options used to be logged
but apparently the switch to oslo.config removed that.
The general policy in OpenStack is to remove deprecated options after just
1 cycle so you should be very careful checking your configuration files
against the documentation  before upgrading.
Finally a bug  has been opened against oslo.config to log a warning
every time a deprecated option is found. I've added the 'ops' tag to it as
it is likely that operators would love to see happen.
---------- Forwarded message ----------
From: Derek Higgins <derekh at redhat.com>
Date: Mon, Nov 10, 2014 at 10:45 AM
Subject: [openstack-dev] [all] config options not correctly deprecated
To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org>
Tl;dr oslo.config wasn't logging warnings about deprecated config
options, do we need to support them for another cycle?
A set of patches to remove deprecated options in Nova was landed on
Thursday, these were marked as deprecated during the juno dev cycle
and got removed now that kilo has started.
Most of the deprecated config options are listed as deprecated in the
documentation for nova.conf changes linked to from the Nova upgrade
section in the Juno release notes (the deprecated cinder config
options are not listed here along with the allowed_direct_url_schemes
My main worry is that there were no warnings about these options being
deprecated in nova's logs (as a result they were still being used in
tripleo), once I noticed tripleo's CI jobs were failing and discovered
the reason I submitted 4 reverts to put back the deprecated options in
nova as I believe they should now be supported for another cycle
(along with a fix to oslo.config to log warnings about their use). The 4
patches have now been blocked as they go "against our deprecation policy".
I believe the correct way to handle this is to support these options for
another cycle so that other operators don't get hit when upgrading to
kilo. While at that same time fix oslo.config to report the deprecated
options in kilo.
I have marked this mail with the [all] tag because there are other
projects using the same "deprecated_name" (or "deprecated_group")
parameter when adding config options, I think those projects also now
need to support their deprecated options for another cycle.
I've also opened a bug for this against tripleo, nova and oslo.conf
and for the moment in tripleo-ci I have pinned the version of nova we
use to something from before the commits were merged while we get a
chance to correctly use the new name for each of the options that were
On a side node, When trying to look up the deprecation policy I wasn't
able to find it so if anybody has a link handy can you point me at it.
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-operators