47 lines
2.2 KiB
XML
47 lines
2.2 KiB
XML
<?xml version='1.0' encoding='UTF-8'?>
|
|
<para xmlns="http://docbook.org/ns/docbook" version="5.0">
|
|
<!-- Warning: Do not edit this file. It is automatically
|
|
generated and your changes will be overwritten.
|
|
The tool to do so lives in openstack-doc-tools repository. -->
|
|
<table rules="all" xml:id="config_table_keystone_amqp">
|
|
<caption>Description of AMQP configuration options</caption>
|
|
<col width="50%"/>
|
|
<col width="50%"/>
|
|
<thead>
|
|
<tr>
|
|
<th>Configuration option = Default value</th>
|
|
<th>Description</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr>
|
|
<th colspan="2">[DEFAULT]</th>
|
|
</tr>
|
|
<tr>
|
|
<td><option>control_exchange</option> = <replaceable>keystone</replaceable></td>
|
|
<td>(StrOpt) The default exchange under which topics are scoped. May be overridden by an exchange name specified in the transport_url option.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><option>default_publisher_id</option> = <replaceable>None</replaceable></td>
|
|
<td>(StrOpt) Default publisher_id for outgoing notifications</td>
|
|
</tr>
|
|
<tr>
|
|
<td><option>notification_driver</option> = <replaceable>[]</replaceable></td>
|
|
<td>(MultiStrOpt) The Drivers(s) to handle sending notifications. Possible values are messaging, messagingv2, routing, log, test, noop</td>
|
|
</tr>
|
|
<tr>
|
|
<td><option>notification_format</option> = <replaceable>basic</replaceable></td>
|
|
<td>(StrOpt) Define the notification format for Identity Service events. A "basic" notification has information about the resource being operated on. A "cadf" notification has the same information, as well as information about the initiator of the event.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><option>notification_topics</option> = <replaceable>notifications</replaceable></td>
|
|
<td>(ListOpt) AMQP topic used for OpenStack notifications.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><option>transport_url</option> = <replaceable>None</replaceable></td>
|
|
<td>(StrOpt) A URL representing the messaging driver to use and its full configuration. If not set, we fall back to the rpc_backend option and driver specific configuration.</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</para>
|