notification options in quantum.conf is not self explained
Bug #1056637 reported by
yong sheng gong
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
yong sheng gong |
Bug Description
The list_notificati
Changed in quantum: | |
milestone: | none → grizzly-1 |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
milestone: | grizzly-1 → 2013.1 |
To post a comment you must log in.
the right ones should be: ======= =======
# ============ Notification System Options =======
# Notifications can be sent when network/subnet/port are create, updated or deleted.
# There are three methods of sending notifications: logging (via the
# log_file directive), rpc (via a message queue) and
# noop (no notifications sent, the default)
# Notification_driver can be defined multiple times openstack. common. notifier. no_op_notifier openstack. common. notifier. log_notifier openstack. common. notifier. rabbit_ notifier
# Do nothing driver
# notification_driver = quantum.
# Logging driver
# notification_driver = quantum.
# RPC driver
# notification_driver = quantum.
# default_ notification_ level is used to form actual topic names or to set logging level notification_ level = INFO
# default_
# default_ publisher_ id is a part of the notification payload publisher_ id = $host
# host = myhost.com
# default_
# Defined in rabbit_notifier for rpc way, can be comma separated values. notification_ level)s
# The actual topic names will be %s.%(default_
# notification_topics = notifications