<div dir="ltr"><div><div>Hello,<br></div>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 [1]. I'm pretty sure that at some point, deprecated options used to be logged but apparently the switch to oslo.config removed that.<br>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 [2] before upgrading.<br></div><div>Finally a bug [3] 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.<br></div><div>BR,<br></div>Simon<br>[1] <a href="http://lists.openstack.org/pipermail/openstack-dev/2014-November/050036.html">http://lists.openstack.org/pipermail/openstack-dev/2014-November/050036.html</a><br>[2] <a href="http://docs.openstack.org/juno/config-reference/content/nova-conf-changes-juno.html">http://docs.openstack.org/juno/config-reference/content/nova-conf-changes-juno.html</a><br>[3] <a href="https://bugs.launchpad.net/oslo.config/+bug/1390408">https://bugs.launchpad.net/oslo.config/+bug/1390408</a><br><div><div><div><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Derek Higgins</b> <span dir="ltr"><<a href="mailto:derekh@redhat.com">derekh@redhat.com</a>></span><br>Date: Mon, Nov 10, 2014 at 10:45 AM<br>Subject: [openstack-dev] [all] config options not correctly deprecated<br>To: OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br><br><br>Tl;dr oslo.config wasn't logging warnings about deprecated config<br>
options, do we need to support them for another cycle?<br>
<br>
A set of patches to remove deprecated options in Nova was landed on<br>
Thursday[1], these were marked as deprecated during the juno dev cycle<br>
and got removed now that kilo has started.<br>
<br>
Most of the deprecated config options are listed as deprecated in the<br>
documentation for nova.conf changes[2] linked to from the Nova upgrade<br>
section in the Juno release notes[3] (the deprecated cinder config<br>
options are not listed here along with the allowed_direct_url_schemes<br>
glance option).<br>
<br>
My main worry is that there were no warnings about these options being<br>
deprecated in nova's logs (as a result they were still being used in<br>
tripleo), once I noticed tripleo's CI jobs were failing and discovered<br>
the reason I submitted 4 reverts to put back the deprecated options in<br>
nova[4] as I believe they should now be supported for another cycle<br>
(along with a fix to oslo.config to log warnings about their use). The 4<br>
patches have now been blocked as they go "against our deprecation policy".<br>
<br>
I believe the correct way to handle this is to support these options for<br>
another cycle so that other operators don't get hit when upgrading to<br>
kilo. While at that same time fix oslo.config to report the deprecated<br>
options in kilo.<br>
<br>
I have marked this mail with the [all] tag because there are other<br>
projects using the same "deprecated_name" (or "deprecated_group")<br>
parameter when adding config options, I think those projects also now<br>
need to support their deprecated options for another cycle.<br>
<br>
I've also opened a bug for this against tripleo, nova and oslo.conf[5]<br>
and for the moment in tripleo-ci I have pinned the version of nova we<br>
use to something from before the commits were merged while we get a<br>
chance to correctly use the new name for each of the options that were<br>
deprecated.<br>
<br>
On a side node, When trying to look up the deprecation policy I wasn't<br>
able to find it so if anybody has a link handy can you point me at it.<br>
<br>
Thanks,<br>
Derek<br>
<br>
[1] <a href="https://review.openstack.org/#/c/132900/" target="_blank">https://review.openstack.org/#/c/132900/</a><br>
<a href="https://review.openstack.org/#/c/132887/" target="_blank">https://review.openstack.org/#/c/132887/</a><br>
<a href="https://review.openstack.org/#/c/132885/" target="_blank">https://review.openstack.org/#/c/132885/</a><br>
<a href="https://review.openstack.org/#/c/132901/" target="_blank">https://review.openstack.org/#/c/132901/</a><br>
[2]<br>
<a href="http://docs.openstack.org/trunk/config-reference/content/nova-conf-changes-master.html" target="_blank">http://docs.openstack.org/trunk/config-reference/content/nova-conf-changes-master.html</a><br>
[3] <a href="https://wiki.openstack.org/wiki/ReleaseNotes/Juno#Upgrade_Notes_2" target="_blank">https://wiki.openstack.org/wiki/ReleaseNotes/Juno#Upgrade_Notes_2</a><br>
[4]<br>
<a href="https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:redeprecate,n,z" target="_blank">https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:redeprecate,n,z</a><br>
[5] <a href="https://bugs.launchpad.net/tripleo/+bug/1390427" target="_blank">https://bugs.launchpad.net/tripleo/+bug/1390427</a><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div><br></div></div></div></div>