notification_driver is poorly documented
Bug #1394397 reported by
Andrew Bogott
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
Low
|
Joseph Robinson |
Bug Description
notification_driver is only barely mentioned in the nova docs. Where it is mentioned, it says terse things like "Driver or drivers to handle sending notifications"
The behavior of that setting has changed radically from version to version, with no updates in docs. In Icehouse, notification_driver can be set to several built-in drivers, none of them enumerated in docs as far as I can see. It can also refer to a custom notifier, but that notifier needs an entrypoint in the (again, undocumented) oslo.messaging.
(In Havana, it didn't use an entrypoint but just specified a file in the python path. In Juno or Kilo, who knows?)
Changed in openstack-manuals: | |
status: | New → Confirmed |
importance: | Undecided → Low |
tags: | added: nova |
tags: |
added: oslo removed: nova |
Changed in openstack-manuals: | |
status: | Confirmed → Won't Fix |
tags: | added: ops-guide |
tags: |
added: ops removed: ops-guide |
Changed in openstack-manuals: | |
assignee: | nobody → Joseph Robinson (joseph-r-email) |
To post a comment you must log in.
* This is internal glue, albeit configurable internal glue, but it doesn't really have an end-user impact. For that reason, it probably belongs in dev or API docs, more than openstack-manuals.
* As far as we can tell (and I understand this is a difficult thing to measure), this driver is only minimally in use, so the impact even to devs is pretty trivial
I have contacted the Nova PTL, Oslo PTL, and the Oslo docs liaison regarding this. Please feel free to raise an objection and reopen if you feel I've closed this in error.