zaqar.conf
DEFAULT
-
auth_strategy
-
Backend to use for authentication. For no auth, keep it empty. Existing strategies: keystone. See also the keystone_authtoken section below
-
admin_mode
| Type: | boolean |
| Default: | false |
Activate privileged endpoints.
-
pooling
| Type: | boolean |
| Default: | false |
Enable pooling across multiple storage backends. If pooling is enabled, the storage driver configuration is used to determine where the catalogue/control plane data is kept.
Deprecated Variations
| Group |
Name |
| DEFAULT |
sharding |
-
unreliable
| Type: | boolean |
| Default: | false |
Disable all reliability constraints.
-
enable_deprecated_api_versions
-
List of deprecated API versions to enable.
-
enable_checksum
| Type: | boolean |
| Default: | false |
Enable a checksum for message body. The default value is False.
-
rpc_conn_pool_size
-
Size of RPC connection pool.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_conn_pool_size |
-
conn_pool_min_size
-
The pool size limit for connections expiration policy
-
conn_pool_ttl
| Type: | integer |
| Default: | 1200 |
The time-to-live in sec of idle connections in the pool
-
rpc_zmq_bind_address
-
ZeroMQ bind address. Should be a wildcard (*), an ethernet interface, or IP. The “host” option should point or resolve to this address.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_bind_address |
-
rpc_zmq_matchmaker
| Type: | string |
| Default: | redis |
| Valid Values: | redis, sentinel, dummy |
MatchMaker driver.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_matchmaker |
-
rpc_zmq_contexts
-
Number of ZeroMQ contexts, defaults to 1.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_contexts |
-
rpc_zmq_topic_backlog
| Type: | integer |
| Default: | <None> |
Maximum number of ingress messages to locally buffer per topic. Default is unlimited.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_topic_backlog |
-
rpc_zmq_ipc_dir
| Type: | string |
| Default: | /var/run/openstack |
Directory for holding IPC sockets.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_ipc_dir |
-
rpc_zmq_host
| Type: | string |
| Default: | localhost |
Name of this node. Must be a valid hostname, FQDN, or IP address. Must match “host” option, if running Nova.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_host |
-
zmq_linger
-
Number of seconds to wait before all pending messages will be sent after closing a socket. The default value of -1 specifies an infinite linger period. The value of 0 specifies no linger period. Pending messages shall be discarded immediately when the socket is closed. Positive values specify an upper bound for the linger period.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_cast_timeout |
-
rpc_poll_timeout
-
The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_poll_timeout |
-
zmq_target_expire
-
Expiration timeout in seconds of a name service record about existing target ( < 0 means no timeout).
Deprecated Variations
| Group |
Name |
| DEFAULT |
zmq_target_expire |
-
zmq_target_update
-
Update period in seconds of a name service record about existing target.
Deprecated Variations
| Group |
Name |
| DEFAULT |
zmq_target_update |
-
use_pub_sub
| Type: | boolean |
| Default: | false |
Use PUB/SUB pattern for fanout methods. PUB/SUB always uses proxy.
Deprecated Variations
| Group |
Name |
| DEFAULT |
use_pub_sub |
-
use_router_proxy
| Type: | boolean |
| Default: | false |
Use ROUTER remote proxy.
Deprecated Variations
| Group |
Name |
| DEFAULT |
use_router_proxy |
-
use_dynamic_connections
| Type: | boolean |
| Default: | false |
This option makes direct connections dynamic or static. It makes sense only with use_router_proxy=False which means to use direct connections for direct message types (ignored otherwise).
-
zmq_failover_connections
-
How many additional connections to a host will be made for failover reasons. This option is actual only in dynamic connections mode.
-
rpc_zmq_min_port
| Type: | port number |
| Default: | 49153 |
| Minimum Value: | 0 |
| Maximum Value: | 65535 |
Minimal port number for random ports range.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_min_port |
-
rpc_zmq_max_port
| Type: | integer |
| Default: | 65536 |
| Minimum Value: | 1 |
| Maximum Value: | 65536 |
Maximal port number for random ports range.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_max_port |
-
rpc_zmq_bind_port_retries
-
Number of retries to find free port number before fail with ZMQBindError.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_bind_port_retries |
-
rpc_zmq_serialization
| Type: | string |
| Default: | json |
| Valid Values: | json, msgpack |
Default serialization mechanism for serializing/deserializing outgoing/incoming messages
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_serialization |
-
zmq_immediate
| Type: | boolean |
| Default: | true |
This option configures round-robin mode in zmq socket. True means not keeping a queue when server side disconnects. False means to keep queue and messages even if server is disconnected, when the server appears we send all accumulated messages to it.
-
zmq_tcp_keepalive
-
Enable/disable TCP keepalive (KA) mechanism. The default value of -1 (or any other negative value) means to skip any overrides and leave it to OS default; 0 and 1 (or any other positive value) mean to disable and enable the option respectively.
-
zmq_tcp_keepalive_idle
-
The duration between two keepalive transmissions in idle condition. The unit is platform dependent, for example, seconds in Linux, milliseconds in Windows etc. The default value of -1 (or any other negative value and 0) means to skip any overrides and leave it to OS default.
-
zmq_tcp_keepalive_cnt
-
The number of retransmissions to be carried out before declaring that remote end is not available. The default value of -1 (or any other negative value and 0) means to skip any overrides and leave it to OS default.
-
zmq_tcp_keepalive_intvl
-
The duration between two successive keepalive retransmissions, if acknowledgement to the previous keepalive transmission is not received. The unit is platform dependent, for example, seconds in Linux, milliseconds in Windows etc. The default value of -1 (or any other negative value and 0) means to skip any overrides and leave it to OS default.
-
rpc_thread_pool_size
-
Maximum number of (green) threads to work concurrently.
-
rpc_message_ttl
-
Expiration timeout in seconds of a sent/received message after which it is not tracked anymore by a client/server.
-
rpc_use_acks
| Type: | boolean |
| Default: | false |
Wait for message acknowledgements from receivers. This mechanism works only via proxy without PUB/SUB.
-
rpc_ack_timeout_base
-
Number of seconds to wait for an ack from a cast/call. After each retry attempt this timeout is multiplied by some specified multiplier.
-
rpc_ack_timeout_multiplier
-
Number to multiply base ack timeout by after each retry attempt.
-
rpc_retry_attempts
-
Default number of message sending attempts in case of any problems occurred: positive value N means at most N retries, 0 means no retries, None or -1 (or any other negative values) mean to retry forever. This option is used only if acknowledgments are enabled.
-
subscribe_on
-
List of publisher hosts SubConsumer can subscribe on. This option has higher priority then the default publishers list taken from the matchmaker.
-
executor_thread_pool_size
-
Size of executor thread pool when executor is threading or eventlet.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_thread_pool_size |
-
rpc_response_timeout
-
Seconds to wait for a response from a call.
-
transport_url
| Type: | string |
| Default: | <None> |
The network address and optional user credentials for connecting to the messaging backend, in URL format. The expected format is:
driver://[user:pass@]host:port[,[userN:passN@]hostN:portN]/virtual_host?query
Example: rabbit://rabbitmq:password@127.0.0.1:5672//
For full details on the fields in the URL see the documentation of oslo_messaging.TransportURL at https://docs.openstack.org/oslo.messaging/latest/reference/transport.html
-
rpc_backend
| Type: | string |
| Default: | rabbit |
The messaging driver to use, defaults to rabbit. Other drivers include amqp and zmq.
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Replaced by [DEFAULT]/transport_url |
-
control_exchange
| Type: | string |
| Default: | openstack |
The default exchange under which topics are scoped. May be overridden by an exchange name specified in the transport_url option.
-
debug
| Type: | boolean |
| Default: | false |
| Mutable: | This option can be changed without restarting. |
If set to true, the logging level will be set to DEBUG instead of the default INFO level.
-
log_config_append
| Type: | string |
| Default: | <None> |
| Mutable: | This option can be changed without restarting. |
The name of a logging configuration file. This file is appended to any existing logging configuration files. For details about logging configuration files, see the Python logging module documentation. Note that when logging configuration files are used then all logging configuration is set in the configuration file and other logging configuration options are ignored (for example, logging_context_format_string).
Deprecated Variations
| Group |
Name |
| DEFAULT |
log-config |
| DEFAULT |
log_config |
-
log_date_format
| Type: | string |
| Default: | %Y-%m-%d %H:%M:%S |
Defines the format string for %(asctime)s in log records. Default: the value above . This option is ignored if log_config_append is set.
-
log_file
| Type: | string |
| Default: | <None> |
(Optional) Name of log file to send logging output to. If no default is set, logging will go to stderr as defined by use_stderr. This option is ignored if log_config_append is set.
Deprecated Variations
| Group |
Name |
| DEFAULT |
logfile |
-
log_dir
| Type: | string |
| Default: | <None> |
(Optional) The base directory used for relative log_file paths. This option is ignored if log_config_append is set.
Deprecated Variations
| Group |
Name |
| DEFAULT |
logdir |
-
watch_log_file
| Type: | boolean |
| Default: | false |
Uses logging handler designed to watch file system. When log file is moved or removed this handler will open a new log file with specified path instantaneously. It makes sense only if log_file option is specified and Linux platform is used. This option is ignored if log_config_append is set.
-
use_syslog
| Type: | boolean |
| Default: | false |
Use syslog for logging. Existing syslog format is DEPRECATED and will be changed later to honor RFC5424. This option is ignored if log_config_append is set.
-
use_journal
| Type: | boolean |
| Default: | false |
Enable journald for logging. If running in a systemd environment you may wish to enable journal support. Doing so will use the journal native protocol which includes structured metadata in addition to log messages.This option is ignored if log_config_append is set.
-
syslog_log_facility
| Type: | string |
| Default: | LOG_USER |
Syslog facility to receive log lines. This option is ignored if log_config_append is set.
-
use_json
| Type: | boolean |
| Default: | false |
Use JSON formatting for logging. This option is ignored if log_config_append is set.
-
use_stderr
| Type: | boolean |
| Default: | false |
Log output to standard error. This option is ignored if log_config_append is set.
-
logging_context_format_string
| Type: | string |
| Default: | %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user_identity)s] %(instance)s%(message)s |
Format string to use for log messages with context.
-
logging_default_format_string
| Type: | string |
| Default: | %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [-] %(instance)s%(message)s |
Format string to use for log messages when context is undefined.
-
logging_debug_format_suffix
| Type: | string |
| Default: | %(funcName)s %(pathname)s:%(lineno)d |
Additional data to append to log message when logging level for the message is DEBUG.
-
logging_exception_prefix
| Type: | string |
| Default: | %(asctime)s.%(msecs)03d %(process)d ERROR %(name)s %(instance)s |
Prefix each line of exception output with this format.
-
logging_user_identity_format
| Type: | string |
| Default: | %(user)s %(tenant)s %(domain)s %(user_domain)s %(project_domain)s |
Defines the format string for %(user_identity)s that is used in logging_context_format_string.
-
default_log_levels
| Type: | list |
| Default: | amqp=WARN,amqplib=WARN,boto=WARN,qpid=WARN,sqlalchemy=WARN,suds=INFO,oslo.messaging=INFO,oslo_messaging=INFO,iso8601=WARN,requests.packages.urllib3.connectionpool=WARN,urllib3.connectionpool=WARN,websocket=WARN,requests.packages.urllib3.util.retry=WARN,urllib3.util.retry=WARN,keystonemiddleware=WARN,routes.middleware=WARN,stevedore=WARN,taskflow=WARN,keystoneauth=WARN,oslo.cache=INFO,dogpile.core.dogpile=INFO |
List of package logging levels in logger=LEVEL pairs. This option is ignored if log_config_append is set.
-
publish_errors
| Type: | boolean |
| Default: | false |
Enables or disables publication of error events.
-
instance_format
| Type: | string |
| Default: | "[instance: %(uuid)s] " |
The format for an instance that is passed with the log message.
-
instance_uuid_format
| Type: | string |
| Default: | "[instance: %(uuid)s] " |
The format for an instance UUID that is passed with the log message.
-
rate_limit_interval
-
Interval, number of seconds, of log rate limiting.
-
rate_limit_burst
-
Maximum number of logged messages per rate_limit_interval.
-
rate_limit_except_level
| Type: | string |
| Default: | CRITICAL |
Log level name used by rate limiting: CRITICAL, ERROR, INFO, WARNING, DEBUG or empty string. Logs with level greater or equal to rate_limit_except_level are not filtered. An empty string means that all levels are filtered.
-
fatal_deprecations
| Type: | boolean |
| Default: | false |
Enables or disables fatal status of deprecations.
cache
-
config_prefix
| Type: | string |
| Default: | cache.oslo |
Prefix for building the configuration dictionary for the cache region. This should not need to be changed unless there is another dogpile.cache region with the same configuration name.
-
expiration_time
-
Default TTL, in seconds, for any cached item in the dogpile.cache region. This applies to any cached method that doesn’t have an explicit cache expiration time defined for it.
-
backend
| Type: | string |
| Default: | dogpile.cache.null |
| Valid Values: | oslo_cache.memcache_pool, oslo_cache.dict, oslo_cache.mongo, oslo_cache.etcd3gw, dogpile.cache.memcached, dogpile.cache.pylibmc, dogpile.cache.bmemcached, dogpile.cache.dbm, dogpile.cache.redis, dogpile.cache.memory, dogpile.cache.memory_pickle, dogpile.cache.null |
Cache backend module. For eventlet-based or environments with hundreds of threaded servers, Memcache with pooling (oslo_cache.memcache_pool) is recommended. For environments with less than 100 threaded servers, Memcached (dogpile.cache.memcached) or Redis (dogpile.cache.redis) is recommended. Test environments with a single instance of the server can use the dogpile.cache.memory backend.
-
backend_argument
| Type: | multi-valued |
| Default: | u'' |
Arguments supplied to the backend module. Specify this option once per argument to be passed to the dogpile.cache backend. Example format: “<argname>:<value>”.
-
proxies
-
Proxy classes to import that will affect the way the dogpile.cache backend functions. See the dogpile.cache documentation on changing-backend-behavior.
-
enabled
| Type: | boolean |
| Default: | false |
Global toggle for caching.
-
debug_cache_backend
| Type: | boolean |
| Default: | false |
Extra debugging from the cache backend (cache keys, get/set/delete/etc calls). This is only really useful if you need to see the specific cache-backend get/set/delete calls with the keys/values. Typically this should be left set to false.
-
memcache_servers
| Type: | list |
| Default: | localhost:11211 |
Memcache servers in the format of “host:port”. (dogpile.cache.memcache and oslo_cache.memcache_pool backends only).
-
memcache_dead_retry
-
Number of seconds memcached server is considered dead before it is tried again. (dogpile.cache.memcache and oslo_cache.memcache_pool backends only).
-
memcache_socket_timeout
-
Timeout in seconds for every call to a server. (dogpile.cache.memcache and oslo_cache.memcache_pool backends only).
-
memcache_pool_maxsize
-
Max total number of open connections to every memcached server. (oslo_cache.memcache_pool backend only).
-
memcache_pool_unused_timeout
-
Number of seconds a connection to memcached is held unused in the pool before it is closed. (oslo_cache.memcache_pool backend only).
-
memcache_pool_connection_get_timeout
-
Number of seconds that an operation will wait to get a memcache client connection.
cors
-
allowed_origin
-
Indicate whether this resource may be shared with the domain received in the requests “origin” header. Format: “<protocol>://<host>[:<port>]”, no trailing slash. Example: https://horizon.example.com
-
allow_credentials
| Type: | boolean |
| Default: | true |
Indicate that the actual request can include user credentials
-
Indicate which headers are safe to expose to the API. Defaults to HTTP Simple Headers.
-
max_age
| Type: | integer |
| Default: | 3600 |
Maximum cache age of CORS preflight requests.
-
allow_methods
| Type: | list |
| Default: | OPTIONS,GET,HEAD,POST,PUT,DELETE,TRACE,PATCH |
Indicate which methods can be used during the actual request.
-
Indicate which header field names may be used during the actual request.
drivers
-
transport
-
Transport driver to use.
-
message_store
| Type: | string |
| Default: | mongodb |
Storage driver to use as the messaging store.
Deprecated Variations
| Group |
Name |
| drivers |
storage |
-
management_store
| Type: | string |
| Default: | mongodb |
Storage driver to use as the management store.
drivers:management_store:mongodb
-
ssl_keyfile
| Type: | string |
| Default: | <None> |
The private keyfile used to identify the local connection against mongod. If included with the certifle then only the ssl_certfile is needed.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
ssl_keyfile |
-
ssl_certfile
| Type: | string |
| Default: | <None> |
The certificate file used to identify the local connection against mongod.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
ssl_certfile |
-
ssl_cert_reqs
| Type: | string |
| Default: | CERT_REQUIRED |
Specifies whether a certificate is required from the other side of the connection, and whether it will be validated if provided. It must be one of the three values CERT_NONE``(certificates ignored), ``CERT_OPTIONAL``(not required, but validated if provided), or ``CERT_REQUIRED``(required and validated). If the value of this parameter is not ``CERT_NONE, then the ssl_ca_cert parameter must point to a file of CA certificates.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
ssl_cert_reqs |
-
ssl_ca_certs
| Type: | string |
| Default: | <None> |
The ca_certs file contains a set of concatenated “certification authority” certificates, which are used to validate certificates passed from the other end of the connection.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
ssl_ca_certs |
-
uri
| Type: | string |
| Default: | <None> |
Mongodb Connection URI. If ssl connection enabled, then ssl_keyfile, ssl_certfile, ssl_cert_reqs, ssl_ca_certs need to be set accordingly.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
uri |
-
database
| Type: | string |
| Default: | zaqar |
Database name.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
database |
-
max_attempts
| Type: | integer |
| Default: | 1000 |
| Minimum Value: | 0 |
Maximum number of times to retry a failed operation. Currently only used for retrying a message post.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
max_attempts |
-
max_retry_sleep
| Type: | floating point |
| Default: | 0.1 |
Maximum sleep interval between retries (actual sleep time increases linearly according to number of attempts performed).
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
max_retry_sleep |
-
max_retry_jitter
| Type: | floating point |
| Default: | 0.005 |
Maximum jitter interval, to be added to the sleep interval, in order to decrease probability that parallel requests will retry at the same instant.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
max_retry_jitter |
-
max_reconnect_attempts
-
Maximum number of times to retry an operation that failed due to a primary node failover.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
max_reconnect_attempts |
-
reconnect_sleep
| Type: | floating point |
| Default: | 0.02 |
Base sleep interval between attempts to reconnect after a primary node failover. The actual sleep time increases exponentially (power of 2) each time the operation is retried.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
reconnect_sleep |
drivers:management_store:redis
-
uri
| Type: | string |
| Default: | redis://127.0.0.1:6379 |
Redis connection URI, taking one of three forms. For a direct connection to a Redis server, use the form “redis://[:password]@host[:port][?options]”, where password is redis-server’s password, whenredis-server is set password, the password optionneeds to be set. port defaults to 6379 if notspecified. For an HA master-slave Redis cluster using Redis Sentinel, use the form “redis://[:password]@host1[:port1][,host2[:port2],…,hostN[:portN]][?options]”, where each host specified corresponds to an instance of redis-sentinel. In this form, the name of the Redis master used in the Sentinel configuration must be included in the query string as “master=<name>”. Finally, to connect to a local instance of Redis over a unix socket, you may use the form “redis:[:password]@/path/to/redis.sock[?options]”. In all forms, the “socket_timeout” option may bespecified in the query string. Its value is given in seconds. If not provided, “socket_timeout” defaults to 0.1 seconds.There are multiple database instances in redis database, for example in the /etc/redis/redis.conf, if the parameter is “database 16”, there are 16 database instances. By default, the data is stored in db = 0 database, if you want to use db = 1 database, you can use the following form: “redis://host[:port][?dbid=1]”.
Deprecated Variations
| Group |
Name |
| drivers:storage:redis |
uri |
-
max_reconnect_attempts
-
Maximum number of times to retry an operation that failed due to a redis node failover.
Deprecated Variations
| Group |
Name |
| drivers:storage:redis |
max_reconnect_attempts |
-
reconnect_sleep
| Type: | floating point |
| Default: | 1.0 |
Base sleep interval between attempts to reconnect after a redis node failover.
Deprecated Variations
| Group |
Name |
| drivers:storage:redis |
reconnect_sleep |
drivers:management_store:sqlalchemy
-
uri
| Type: | string |
| Default: | sqlite:///:memory: |
An sqlalchemy URL
Deprecated Variations
| Group |
Name |
| drivers:storage:sqlalchemy |
uri |
drivers:message_store:mongodb
-
ssl_keyfile
| Type: | string |
| Default: | <None> |
The private keyfile used to identify the local connection against mongod. If included with the certifle then only the ssl_certfile is needed.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
ssl_keyfile |
-
ssl_certfile
| Type: | string |
| Default: | <None> |
The certificate file used to identify the local connection against mongod.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
ssl_certfile |
-
ssl_cert_reqs
| Type: | string |
| Default: | CERT_REQUIRED |
Specifies whether a certificate is required from the other side of the connection, and whether it will be validated if provided. It must be one of the three values CERT_NONE``(certificates ignored), ``CERT_OPTIONAL``(not required, but validated if provided), or ``CERT_REQUIRED``(required and validated). If the value of this parameter is not ``CERT_NONE, then the ssl_ca_cert parameter must point to a file of CA certificates.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
ssl_cert_reqs |
-
ssl_ca_certs
| Type: | string |
| Default: | <None> |
The ca_certs file contains a set of concatenated “certification authority” certificates, which are used to validate certificates passed from the other end of the connection.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
ssl_ca_certs |
-
uri
| Type: | string |
| Default: | <None> |
Mongodb Connection URI. If ssl connection enabled, then ssl_keyfile, ssl_certfile, ssl_cert_reqs, ssl_ca_certs need to be set accordingly.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
uri |
-
database
| Type: | string |
| Default: | zaqar |
Database name.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
database |
-
max_attempts
| Type: | integer |
| Default: | 1000 |
| Minimum Value: | 0 |
Maximum number of times to retry a failed operation. Currently only used for retrying a message post.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
max_attempts |
-
max_retry_sleep
| Type: | floating point |
| Default: | 0.1 |
Maximum sleep interval between retries (actual sleep time increases linearly according to number of attempts performed).
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
max_retry_sleep |
-
max_retry_jitter
| Type: | floating point |
| Default: | 0.005 |
Maximum jitter interval, to be added to the sleep interval, in order to decrease probability that parallel requests will retry at the same instant.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
max_retry_jitter |
-
max_reconnect_attempts
-
Maximum number of times to retry an operation that failed due to a primary node failover.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
max_reconnect_attempts |
-
reconnect_sleep
| Type: | floating point |
| Default: | 0.02 |
Base sleep interval between attempts to reconnect after a primary node failover. The actual sleep time increases exponentially (power of 2) each time the operation is retried.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
reconnect_sleep |
-
partitions
-
Number of databases across which to partition message data, in order to reduce writer lock %. DO NOT change this setting after initial deployment. It MUST remain static. Also, you should not need a large number of partitions to improve performance, esp. if deploying MongoDB on SSD storage.
Deprecated Variations
| Group |
Name |
| drivers:storage:mongodb |
partitions |
drivers:message_store:redis
-
uri
| Type: | string |
| Default: | redis://127.0.0.1:6379 |
Redis connection URI, taking one of three forms. For a direct connection to a Redis server, use the form “redis://[:password]@host[:port][?options]”, where password is redis-server’s password, whenredis-server is set password, the password optionneeds to be set. port defaults to 6379 if notspecified. For an HA master-slave Redis cluster using Redis Sentinel, use the form “redis://[:password]@host1[:port1][,host2[:port2],…,hostN[:portN]][?options]”, where each host specified corresponds to an instance of redis-sentinel. In this form, the name of the Redis master used in the Sentinel configuration must be included in the query string as “master=<name>”. Finally, to connect to a local instance of Redis over a unix socket, you may use the form “redis:[:password]@/path/to/redis.sock[?options]”. In all forms, the “socket_timeout” option may bespecified in the query string. Its value is given in seconds. If not provided, “socket_timeout” defaults to 0.1 seconds.There are multiple database instances in redis database, for example in the /etc/redis/redis.conf, if the parameter is “database 16”, there are 16 database instances. By default, the data is stored in db = 0 database, if you want to use db = 1 database, you can use the following form: “redis://host[:port][?dbid=1]”.
Deprecated Variations
| Group |
Name |
| drivers:storage:redis |
uri |
-
max_reconnect_attempts
-
Maximum number of times to retry an operation that failed due to a redis node failover.
Deprecated Variations
| Group |
Name |
| drivers:storage:redis |
max_reconnect_attempts |
-
reconnect_sleep
| Type: | floating point |
| Default: | 1.0 |
Base sleep interval between attempts to reconnect after a redis node failover.
Deprecated Variations
| Group |
Name |
| drivers:storage:redis |
reconnect_sleep |
drivers:message_store:swift
-
auth_url
| Type: | string |
| Default: | http://127.0.0.1:5000/v3/ |
URI of Keystone endpoint to discover Swift
-
uri
| Type: | string |
| Default: | swift://demo:nomoresecrete@/demo |
Custom URI describing the swift connection.
-
insecure
| Type: | string |
| Default: | False |
Don’t check SSL certificate
-
project_domain_id
| Type: | string |
| Default: | default |
Domain ID containing project
-
project_domain_name
| Type: | string |
| Default: | <None> |
Domain name containing project
-
user_domain_id
| Type: | string |
| Default: | default |
User’s domain id
-
user_domain_name
| Type: | string |
| Default: | <None> |
User’s domain name
drivers:transport:websocket
-
bind
| Type: | host address |
| Default: | 127.0.0.1 |
Address on which the self-hosting server will listen.
-
port
| Type: | port number |
| Default: | 9000 |
| Minimum Value: | 0 |
| Maximum Value: | 65535 |
Port on which the self-hosting server will listen.
-
external_port
| Type: | port number |
| Default: | <None> |
| Minimum Value: | 0 |
| Maximum Value: | 65535 |
Port on which the service is provided to the user.
-
notification_bind
| Type: | host address |
| Default: | <None> |
Address on which the notification server will listen.
-
notification_port
| Type: | port number |
| Default: | 0 |
| Minimum Value: | 0 |
| Maximum Value: | 65535 |
Port on which the notification server will listen.
drivers:transport:wsgi
-
bind
| Type: | host address |
| Default: | 127.0.0.1 |
Address on which the self-hosting server will listen.
-
port
| Type: | port number |
| Default: | 8888 |
| Minimum Value: | 0 |
| Maximum Value: | 65535 |
Port on which the self-hosting server will listen.
keystone_authtoken
-
www_authenticate_uri
| Type: | string |
| Default: | <None> |
Complete “public” Identity API endpoint. This endpoint should not be an “admin” endpoint, as it should be accessible by all end users. Unauthenticated clients are redirected to this endpoint to authenticate. Although this endpoint should ideally be unversioned, client support in the wild varies. If you’re using a versioned v2 endpoint here, then this should not be the same endpoint the service user utilizes for validating tokens, because normal end users may not be able to reach that endpoint.
Deprecated Variations
| Group |
Name |
| keystone_authtoken |
auth_uri |
-
auth_uri
| Type: | string |
| Default: | <None> |
Complete “public” Identity API endpoint. This endpoint should not be an “admin” endpoint, as it should be accessible by all end users. Unauthenticated clients are redirected to this endpoint to authenticate. Although this endpoint should ideally be unversioned, client support in the wild varies. If you’re using a versioned v2 endpoint here, then this should not be the same endpoint the service user utilizes for validating tokens, because normal end users may not be able to reach that endpoint. This option is deprecated in favor of www_authenticate_uri and will be removed in the S release.
Warning
This option is deprecated for removal since Queens.
Its value may be silently ignored
in the future.
| Reason: | The auth_uri option is deprecated in favor of www_authenticate_uri and will be removed in the S release. |
-
auth_version
| Type: | string |
| Default: | <None> |
API version of the admin Identity API endpoint.
-
delay_auth_decision
| Type: | boolean |
| Default: | false |
Do not handle authorization requests within the middleware, but delegate the authorization decision to downstream WSGI components.
-
http_connect_timeout
| Type: | integer |
| Default: | <None> |
Request timeout value for communicating with Identity API server.
-
http_request_max_retries
-
How many times are we trying to reconnect when communicating with Identity API Server.
-
cache
| Type: | string |
| Default: | <None> |
Request environment key where the Swift cache object is stored. When auth_token middleware is deployed with a Swift cache, use this option to have the middleware share a caching backend with swift. Otherwise, use the memcached_servers option instead.
-
certfile
| Type: | string |
| Default: | <None> |
Required if identity server requires client certificate
-
keyfile
| Type: | string |
| Default: | <None> |
Required if identity server requires client certificate
-
cafile
| Type: | string |
| Default: | <None> |
A PEM encoded Certificate Authority to use when verifying HTTPs connections. Defaults to system CAs.
-
insecure
| Type: | boolean |
| Default: | false |
Verify HTTPS connections.
-
region_name
| Type: | string |
| Default: | <None> |
The region in which the identity server can be found.
-
signing_dir
| Type: | string |
| Default: | <None> |
Directory used to cache files related to PKI tokens. This option has been deprecated in the Ocata release and will be removed in the P release.
Warning
This option is deprecated for removal since Ocata.
Its value may be silently ignored
in the future.
| Reason: | PKI token format is no longer supported. |
-
memcached_servers
-
Optionally specify a list of memcached server(s) to use for caching. If left undefined, tokens will instead be cached in-process.
Deprecated Variations
| Group |
Name |
| keystone_authtoken |
memcache_servers |
-
token_cache_time
-
In order to prevent excessive effort spent validating tokens, the middleware caches previously-seen tokens for a configurable duration (in seconds). Set to -1 to disable caching completely.
-
revocation_cache_time
-
Determines the frequency at which the list of revoked tokens is retrieved from the Identity service (in seconds). A high number of revocation events combined with a low cache duration may significantly reduce performance. Only valid for PKI tokens. This option has been deprecated in the Ocata release and will be removed in the P release.
Warning
This option is deprecated for removal since Ocata.
Its value may be silently ignored
in the future.
| Reason: | PKI token format is no longer supported. |
-
memcache_security_strategy
| Type: | string |
| Default: | None |
| Valid Values: | None, MAC, ENCRYPT |
(Optional) If defined, indicate whether token data should be authenticated or authenticated and encrypted. If MAC, token data is authenticated (with HMAC) in the cache. If ENCRYPT, token data is encrypted and authenticated in the cache. If the value is not one of these options or empty, auth_token will raise an exception on initialization.
-
memcache_secret_key
| Type: | string |
| Default: | <None> |
(Optional, mandatory if memcache_security_strategy is defined) This string is used for key derivation.
-
memcache_pool_dead_retry
-
(Optional) Number of seconds memcached server is considered dead before it is tried again.
-
memcache_pool_maxsize
-
(Optional) Maximum total number of open connections to every memcached server.
-
memcache_pool_socket_timeout
-
(Optional) Socket timeout in seconds for communicating with a memcached server.
-
memcache_pool_unused_timeout
-
(Optional) Number of seconds a connection to memcached is held unused in the pool before it is closed.
-
memcache_pool_conn_get_timeout
-
(Optional) Number of seconds that an operation will wait to get a memcached client connection from the pool.
-
memcache_use_advanced_pool
| Type: | boolean |
| Default: | false |
(Optional) Use the advanced (eventlet safe) memcached client pool. The advanced pool will only work under python 2.x.
-
include_service_catalog
| Type: | boolean |
| Default: | true |
(Optional) Indicate whether to set the X-Service-Catalog header. If False, middleware will not ask for service catalog on token validation and will not set the X-Service-Catalog header.
-
enforce_token_bind
| Type: | string |
| Default: | permissive |
Used to control the use and type of token binding. Can be set to: “disabled” to not check token binding. “permissive” (default) to validate binding information if the bind type is of a form known to the server and ignore it if not. “strict” like “permissive” but if the bind type is unknown the token will be rejected. “required” any form of token binding is needed to be allowed. Finally the name of a binding method that must be present in tokens.
-
check_revocations_for_cached
| Type: | boolean |
| Default: | false |
If true, the revocation list will be checked for cached tokens. This requires that PKI tokens are configured on the identity server.
Warning
This option is deprecated for removal since Ocata.
Its value may be silently ignored
in the future.
| Reason: | PKI token format is no longer supported. |
-
hash_algorithms
-
Hash algorithms to use for hashing PKI tokens. This may be a single algorithm or multiple. The algorithms are those supported by Python standard hashlib.new(). The hashes will be tried in the order given, so put the preferred one first for performance. The result of the first hash will be stored in the cache. This will typically be set to multiple values only while migrating from a less secure algorithm to a more secure one. Once all the old tokens are expired this option should be set to a single value for better performance.
Warning
This option is deprecated for removal since Ocata.
Its value may be silently ignored
in the future.
| Reason: | PKI token format is no longer supported. |
-
service_token_roles
| Type: | list |
| Default: | service |
A choice of roles that must be present in a service token. Service tokens are allowed to request that an expired token can be used and so this check should tightly control that only actual services should be sending this token. Roles here are applied as an ANY check so any role in this list must be present. For backwards compatibility reasons this currently only affects the allow_expired check.
-
service_token_roles_required
| Type: | boolean |
| Default: | false |
For backwards compatibility reasons we must let valid service tokens pass that don’t pass the service_token_roles check as valid. Setting this true will become the default in a future release and should be enabled if possible.
-
auth_type
| Type: | unknown type |
| Default: | <None> |
Authentication type to load
Deprecated Variations
| Group |
Name |
| keystone_authtoken |
auth_plugin |
-
auth_section
| Type: | unknown type |
| Default: | <None> |
Config Section from which to load plugin specific options
matchmaker_redis
-
host
| Type: | string |
| Default: | 127.0.0.1 |
Host to locate redis.
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Replaced by [DEFAULT]/transport_url |
-
port
| Type: | port number |
| Default: | 6379 |
| Minimum Value: | 0 |
| Maximum Value: | 65535 |
Use this port to connect to redis host.
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Replaced by [DEFAULT]/transport_url |
-
password
-
Password for Redis server (optional).
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Replaced by [DEFAULT]/transport_url |
-
sentinel_hosts
-
List of Redis Sentinel hosts (fault tolerance mode), e.g., [host:port, host1:port … ]
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Replaced by [DEFAULT]/transport_url |
-
sentinel_group_name
| Type: | string |
| Default: | oslo-messaging-zeromq |
Redis replica set name.
-
wait_timeout
| Type: | integer |
| Default: | 2000 |
Time in ms to wait between connection attempts.
-
check_timeout
| Type: | integer |
| Default: | 20000 |
Time in ms to wait before the transaction is killed.
-
socket_timeout
| Type: | integer |
| Default: | 10000 |
Timeout in ms on blocking socket operations.
notification
-
smtp_command
| Type: | string |
| Default: | /usr/sbin/sendmail -t -oi |
The command of smtp to send email. The format is “command_name arg1 arg2”.
-
max_notifier_workers
-
The max amount of the notification workers.
-
require_confirmation
| Type: | boolean |
| Default: | false |
Whether the http/https/email subscription need to be confirmed before notification.
-
external_confirmation_url
| Type: | string |
| Default: | <None> |
The confirmation page url that will be used in email subscription confirmation before notification.
-
subscription_confirmation_email_template
| Type: | dict |
| Default: | body:You have chosen to subscribe to the queue: {0}. This queue belongs to project: {1}. To confirm this subscription, click or visit this link below: {2},sender:Zaqar Notifications <no-reply@openstack.org>,topic:Zaqar Notification - Subscription Confirmation |
Defines the set of subscription confirmation email content, including topic, body and sender. There is a mapping is {0} -> queue name, {1} ->project id, {2}-> confirm url in body string. User can use any of the three value. But they can’t use more than three.
-
unsubscribe_confirmation_email_template
| Type: | dict |
| Default: | body:You have unsubscribed successfully to the queue: {0}. This queue belongs to project: {1}. To resubscribe this subscription, click or visit this link below: {2},sender:Zaqar Notifications <no-reply@openstack.org>,topic:Zaqar Notification - Unsubscribe Confirmation |
Defines the set of unsubscribe confirmation email content, including topic, body and sender. There is a mapping is {0} -> queue name, {1} ->project id, {2}-> confirm url in body string. User can use any of the three value. But they can’t use more than three.
oslo_messaging_amqp
-
container_name
| Type: | string |
| Default: | <None> |
Name for the AMQP container. must be globally unique. Defaults to a generated UUID
Deprecated Variations
| Group |
Name |
| amqp1 |
container_name |
-
idle_timeout
-
Timeout for inactive connections (in seconds)
Deprecated Variations
| Group |
Name |
| amqp1 |
idle_timeout |
-
trace
| Type: | boolean |
| Default: | false |
Debug: dump AMQP frames to stdout
Deprecated Variations
| Group |
Name |
| amqp1 |
trace |
-
ssl
| Type: | boolean |
| Default: | false |
Attempt to connect via SSL. If no other ssl-related parameters are given, it will use the system’s CA-bundle to verify the server’s certificate.
-
ssl_ca_file
-
CA certificate PEM file used to verify the server’s certificate
Deprecated Variations
| Group |
Name |
| amqp1 |
ssl_ca_file |
-
ssl_cert_file
-
Self-identifying certificate PEM file for client authentication
Deprecated Variations
| Group |
Name |
| amqp1 |
ssl_cert_file |
-
ssl_key_file
-
Private key PEM file used to sign ssl_cert_file certificate (optional)
Deprecated Variations
| Group |
Name |
| amqp1 |
ssl_key_file |
-
ssl_key_password
| Type: | string |
| Default: | <None> |
Password for decrypting ssl_key_file (if encrypted)
Deprecated Variations
| Group |
Name |
| amqp1 |
ssl_key_password |
-
ssl_verify_vhost
| Type: | boolean |
| Default: | false |
By default SSL checks that the name in the server’s certificate matches the hostname in the transport_url. In some configurations it may be preferable to use the virtual hostname instead, for example if the server uses the Server Name Indication TLS extension (rfc6066) to provide a certificate per virtual host. Set ssl_verify_vhost to True if the server’s SSL certificate uses the virtual host name instead of the DNS name.
-
allow_insecure_clients
| Type: | boolean |
| Default: | false |
Accept clients using either SSL or plain TCP
Deprecated Variations
| Group |
Name |
| amqp1 |
allow_insecure_clients |
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Not applicable - not a SSL server |
-
sasl_mechanisms
-
Space separated list of acceptable SASL mechanisms
Deprecated Variations
| Group |
Name |
| amqp1 |
sasl_mechanisms |
-
sasl_config_dir
-
Path to directory that contains the SASL configuration
Deprecated Variations
| Group |
Name |
| amqp1 |
sasl_config_dir |
-
sasl_config_name
-
Name of configuration file (without .conf suffix)
Deprecated Variations
| Group |
Name |
| amqp1 |
sasl_config_name |
-
sasl_default_realm
-
SASL realm to use if no realm present in username
-
username
-
User name for message broker authentication
Deprecated Variations
| Group |
Name |
| amqp1 |
username |
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Should use configuration option transport_url to provide the username. |
-
password
-
Password for message broker authentication
Deprecated Variations
| Group |
Name |
| amqp1 |
password |
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Should use configuration option transport_url to provide the password. |
-
connection_retry_interval
| Type: | integer |
| Default: | 1 |
| Minimum Value: | 1 |
Seconds to pause before attempting to re-connect.
-
connection_retry_backoff
| Type: | integer |
| Default: | 2 |
| Minimum Value: | 0 |
Increase the connection_retry_interval by this many seconds after each unsuccessful failover attempt.
-
connection_retry_interval_max
| Type: | integer |
| Default: | 30 |
| Minimum Value: | 1 |
Maximum limit for connection_retry_interval + connection_retry_backoff
-
link_retry_delay
| Type: | integer |
| Default: | 10 |
| Minimum Value: | 1 |
Time to pause between re-connecting an AMQP 1.0 link that failed due to a recoverable error.
-
default_reply_retry
| Type: | integer |
| Default: | 0 |
| Minimum Value: | -1 |
The maximum number of attempts to re-send a reply message which failed due to a recoverable error.
-
default_reply_timeout
| Type: | integer |
| Default: | 30 |
| Minimum Value: | 5 |
The deadline for an rpc reply message delivery.
-
default_send_timeout
| Type: | integer |
| Default: | 30 |
| Minimum Value: | 5 |
The deadline for an rpc cast or call message delivery. Only used when caller does not provide a timeout expiry.
-
default_notify_timeout
| Type: | integer |
| Default: | 30 |
| Minimum Value: | 5 |
The deadline for a sent notification message delivery. Only used when caller does not provide a timeout expiry.
-
default_sender_link_timeout
| Type: | integer |
| Default: | 600 |
| Minimum Value: | 1 |
The duration to schedule a purge of idle sender links. Detach link after expiry.
-
addressing_mode
| Type: | string |
| Default: | dynamic |
Indicates the addressing mode used by the driver.
Permitted values:
‘legacy’ - use legacy non-routable addressing
‘routable’ - use routable addresses
‘dynamic’ - use legacy addresses if the message bus does not support routing otherwise use routable addressing
-
pseudo_vhost
| Type: | boolean |
| Default: | true |
Enable virtual host support for those message buses that do not natively support virtual hosting (such as qpidd). When set to true the virtual host name will be added to all message bus addresses, effectively creating a private ‘subnet’ per virtual host. Set to False if the message bus supports virtual hosting using the ‘hostname’ field in the AMQP 1.0 Open performative as the name of the virtual host.
-
server_request_prefix
| Type: | string |
| Default: | exclusive |
address prefix used when sending to a specific server
Deprecated Variations
| Group |
Name |
| amqp1 |
server_request_prefix |
-
broadcast_prefix
| Type: | string |
| Default: | broadcast |
address prefix used when broadcasting to all servers
Deprecated Variations
| Group |
Name |
| amqp1 |
broadcast_prefix |
-
group_request_prefix
| Type: | string |
| Default: | unicast |
address prefix when sending to any server in group
Deprecated Variations
| Group |
Name |
| amqp1 |
group_request_prefix |
-
rpc_address_prefix
| Type: | string |
| Default: | openstack.org/om/rpc |
Address prefix for all generated RPC addresses
-
notify_address_prefix
| Type: | string |
| Default: | openstack.org/om/notify |
Address prefix for all generated Notification addresses
-
multicast_address
| Type: | string |
| Default: | multicast |
Appended to the address prefix when sending a fanout message. Used by the message bus to identify fanout messages.
-
unicast_address
| Type: | string |
| Default: | unicast |
Appended to the address prefix when sending to a particular RPC/Notification server. Used by the message bus to identify messages sent to a single destination.
-
anycast_address
| Type: | string |
| Default: | anycast |
Appended to the address prefix when sending to a group of consumers. Used by the message bus to identify messages that should be delivered in a round-robin fashion across consumers.
-
default_notification_exchange
| Type: | string |
| Default: | <None> |
Exchange name used in notification addresses.
Exchange name resolution precedence:
Target.exchange if set
else default_notification_exchange if set
else control_exchange if set
else ‘notify’
-
default_rpc_exchange
| Type: | string |
| Default: | <None> |
Exchange name used in RPC addresses.
Exchange name resolution precedence:
Target.exchange if set
else default_rpc_exchange if set
else control_exchange if set
else ‘rpc’
-
reply_link_credit
| Type: | integer |
| Default: | 200 |
| Minimum Value: | 1 |
Window size for incoming RPC Reply messages.
-
rpc_server_credit
| Type: | integer |
| Default: | 100 |
| Minimum Value: | 1 |
Window size for incoming RPC Request messages
-
notify_server_credit
| Type: | integer |
| Default: | 100 |
| Minimum Value: | 1 |
Window size for incoming Notification messages
-
pre_settled
| Type: | multi-valued |
| Default: | rpc-cast |
| Default: | rpc-reply |
Send messages of this type pre-settled.
Pre-settled messages will not receive acknowledgement
from the peer. Note well: pre-settled messages may be
silently discarded if the delivery fails.
Permitted values:
‘rpc-call’ - send RPC Calls pre-settled
‘rpc-reply’- send RPC Replies pre-settled
‘rpc-cast’ - Send RPC Casts pre-settled
‘notify’ - Send Notifications pre-settled
oslo_messaging_kafka
-
kafka_default_host
| Type: | string |
| Default: | localhost |
Default Kafka broker Host
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Replaced by [DEFAULT]/transport_url |
-
kafka_default_port
| Type: | port number |
| Default: | 9092 |
| Minimum Value: | 0 |
| Maximum Value: | 65535 |
Default Kafka broker Port
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Replaced by [DEFAULT]/transport_url |
-
kafka_max_fetch_bytes
| Type: | integer |
| Default: | 1048576 |
Max fetch bytes of Kafka consumer
-
kafka_consumer_timeout
| Type: | floating point |
| Default: | 1.0 |
Default timeout(s) for Kafka consumers
-
pool_size
-
Pool Size for Kafka Consumers
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Driver no longer uses connection pool. |
-
conn_pool_min_size
-
The pool size limit for connections expiration policy
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Driver no longer uses connection pool. |
-
conn_pool_ttl
| Type: | integer |
| Default: | 1200 |
The time-to-live in sec of idle connections in the pool
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Driver no longer uses connection pool. |
-
consumer_group
| Type: | string |
| Default: | oslo_messaging_consumer |
Group id for Kafka consumer. Consumers in one group will coordinate message consumption
-
producer_batch_timeout
| Type: | floating point |
| Default: | 0.0 |
Upper bound on the delay for KafkaProducer batching in seconds
-
producer_batch_size
| Type: | integer |
| Default: | 16384 |
Size of batch for the producer async send
oslo_messaging_notifications
-
driver
| Type: | multi-valued |
| Default: | u'' |
The Drivers(s) to handle sending notifications. Possible values are messaging, messagingv2, routing, log, test, noop
Deprecated Variations
| Group |
Name |
| DEFAULT |
notification_driver |
-
transport_url
| Type: | string |
| Default: | <None> |
A URL representing the messaging driver to use for notifications. If not set, we fall back to the same configuration used for RPC.
Deprecated Variations
| Group |
Name |
| DEFAULT |
notification_transport_url |
-
topics
| Type: | list |
| Default: | notifications |
AMQP topic used for OpenStack notifications.
Deprecated Variations
| Group |
Name |
| rpc_notifier2 |
topics |
| DEFAULT |
notification_topics |
-
retry
-
The maximum number of attempts to re-send a notification message which failed to be delivered due to a recoverable error. 0 - No retry, -1 - indefinite
oslo_messaging_rabbit
-
amqp_durable_queues
| Type: | boolean |
| Default: | false |
Use durable queues in AMQP.
Deprecated Variations
| Group |
Name |
| DEFAULT |
amqp_durable_queues |
| DEFAULT |
rabbit_durable_queues |
-
amqp_auto_delete
| Type: | boolean |
| Default: | false |
Auto-delete queues in AMQP.
Deprecated Variations
| Group |
Name |
| DEFAULT |
amqp_auto_delete |
-
ssl
| Type: | boolean |
| Default: | <None> |
Enable SSL
-
ssl_version
-
SSL version to use (valid only if SSL enabled). Valid values are TLSv1 and SSLv23. SSLv2, SSLv3, TLSv1_1, and TLSv1_2 may be available on some distributions.
Deprecated Variations
| Group |
Name |
| oslo_messaging_rabbit |
kombu_ssl_version |
-
ssl_key_file
-
SSL key file (valid only if SSL enabled).
Deprecated Variations
| Group |
Name |
| oslo_messaging_rabbit |
kombu_ssl_keyfile |
-
ssl_cert_file
-
SSL cert file (valid only if SSL enabled).
Deprecated Variations
| Group |
Name |
| oslo_messaging_rabbit |
kombu_ssl_certfile |
-
ssl_ca_file
-
SSL certification authority file (valid only if SSL enabled).
Deprecated Variations
| Group |
Name |
| oslo_messaging_rabbit |
kombu_ssl_ca_certs |
-
kombu_reconnect_delay
| Type: | floating point |
| Default: | 1.0 |
How long to wait before reconnecting in response to an AMQP consumer cancel notification.
Deprecated Variations
| Group |
Name |
| DEFAULT |
kombu_reconnect_delay |
-
kombu_compression
| Type: | string |
| Default: | <None> |
EXPERIMENTAL: Possible values are: gzip, bz2. If not set compression will not be used. This option may not be available in future versions.
-
kombu_missing_consumer_retry_timeout
-
How long to wait a missing client before abandoning to send it its replies. This value should not be longer than rpc_response_timeout.
Deprecated Variations
| Group |
Name |
| oslo_messaging_rabbit |
kombu_reconnect_timeout |
-
kombu_failover_strategy
| Type: | string |
| Default: | round-robin |
| Valid Values: | round-robin, shuffle |
Determines how the next RabbitMQ node is chosen in case the one we are currently connected to becomes unavailable. Takes effect only if more than one RabbitMQ node is provided in config.
-
rabbit_host
| Type: | string |
| Default: | localhost |
The RabbitMQ broker address where a single node is used.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rabbit_host |
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Replaced by [DEFAULT]/transport_url |
-
rabbit_port
| Type: | port number |
| Default: | 5672 |
| Minimum Value: | 0 |
| Maximum Value: | 65535 |
The RabbitMQ broker port where a single node is used.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rabbit_port |
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Replaced by [DEFAULT]/transport_url |
-
rabbit_hosts
| Type: | list |
| Default: | $rabbit_host:$rabbit_port |
RabbitMQ HA cluster host:port pairs.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rabbit_hosts |
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Replaced by [DEFAULT]/transport_url |
-
rabbit_userid
| Type: | string |
| Default: | guest |
The RabbitMQ userid.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rabbit_userid |
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Replaced by [DEFAULT]/transport_url |
-
rabbit_password
| Type: | string |
| Default: | guest |
The RabbitMQ password.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rabbit_password |
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Replaced by [DEFAULT]/transport_url |
-
rabbit_login_method
| Type: | string |
| Default: | AMQPLAIN |
| Valid Values: | PLAIN, AMQPLAIN, RABBIT-CR-DEMO |
The RabbitMQ login method.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rabbit_login_method |
-
rabbit_virtual_host
-
The RabbitMQ virtual host.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rabbit_virtual_host |
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
| Reason: | Replaced by [DEFAULT]/transport_url |
-
rabbit_retry_interval
-
How frequently to retry connecting with RabbitMQ.
-
rabbit_retry_backoff
-
How long to backoff for between retries when connecting to RabbitMQ.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rabbit_retry_backoff |
-
rabbit_interval_max
-
Maximum interval of RabbitMQ connection retries. Default is 30 seconds.
-
rabbit_max_retries
-
Maximum number of RabbitMQ connection retries. Default is 0 (infinite retry count).
Deprecated Variations
| Group |
Name |
| DEFAULT |
rabbit_max_retries |
Warning
This option is deprecated for removal.
Its value may be silently ignored
in the future.
-
rabbit_ha_queues
| Type: | boolean |
| Default: | false |
Try to use HA queues in RabbitMQ (x-ha-policy: all). If you change this option, you must wipe the RabbitMQ database. In RabbitMQ 3.0, queue mirroring is no longer controlled by the x-ha-policy argument when declaring a queue. If you just want to make sure that all queues (except those with auto-generated names) are mirrored across all nodes, run: “rabbitmqctl set_policy HA ‘^(?!amq.).*’ ‘{“ha-mode”: “all”}’ “
Deprecated Variations
| Group |
Name |
| DEFAULT |
rabbit_ha_queues |
-
rabbit_transient_queues_ttl
| Type: | integer |
| Default: | 1800 |
| Minimum Value: | 1 |
Positive integer representing duration in seconds for queue TTL (x-expires). Queues which are unused for the duration of the TTL are automatically deleted. The parameter affects only reply and fanout queues.
-
rabbit_qos_prefetch_count
-
Specifies the number of messages to prefetch. Setting to zero allows unlimited messages.
-
heartbeat_timeout_threshold
-
Number of seconds after which the Rabbit broker is considered down if heartbeat’s keep-alive fails (0 disable the heartbeat). EXPERIMENTAL
-
heartbeat_rate
-
How often times during the heartbeat_timeout_threshold we check the heartbeat.
-
fake_rabbit
| Type: | boolean |
| Default: | false |
Deprecated, use rpc_backend=kombu+memory or rpc_backend=fake
Deprecated Variations
| Group |
Name |
| DEFAULT |
fake_rabbit |
-
channel_max
| Type: | integer |
| Default: | <None> |
Maximum number of channels to allow
-
frame_max
| Type: | integer |
| Default: | <None> |
The maximum byte size for an AMQP frame
-
heartbeat_interval
-
How often to send heartbeats for consumer’s connections
-
ssl_options
-
Arguments passed to ssl.wrap_socket
-
socket_timeout
| Type: | floating point |
| Default: | 0.25 |
Set socket timeout in seconds for connection’s socket
-
tcp_user_timeout
| Type: | floating point |
| Default: | 0.25 |
Set TCP_USER_TIMEOUT in seconds for connection’s socket
-
host_connection_reconnect_delay
| Type: | floating point |
| Default: | 0.25 |
Set delay for reconnection to some host which has connection error
-
connection_factory
| Type: | string |
| Default: | single |
| Valid Values: | new, single, read_write |
Connection factory implementation
-
pool_max_size
-
Maximum number of connections to keep queued.
-
pool_max_overflow
-
Maximum number of connections to create above pool_max_size.
-
pool_timeout
-
Default number of seconds to wait for a connections to available
-
pool_recycle
-
Lifetime of a connection (since creation) in seconds or None for no recycling. Expired connections are closed on acquire.
-
pool_stale
-
Threshold at which inactive (since release) connections are considered stale in seconds or None for no staleness. Stale connections are closed on acquire.
-
default_serializer_type
| Type: | string |
| Default: | json |
| Valid Values: | json, msgpack |
Default serialization mechanism for serializing/deserializing outgoing/incoming messages
-
notification_persistence
| Type: | boolean |
| Default: | false |
Persist notification messages.
-
default_notification_exchange
| Type: | string |
| Default: | ${control_exchange}_notification |
Exchange name for sending notifications
-
notification_listener_prefetch_count
-
Max number of not acknowledged message which RabbitMQ can send to notification listener.
-
default_notification_retry_attempts
-
Reconnecting retry count in case of connectivity problem during sending notification, -1 means infinite retry.
-
notification_retry_delay
| Type: | floating point |
| Default: | 0.25 |
Reconnecting retry delay in case of connectivity problem during sending notification message
-
rpc_queue_expiration
-
Time to live for rpc queues without consumers in seconds.
-
default_rpc_exchange
| Type: | string |
| Default: | ${control_exchange}_rpc |
Exchange name for sending RPC messages
-
rpc_reply_exchange
| Type: | string |
| Default: | ${control_exchange}_rpc_reply |
Exchange name for receiving RPC replies
-
rpc_listener_prefetch_count
-
Max number of not acknowledged message which RabbitMQ can send to rpc listener.
-
rpc_reply_listener_prefetch_count
-
Max number of not acknowledged message which RabbitMQ can send to rpc reply listener.
-
rpc_reply_retry_attempts
-
Reconnecting retry count in case of connectivity problem during sending reply. -1 means infinite retry during rpc_timeout
-
rpc_reply_retry_delay
| Type: | floating point |
| Default: | 0.25 |
Reconnecting retry delay in case of connectivity problem during sending reply.
-
default_rpc_retry_attempts
-
Reconnecting retry count in case of connectivity problem during sending RPC message, -1 means infinite retry. If actual retry attempts in not 0 the rpc request could be processed more than one time
-
rpc_retry_delay
| Type: | floating point |
| Default: | 0.25 |
Reconnecting retry delay in case of connectivity problem during sending RPC message
oslo_messaging_zmq
-
rpc_zmq_bind_address
-
ZeroMQ bind address. Should be a wildcard (*), an ethernet interface, or IP. The “host” option should point or resolve to this address.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_bind_address |
-
rpc_zmq_matchmaker
| Type: | string |
| Default: | redis |
| Valid Values: | redis, sentinel, dummy |
MatchMaker driver.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_matchmaker |
-
rpc_zmq_contexts
-
Number of ZeroMQ contexts, defaults to 1.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_contexts |
-
rpc_zmq_topic_backlog
| Type: | integer |
| Default: | <None> |
Maximum number of ingress messages to locally buffer per topic. Default is unlimited.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_topic_backlog |
-
rpc_zmq_ipc_dir
| Type: | string |
| Default: | /var/run/openstack |
Directory for holding IPC sockets.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_ipc_dir |
-
rpc_zmq_host
| Type: | string |
| Default: | localhost |
Name of this node. Must be a valid hostname, FQDN, or IP address. Must match “host” option, if running Nova.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_host |
-
zmq_linger
-
Number of seconds to wait before all pending messages will be sent after closing a socket. The default value of -1 specifies an infinite linger period. The value of 0 specifies no linger period. Pending messages shall be discarded immediately when the socket is closed. Positive values specify an upper bound for the linger period.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_cast_timeout |
-
rpc_poll_timeout
-
The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_poll_timeout |
-
zmq_target_expire
-
Expiration timeout in seconds of a name service record about existing target ( < 0 means no timeout).
Deprecated Variations
| Group |
Name |
| DEFAULT |
zmq_target_expire |
-
zmq_target_update
-
Update period in seconds of a name service record about existing target.
Deprecated Variations
| Group |
Name |
| DEFAULT |
zmq_target_update |
-
use_pub_sub
| Type: | boolean |
| Default: | false |
Use PUB/SUB pattern for fanout methods. PUB/SUB always uses proxy.
Deprecated Variations
| Group |
Name |
| DEFAULT |
use_pub_sub |
-
use_router_proxy
| Type: | boolean |
| Default: | false |
Use ROUTER remote proxy.
Deprecated Variations
| Group |
Name |
| DEFAULT |
use_router_proxy |
-
use_dynamic_connections
| Type: | boolean |
| Default: | false |
This option makes direct connections dynamic or static. It makes sense only with use_router_proxy=False which means to use direct connections for direct message types (ignored otherwise).
-
zmq_failover_connections
-
How many additional connections to a host will be made for failover reasons. This option is actual only in dynamic connections mode.
-
rpc_zmq_min_port
| Type: | port number |
| Default: | 49153 |
| Minimum Value: | 0 |
| Maximum Value: | 65535 |
Minimal port number for random ports range.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_min_port |
-
rpc_zmq_max_port
| Type: | integer |
| Default: | 65536 |
| Minimum Value: | 1 |
| Maximum Value: | 65536 |
Maximal port number for random ports range.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_max_port |
-
rpc_zmq_bind_port_retries
-
Number of retries to find free port number before fail with ZMQBindError.
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_bind_port_retries |
-
rpc_zmq_serialization
| Type: | string |
| Default: | json |
| Valid Values: | json, msgpack |
Default serialization mechanism for serializing/deserializing outgoing/incoming messages
Deprecated Variations
| Group |
Name |
| DEFAULT |
rpc_zmq_serialization |
-
zmq_immediate
| Type: | boolean |
| Default: | true |
This option configures round-robin mode in zmq socket. True means not keeping a queue when server side disconnects. False means to keep queue and messages even if server is disconnected, when the server appears we send all accumulated messages to it.
-
zmq_tcp_keepalive
-
Enable/disable TCP keepalive (KA) mechanism. The default value of -1 (or any other negative value) means to skip any overrides and leave it to OS default; 0 and 1 (or any other positive value) mean to disable and enable the option respectively.
-
zmq_tcp_keepalive_idle
-
The duration between two keepalive transmissions in idle condition. The unit is platform dependent, for example, seconds in Linux, milliseconds in Windows etc. The default value of -1 (or any other negative value and 0) means to skip any overrides and leave it to OS default.
-
zmq_tcp_keepalive_cnt
-
The number of retransmissions to be carried out before declaring that remote end is not available. The default value of -1 (or any other negative value and 0) means to skip any overrides and leave it to OS default.
-
zmq_tcp_keepalive_intvl
-
The duration between two successive keepalive retransmissions, if acknowledgement to the previous keepalive transmission is not received. The unit is platform dependent, for example, seconds in Linux, milliseconds in Windows etc. The default value of -1 (or any other negative value and 0) means to skip any overrides and leave it to OS default.
-
rpc_thread_pool_size
-
Maximum number of (green) threads to work concurrently.
-
rpc_message_ttl
-
Expiration timeout in seconds of a sent/received message after which it is not tracked anymore by a client/server.
-
rpc_use_acks
| Type: | boolean |
| Default: | false |
Wait for message acknowledgements from receivers. This mechanism works only via proxy without PUB/SUB.
-
rpc_ack_timeout_base
-
Number of seconds to wait for an ack from a cast/call. After each retry attempt this timeout is multiplied by some specified multiplier.
-
rpc_ack_timeout_multiplier
-
Number to multiply base ack timeout by after each retry attempt.
-
rpc_retry_attempts
-
Default number of message sending attempts in case of any problems occurred: positive value N means at most N retries, 0 means no retries, None or -1 (or any other negative values) mean to retry forever. This option is used only if acknowledgments are enabled.
-
subscribe_on
-
List of publisher hosts SubConsumer can subscribe on. This option has higher priority then the default publishers list taken from the matchmaker.
oslo_policy
-
enforce_scope
| Type: | boolean |
| Default: | false |
This option controls whether or not to enforce scope when evaluating policies. If True, the scope of the token used in the request is compared to the scope_types of the policy being enforced. If the scopes do not match, an InvalidScope exception will be raised. If False, a message will be logged informing operators that policies are being invoked with mismatching scope.
-
policy_file
| Type: | string |
| Default: | policy.json |
The file that defines policies.
Deprecated Variations
| Group |
Name |
| DEFAULT |
policy_file |
-
policy_default_rule
| Type: | string |
| Default: | default |
Default rule. Enforced when a requested rule is not found.
Deprecated Variations
| Group |
Name |
| DEFAULT |
policy_default_rule |
-
policy_dirs
| Type: | multi-valued |
| Default: | policy.d |
Directories where policy configuration files are stored. They can be relative to any directory in the search path defined by the config_dir option, or absolute paths. The file defined by policy_file must exist for these directories to be searched. Missing or empty directories are ignored.
Deprecated Variations
| Group |
Name |
| DEFAULT |
policy_dirs |
-
remote_content_type
| Type: | string |
| Default: | application/x-www-form-urlencoded |
| Valid Values: | application/x-www-form-urlencoded, application/json |
Content Type to send and receive data for REST based policy check
-
remote_ssl_verify_server_crt
| Type: | boolean |
| Default: | false |
server identity verification for REST based policy check
-
remote_ssl_ca_crt_file
| Type: | string |
| Default: | <None> |
Absolute path to ca cert file for REST based policy check
-
remote_ssl_client_crt_file
| Type: | string |
| Default: | <None> |
Absolute path to client cert for REST based policy check
-
remote_ssl_client_key_file
| Type: | string |
| Default: | <None> |
Absolute path client key file REST based policy check
oslo_reports
-
log_dir
| Type: | string |
| Default: | <None> |
Path to a log directory where to create a file
-
file_event_handler
| Type: | string |
| Default: | <None> |
The path to a file to watch for changes to trigger the reports, instead of signals. Setting this option disables the signal trigger for the reports. If application is running as a WSGI application it is recommended to use this instead of signals.
-
file_event_handler_interval
-
How many seconds to wait between polls when file_event_handler is set
pooling:catalog
-
enable_virtual_pool
| Type: | boolean |
| Default: | false |
If enabled, the message_store will be used as the storage for the virtual pool.
profiler
-
trace_wsgi_transport
| Type: | boolean |
| Default: | false |
If False doesn’t trace any transport requests.Please note that it doesn’t work for websocket now.
-
trace_message_store
| Type: | boolean |
| Default: | false |
If False doesn’t trace any message store requests.
-
trace_management_store
| Type: | boolean |
| Default: | false |
If False doesn’t trace any management store requests.
-
enabled
| Type: | boolean |
| Default: | false |
Enables the profiling for all services on this node. Default value is False
(fully disable the profiling feature).
Possible values:
- True: Enables the feature
- False: Disables the feature. The profiling cannot be started via this project
operations. If the profiling is triggered by another project, this project part
will be empty.
Deprecated Variations
| Group |
Name |
| profiler |
profiler_enabled |
-
trace_sqlalchemy
| Type: | boolean |
| Default: | false |
Enables SQL requests profiling in services. Default value is False (SQL
requests won’t be traced).
Possible values:
- True: Enables SQL requests profiling. Each SQL query will be part of the
trace and can the be analyzed by how much time was spent for that.
* False: Disables SQL requests profiling. The spent time is only shown on a
higher level of operations. Single SQL queries cannot be analyzed this
way.
-
hmac_keys
| Type: | string |
| Default: | SECRET_KEY |
Secret key(s) to use for encrypting context data for performance profiling.
This string value should have the following format: <key1>[,<key2>,…<keyn>],
where each key is some random string. A user who triggers the profiling via
the REST API has to set one of these keys in the headers of the REST API call
to include profiling results of this node for this particular project.
Both “enabled” flag and “hmac_keys” config options should be set to enable
profiling. Also, to generate correct profiling information across all services
at least one key needs to be consistent between OpenStack projects. This
ensures it can be used from client side to generate the trace, containing
information from all possible resources.
-
connection_string
| Type: | string |
| Default: | messaging:// |
Connection string for a notifier backend. Default value is messaging:// which
sets the notifier to oslo_messaging.
Examples of possible values:
- messaging://: use oslo_messaging driver for sending notifications.
- mongodb://127.0.0.1:27017 : use mongodb driver for sending notifications.
- elasticsearch://127.0.0.1:9200 : use elasticsearch driver for sending
notifications.
-
es_doc_type
| Type: | string |
| Default: | notification |
Document type for notification indexing in elasticsearch.
-
es_scroll_time
-
This parameter is a time value parameter (for example: es_scroll_time=2m),
indicating for how long the nodes that participate in the search will maintain
relevant resources in order to continue and support it.
-
es_scroll_size
| Type: | integer |
| Default: | 10000 |
Elasticsearch splits large requests in batches. This parameter defines
maximum size of each batch (for example: es_scroll_size=10000).
-
socket_timeout
| Type: | floating point |
| Default: | 0.1 |
Redissentinel provides a timeout option on the connections.
This parameter defines that timeout (for example: socket_timeout=0.1).
-
sentinel_service_name
| Type: | string |
| Default: | mymaster |
Redissentinel uses a service name to identify a master redis service.
This parameter defines the name (for example:
sentinal_service_name=mymaster).
signed_url
-
secret_key
| Type: | string |
| Default: | <None> |
Secret key used to encrypt pre-signed URLs.
storage
-
queue_pipeline
-
Pipeline to use for processing queue operations. This pipeline will be consumed before calling the storage driver’s controller methods.
-
message_pipeline
-
Pipeline to use for processing message operations. This pipeline will be consumed before calling the storage driver’s controller methods.
-
claim_pipeline
-
Pipeline to use for processing claim operations. This pipeline will be consumed before calling the storage driver’s controller methods.
-
subscription_pipeline
-
Pipeline to use for processing subscription operations. This pipeline will be consumed before calling the storage driver’s controller methods.
transport
-
max_queues_per_page
-
Defines the maximum number of queues per page.
Deprecated Variations
| Group |
Name |
| limits:transport |
queue_paging_uplimit |
-
max_messages_per_page
-
Defines the maximum number of messages per page.
Deprecated Variations
| Group |
Name |
| limits:transport |
message_paging_uplimit |
-
max_subscriptions_per_page
-
Defines the maximum number of subscriptions per page.
Deprecated Variations
| Group |
Name |
| limits:transport |
subscription_paging_uplimit |
-
max_messages_per_claim_or_pop
-
The maximum number of messages that can be claimed (OR) popped in a single request
Deprecated Variations
| Group |
Name |
| transport |
max_messages_per_claim |
-
max_queue_metadata
| Type: | integer |
| Default: | 65536 |
Defines the maximum amount of metadata in a queue.
Deprecated Variations
| Group |
Name |
| limits:transport |
metadata_size_uplimit |
-
max_messages_post_size
| Type: | integer |
| Default: | 262144 |
Defines the maximum size of message posts.
Deprecated Variations
| Group |
Name |
| transport |
max_message_size |
| limits:transport |
message_size_uplimit |
-
max_message_ttl
| Type: | integer |
| Default: | 1209600 |
Maximum amount of time a message will be available.
Deprecated Variations
| Group |
Name |
| limits:transport |
message_ttl_max |
-
max_message_delay
-
Maximum delay seconds for messages can be claimed.
-
max_claim_ttl
| Type: | integer |
| Default: | 43200 |
Maximum length of a message in claimed state.
Deprecated Variations
| Group |
Name |
| limits:transport |
claim_ttl_max |
-
max_claim_grace
| Type: | integer |
| Default: | 43200 |
Defines the maximum message grace period in seconds.
Deprecated Variations
| Group |
Name |
| limits:transport |
claim_grace_max |
-
subscriber_types
| Type: | list |
| Default: | http,https,mailto,trust+http,trust+https |
Defines supported subscriber types.
-
max_flavors_per_page
-
Defines the maximum number of flavors per page.
-
max_pools_per_page
-
Defines the maximum number of pools per page.
-
default_message_ttl
| Type: | integer |
| Default: | 3600 |
Defines how long a message will be accessible.
-
default_message_delay
-
Defines the defautl value for queue delay seconds.The 0 means the delayed queues feature is close.
-
default_claim_ttl
-
Defines how long a message will be in claimed state.
-
default_claim_grace
-
Defines the message grace period in seconds.
-
default_subscription_ttl
| Type: | integer |
| Default: | 3600 |
Defines how long a subscription will be available.
trustee
-
auth_type
| Type: | unknown type |
| Default: | <None> |
Authentication type to load
Deprecated Variations
| Group |
Name |
| trustee |
auth_plugin |
-
auth_section
| Type: | unknown type |
| Default: | <None> |
Config Section from which to load plugin specific options
-
auth_url
| Type: | unknown type |
| Default: | <None> |
Authentication URL
-
system_scope
| Type: | unknown type |
| Default: | <None> |
Scope for system operations
-
domain_id
| Type: | unknown type |
| Default: | <None> |
Domain ID to scope to
-
domain_name
| Type: | unknown type |
| Default: | <None> |
Domain name to scope to
-
project_id
| Type: | unknown type |
| Default: | <None> |
Project ID to scope to
Deprecated Variations
| Group |
Name |
| trustee |
tenant-id |
| trustee |
tenant_id |
-
project_name
| Type: | unknown type |
| Default: | <None> |
Project name to scope to
Deprecated Variations
| Group |
Name |
| trustee |
tenant-name |
| trustee |
tenant_name |
-
project_domain_id
| Type: | unknown type |
| Default: | <None> |
Domain ID containing project
-
project_domain_name
| Type: | unknown type |
| Default: | <None> |
Domain name containing project
-
trust_id
| Type: | unknown type |
| Default: | <None> |
Trust ID
-
default_domain_id
| Type: | unknown type |
| Default: | <None> |
Optional domain ID to use with v3 and v2 parameters. It will be used for both the user and project domain in v3 and ignored in v2 authentication.
-
default_domain_name
| Type: | unknown type |
| Default: | <None> |
Optional domain name to use with v3 API and v2 parameters. It will be used for both the user and project domain in v3 and ignored in v2 authentication.
-
user_id
| Type: | unknown type |
| Default: | <None> |
User id
-
username
| Type: | unknown type |
| Default: | <None> |
Username
Deprecated Variations
| Group |
Name |
| trustee |
user-name |
| trustee |
user_name |
-
user_domain_id
| Type: | unknown type |
| Default: | <None> |
User’s domain id
-
user_domain_name
| Type: | unknown type |
| Default: | <None> |
User’s domain name
-
password
| Type: | unknown type |
| Default: | <None> |
User’s password