openstack
/
neutron-dynamic-routing
Code Issues Proposed changes

Set timetable for removal of oslo.messaging.notify.drivers 

Icehouse is dead and gone, at least upstream. These special driver
registrations are not tested in the gate-tempest-dsvm-neutron-full job
which means they are also not tested in requirements constraints jobs.

oslo.messaging 2.6.0 broke these already by removing the internal modules,
which was fixed in o.m 3.0.0 with (deprecated) alias modules.

The minimum required version of o.m in mitaka is currently greater than
2.6.1, so we're OK to remove these once stable/mitaka is our oldest
supported branch. So add a TODO to remove these once liberty-eol happens.

Proper configuration for notification drivers happens through the
config file using the oslo_messaging options:

http://docs.openstack.org/developer/oslo.messaging/opts.html

Adds a release note for the deprecation and timetable.

Change-Id: I2c04117b0f531fe3604e74401d0ffd8d8d3dd308
Related-Bug: #1513630
This commit is contained in:
Matt Riedemann 2015-11-19 18:43:07 -08:00
parent 2ad04a57b0
commit f6e7a282ac
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
setup.cfg
View File

@ -117,6 +117,7 @@ neutron.qos.agent_drivers =
neutron.agent.linux.pd_drivers =
dibbler = neutron.agent.linux.dibbler:PDDibbler
# These are for backwards compat with Icehouse notification_driver configuration values
# TODO(mriedem): Remove these once liberty-eol happens.
oslo.messaging.notify.drivers =
neutron.openstack.common.notifier.log_notifier = oslo_messaging.notify._impl_log:LogDriver
neutron.openstack.common.notifier.no_op_notifier = oslo_messaging.notify._impl_noop:NoOpDriver