CONF.notification_driver should be StrMultiOpt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-common |
Fix Released
|
Medium
|
Andrew Bogott |
Bug Description
Right now we have an optional notifier driver, list_notifier, which handles n notifiers. It works perfectly well for n = 0 or 1, so there's no real reason to not always use the list notifier. And, going further, there's no reason to consider the list_notifier to be a driver at all; the list behavior should be promoted into the notifier api so that the notifier api always handles n drivers rather than 0 or 1.
The problem that this solves:
There's code in the pluginmanager that switches CONF.notificati
Problems this might cause:
Thanks to the existing behavior of StrMultiOpt, existing installs that set CONF.list_notifier once, e.g.
$ notification_driver = foozle
...will still work as before. If, however, someone has a buggy nova.conf that sets CONF.list_notifier twice
$ notification_driver = foozle
$ notification_driver = oopsIMeantFazzle
...the behavior will change, as previously only the second driver was used, but in the StrMultiOpt scenario both drivers will be used.
This could be avoided by instituting a new CONF.notificati
description: | updated |
Changed in openstack-common: | |
assignee: | nobody → Andrew Bogott (andrewbogott) |
Changed in openstack-common: | |
milestone: | none → folsom-3 |
importance: | Undecided → Medium |
Changed in openstack-common: | |
milestone: | folsom-3 → 2012.2 |
status: | Fix Committed → Fix Released |
At first glance, making it MultiStrOpt seems reasonable to me
MultiStrOpts should be singular, ListOpts should be plural i.e.
notification_ driver = foo driver = bar
notification_
vs
notification_ drivers = foo,bar