Chapter 4. designate
The following chapter contains information about the configuration options in the designate
service.
4.1. designate.conf
This section contains options for the /etc/designate/designate.conf
file.
4.1.1. DEFAULT
The following table outlines the options available under the [DEFAULT]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Enable eventlet backdoor. Acceptable values are 0, <port>, and <start>:<end>, where 0 results in listening on a random tcp port number; <port> results in listening on the specified port number (and not enabling backdoor if that port is in use); and <start>:<end> results in listening on the smallest unused port number within the specified range of port numbers. The chosen port is displayed in the service’s log file. |
| string value | Enable eventlet backdoor, using the provided path as a unix socket that can receive connections. This option is mutually exclusive with backdoor_port in that only one should be provided. If both are provided then the existence of this option overrides the usage of that option. |
| integer value | Number of backlog requests to configure the socket with |
| string value | Central Topic |
| integer value | The pool size limit for connections expiration policy |
| integer value | The time-to-live in sec of idle connections in the pool |
| string value | The default exchange under which topics are scoped. May be overridden by an exchange name specified in the transport_url option. |
| boolean value | If set to true, the logging level will be set to DEBUG instead of the default INFO level. |
| integer value | SOA expire |
| integer value | SOA minimum value |
| integer value | SOA max value |
| integer value | SOA refresh-min value |
| integer value | SOA retry |
| integer value | TTL Value |
| list value | List of package logging levels in logger=LEVEL pairs. This option is ignored if log_config_append is set. |
| integer value | Size of executor thread pool when executor is threading or eventlet. |
| boolean value | Enables or disables fatal status of deprecations. |
| integer value | Specify a timeout after which a gracefully shutdown server will exit. Zero value means endless wait. |
| string value | Name of this node |
`instance_format = [instance: %(uuid)s] ` | string value | The format for an instance that is passed with the log message. |
`instance_uuid_format = [instance: %(uuid)s] ` | string value | The format for an instance UUID that is passed with the log message. |
| string value | 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). |
| string value | Defines the format string for %%(asctime)s in log records. Default: %(default)s . This option is ignored if log_config_append is set. |
| string value | (Optional) The base directory used for relative log_file paths. This option is ignored if log_config_append is set. |
| string value | (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. |
| boolean value | Enables or disables logging values of all registered options when starting a service (at DEBUG level). |
| string value | Format string to use for log messages with context. |
| string value | Additional data to append to log message when logging level for the message is DEBUG. |
| string value | Format string to use for log messages when context is undefined. |
| string value | Prefix each line of exception output with this format. |
| string value | Defines the format string for %(user_identity)s that is used in logging_context_format_string. |
| string value | mDNS Topic |
| string value | Which API to use. |
| string value | The notification plugin to use |
| boolean value | Send notifications if there’s a failure in the API. |
| string value | Pool Manager Topic |
| boolean value | Enables or disables publication of error events. |
| string value | Directory where the designate python module is installed |
| integer value | Number of recordsets allowed in a zone export |
| string value | Quota driver to use |
| integer value | Number of records allowed per recordset |
| integer value | Number of records allowed per zone |
| integer value | Number of recordsets allowed per zone |
| integer value | Number of zones allowed per tenant |
| integer value | Maximum number of logged messages per rate_limit_interval. |
| string value | 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. |
| integer value | Interval, number of seconds, of log rate limiting. |
| string value | designate-rootwrap configuration |
| integer value | Number of seconds to wait for an ack from a cast/call. After each retry attempt this timeout is multiplied by some specified multiplier. |
| integer value | Number to multiply base ack timeout by after each retry attempt. |
| string value | The messaging driver to use, defaults to rabbit. Other drivers include amqp and zmq. |
| integer value | Size of RPC connection pool. |
| integer value | Expiration timeout in seconds of a sent/received message after which it is not tracked anymore by a client/server. |
| integer value | The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired. |
| integer value | Seconds to wait for a response from a call. |
| integer value | 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. |
| integer value | Maximum number of (green) threads to work concurrently. |
| boolean value | Wait for message acknowledgements from receivers. This mechanism works only via proxy without PUB/SUB. |
| string value | ZeroMQ bind address. Should be a wildcard (*), an ethernet interface, or IP. The "host" option should point or resolve to this address. |
| integer value | Number of retries to find free port number before fail with ZMQBindError. |
| integer value | Number of ZeroMQ contexts, defaults to 1. |
| string value | Name of this node. Must be a valid hostname, FQDN, or IP address. Must match "host" option, if running Nova. |
| string value | Directory for holding IPC sockets. |
| string value | MatchMaker driver. |
| integer value | Maximal port number for random ports range. |
| port value | Minimal port number for random ports range. |
| string value | Default serialization mechanism for serializing/deserializing outgoing/incoming messages |
| integer value | Maximum number of ingress messages to locally buffer per topic. Default is unlimited. |
| boolean value | Some periodic tasks can be run in a separate process. Should we run them here? |
| string value | Top-level directory for maintaining designate’s state |
| list value | List of publisher hosts SubConsumer can subscribe on. This option has higher priority then the default publishers list taken from the matchmaker. |
| list value | Supported record types |
| string value | Syslog facility to receive log lines. This option is ignored if log_config_append is set. |
| integer value | Sets the value of TCP_KEEPIDLE in seconds for each server socket. Not supported on OS X. |
| string value | 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 |
| boolean value | 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. |
| boolean value | Use JSON formatting for logging. This option is ignored if log_config_append is set. |
| boolean value | 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. |
| boolean value | 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). |
| boolean value | Use PUB/SUB pattern for fanout methods. PUB/SUB always uses proxy. |
| boolean value | Use ROUTER remote proxy. |
| boolean value | Log output to standard error. This option is ignored if log_config_append is set. |
| boolean value | 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. |
| string value | Worker Topic |
| integer value | Timeout in seconds for XFR’s. |
| integer value | How many additional connections to a host will be made for failover reasons. This option is actual only in dynamic connections mode. |
| boolean value | 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. |
| integer value | 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. |
| integer value | Expiration timeout in seconds of a name service record about existing target ( < 0 means no timeout). |
| integer value | Update period in seconds of a name service record about existing target. |
| integer value | 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. |
| integer value | 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. |
| integer value | 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. |
| integer value | 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. |
4.1.2. backend:agent:bind9
The following table outlines the options available under the [backend:agent:bind9]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Host to query when finding zones |
| string value | RNDC Config File |
| string value | RNDC Host |
| string value | RNDC Key File |
| integer value | RNDC Port |
| string value | Path where zone files are stored |
4.1.3. backend:agent:denominator
The following table outlines the options available under the [backend:agent:denominator]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Path to Denominator configuration file |
| string value | Name of the affected provider |
4.1.4. backend:agent:djbdns
The following table outlines the options available under the [backend:agent:djbdns]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | axfr-get executable path or rootwrap command name |
| string value | Host to query when finding zones |
| string value | tcpclient executable path or rootwrap command name |
| string value | tinydns-data executable path or rootwrap command name |
| string value | TinyDNS data directory |
4.1.5. backend:agent:gdnsd
The following table outlines the options available under the [backend:agent:gdnsd]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | gdnsd configuration directory path |
| string value | gdnsd executable path or rootwrap command name |
| string value | Host to query when finding zones |
4.1.6. backend:agent:knot2
The following table outlines the options available under the [backend:agent:knot2]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | knotc executable path or rootwrap command name |
| string value | Host to query when finding zones |
4.1.7. coordination
The following table outlines the options available under the [coordination]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value |
The backend URL to use for distributed coordination. If unset services that need coordination will function as a standalone service. This is a |
| floating point value | Number of seconds between heartbeats for distributed coordination. |
| floating point value | Number of seconds between checks to see if group membership has changed |
4.1.8. cors
The following table outlines the options available under the [cors]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Indicate that the actual request can include user credentials |
| list value | Indicate which header field names may be used during the actual request. |
| list value | Indicate which methods can be used during the actual request. |
| list value | 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 |
| list value | Indicate which headers are safe to expose to the API. Defaults to HTTP Simple Headers. |
| integer value | Maximum cache age of CORS preflight requests. |
4.1.9. database
The following table outlines the options available under the [database]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | The back end to use for the database. |
| string value | The SQLAlchemy connection string to use to connect to the database. |
| integer value | Verbosity of SQL debugging information: 0=None, 100=Everything. |
| integer value | Connections which have been present in the connection pool longer than this number of seconds will be replaced with a new one the next time they are checked out from the pool. |
| boolean value | Add Python stack traces to SQL as comment strings. |
| boolean value | If True, increases the interval between retries of a database operation up to db_max_retry_interval. |
| integer value | Maximum retries in case of connection error or deadlock error before error is raised. Set to -1 to specify an infinite retry count. |
| integer value | If db_inc_retry_interval is set, the maximum seconds between retries of a database operation. |
| integer value | Seconds between retries of a database transaction. |
| integer value | If set, use this value for max_overflow with SQLAlchemy. |
| integer value | Maximum number of SQL connections to keep open in a pool. Setting a value of 0 indicates no limit. |
| integer value | Maximum number of database connection retries during startup. Set to -1 to specify an infinite retry count. |
| integer value | Minimum number of SQL connections to keep open in a pool. |
| boolean value | If True, transparently enables support for handling MySQL Cluster (NDB). |
| string value | The SQL mode to be used for MySQL sessions. This option, including the default, overrides any server-set SQL mode. To use whatever SQL mode is set by the server configuration, set this to no value. Example: mysql_sql_mode= |
| integer value | If set, use this value for pool_timeout with SQLAlchemy. |
| integer value | Interval between retries of opening a SQL connection. |
| string value | The SQLAlchemy connection string to use to connect to the slave database. |
| boolean value | If True, SQLite uses synchronous mode. |
| boolean value | Enable the experimental use of database reconnect on connection lost. |
4.1.10. handler:neutron_floatingip
The following table outlines the options available under the [handler:neutron_floatingip]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | control-exchange for neutron notification |
| multi valued | format which replaced by formatv4/formatv6 |
| multi valued | IPv4 format |
| multi valued | IPv6 format |
| list value | notification any events from neutron |
| string value | Zone ID with each notification |
4.1.11. handler:nova_fixed
The following table outlines the options available under the [handler:nova_fixed]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | control-exchange for nova notification |
| multi valued | format which replaced by formatv4/formatv6 |
| multi valued | IPv4 format |
| multi valued | IPv6 format |
| list value | notification any events from nova |
| string value | Zone ID with each notification |
4.1.12. healthcheck
The following table outlines the options available under the [healthcheck]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| list value | Additional backends that can perform health checks and report that information back as part of a request. |
| boolean value | Show more detailed information as part of the response |
| string value | Check the presence of a file to determine if an application is running on a port. Used by DisableByFileHealthcheck plugin. |
| list value | Check the presence of a file based on a port to determine if an application is running on a port. Expects a "port:path" list of strings. Used by DisableByFilesPortsHealthcheck plugin. |
| string value | The path to respond to healtcheck requests on. |
4.1.13. heartbeat_emitter
The following table outlines the options available under the [heartbeat_emitter]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Emitter to use |
| floating point value | Number of seconds between heartbeats for reporting state |
4.1.14. keystone_authtoken
The following table outlines the options available under the [keystone_authtoken]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Config Section from which to load plugin specific options |
| string value | Authentication type to load |
| string value | 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. |
| string value | API version of the admin Identity API endpoint. |
| string value |
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 |
| string value | A PEM encoded Certificate Authority to use when verifying HTTPs connections. Defaults to system CAs. |
| string value | Required if identity server requires client certificate |
| boolean value | If true, the revocation list will be checked for cached tokens. This requires that PKI tokens are configured on the identity server. |
| boolean value | Do not handle authorization requests within the middleware, but delegate the authorization decision to downstream WSGI components. |
| string value | 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. |
| list value | 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. |
| integer value | Request timeout value for communicating with Identity API server. |
| integer value | How many times are we trying to reconnect when communicating with Identity API Server. |
| boolean value | (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. |
| boolean value | Verify HTTPS connections. |
| string value | Required if identity server requires client certificate |
| integer value | (Optional) Number of seconds that an operation will wait to get a memcached client connection from the pool. |
| integer value | (Optional) Number of seconds memcached server is considered dead before it is tried again. |
| integer value | (Optional) Maximum total number of open connections to every memcached server. |
| integer value | (Optional) Socket timeout in seconds for communicating with a memcached server. |
| integer value | (Optional) Number of seconds a connection to memcached is held unused in the pool before it is closed. |
| string value | (Optional, mandatory if memcache_security_strategy is defined) This string is used for key derivation. |
| string value | (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. |
| boolean value | (Optional) Use the advanced (eventlet safe) memcached client pool. The advanced pool will only work under python 2.x. |
| list value | Optionally specify a list of memcached server(s) to use for caching. If left undefined, tokens will instead be cached in-process. |
| string value | The region in which the identity server can be found. |
| integer value | 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. |
| list value | 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. |
| boolean value | 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. |
| string value | 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. |
| integer value | 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. |
| string value | 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. |
4.1.15. matchmaker_redis
The following table outlines the options available under the [matchmaker_redis]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Time in ms to wait before the transaction is killed. |
| string value | Host to locate redis. |
`password = ` | string value | Password for Redis server (optional). |
| port value | Use this port to connect to redis host. |
| string value | Redis replica set name. |
| list value | List of Redis Sentinel hosts (fault tolerance mode), e.g., [host:port, host1:port … ] |
| integer value | Timeout in ms on blocking socket operations. |
| integer value | Time in ms to wait between connection attempts. |
4.1.16. monasca:statsd
The following table outlines the options available under the [monasca:statsd]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | enable |
| string value | hostname |
| integer value | UDP port |
4.1.17. network_api:neutron
The following table outlines the options available under the [network_api:neutron]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | password for connecting to neutron in admin context |
| string value | tenant name for connecting to neutron in admin context |
| string value | username for connecting to neutron in admin context |
| string value | auth strategy for connecting to neutron in admin context |
| string value | auth url for connecting to neutron in admin context |
| string value | Location of ca certificates file to use for neutron client requests. |
| string value | Endpoint type to use |
| list value | URL to use if None in the ServiceCatalog that is passed by the request context. Format: <region>|<url> |
| boolean value | if set, ignore any SSL validation issues |
| integer value | timeout value for connecting to neutron in seconds |
4.1.18. oslo_concurrency
The following table outlines the options available under the [oslo_concurrency]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Enables or disables inter-process locks. |
| string value | Directory to use for lock files. For security, the specified directory should only be writable by the user running the processes that need locking. Defaults to environment variable OSLO_LOCK_PATH. If external locks are used, a lock path must be set. |
4.1.19. oslo_messaging_amqp
The following table outlines the options available under the [oslo_messaging_amqp]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | 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 |
| boolean value | Accept clients using either SSL or plain TCP |
| string value | 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. |
| string value | address prefix used when broadcasting to all servers |
| integer value | Increase the connection_retry_interval by this many seconds after each unsuccessful failover attempt. |
| integer value | Seconds to pause before attempting to re-connect. |
| integer value | Maximum limit for connection_retry_interval + connection_retry_backoff |
| string value | Name for the AMQP container. must be globally unique. Defaults to a generated UUID |
| string value | 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 |
| integer value | The deadline for a sent notification message delivery. Only used when caller does not provide a timeout expiry. |
| integer value | The maximum number of attempts to re-send a reply message which failed due to a recoverable error. |
| integer value | The deadline for an rpc reply message delivery. |
| string value | 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 |
| integer value | The deadline for an rpc cast or call message delivery. Only used when caller does not provide a timeout expiry. |
| integer value | The duration to schedule a purge of idle sender links. Detach link after expiry. |
| string value | address prefix when sending to any server in group |
| integer value | Timeout for inactive connections (in seconds) |
| integer value | Time to pause between re-connecting an AMQP 1.0 link that failed due to a recoverable error. |
| string value | Appended to the address prefix when sending a fanout message. Used by the message bus to identify fanout messages. |
| string value | Address prefix for all generated Notification addresses |
| integer value | Window size for incoming Notification messages |
`password = ` | string value | Password for message broker authentication |
| multi valued | 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 |
| boolean value | 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. |
| integer value | Window size for incoming RPC Reply messages. |
| string value | Address prefix for all generated RPC addresses |
| integer value | Window size for incoming RPC Request messages |
`sasl_config_dir = ` | string value | Path to directory that contains the SASL configuration |
`sasl_config_name = ` | string value | Name of configuration file (without .conf suffix) |
`sasl_default_realm = ` | string value | SASL realm to use if no realm present in username |
`sasl_mechanisms = ` | string value | Space separated list of acceptable SASL mechanisms |
| string value | address prefix used when sending to a specific server |
| boolean value | 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 = ` | string value | CA certificate PEM file used to verify the server’s certificate |
`ssl_cert_file = ` | string value | Self-identifying certificate PEM file for client authentication |
`ssl_key_file = ` | string value | Private key PEM file used to sign ssl_cert_file certificate (optional) |
| string value | Password for decrypting ssl_key_file (if encrypted) |
| boolean value | 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. |
| boolean value | Debug: dump AMQP frames to stdout |
| string value | 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. |
`username = ` | string value | User name for message broker authentication |
4.1.20. oslo_messaging_kafka
The following table outlines the options available under the [oslo_messaging_kafka]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | The pool size limit for connections expiration policy |
| integer value | The time-to-live in sec of idle connections in the pool |
| string value | Group id for Kafka consumer. Consumers in one group will coordinate message consumption |
| floating point value | Default timeout(s) for Kafka consumers |
| string value | Default Kafka broker Host |
| port value | Default Kafka broker Port |
| integer value | Max fetch bytes of Kafka consumer |
| integer value | Pool Size for Kafka Consumers |
| integer value | Size of batch for the producer async send |
| floating point value | Upper bound on the delay for KafkaProducer batching in seconds |
4.1.21. oslo_messaging_notifications
The following table outlines the options available under the [oslo_messaging_notifications]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| multi valued | The Drivers(s) to handle sending notifications. Possible values are messaging, messagingv2, routing, log, test, noop |
| integer value | 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 |
| list value | AMQP topic used for OpenStack notifications. |
| string value | A URL representing the messaging driver to use for notifications. If not set, we fall back to the same configuration used for RPC. |
4.1.22. oslo_messaging_rabbit
The following table outlines the options available under the [oslo_messaging_rabbit]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Auto-delete queues in AMQP. |
| boolean value | Use durable queues in AMQP. |
| integer value | Maximum number of channels to allow |
| string value | Connection factory implementation |
| string value | Exchange name for sending notifications |
| integer value | Reconnecting retry count in case of connectivity problem during sending notification, -1 means infinite retry. |
| string value | Exchange name for sending RPC messages |
| integer value | 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 |
| string value | Default serialization mechanism for serializing/deserializing outgoing/incoming messages |
| boolean value | Deprecated, use rpc_backend=kombu+memory or rpc_backend=fake |
| integer value | The maximum byte size for an AMQP frame |
| integer value | How often to send heartbeats for consumer’s connections |
| integer value | How often times during the heartbeat_timeout_threshold we check the heartbeat. |
| integer value | Number of seconds after which the Rabbit broker is considered down if heartbeat’s keep-alive fails (0 disable the heartbeat). EXPERIMENTAL |
| floating point value | Set delay for reconnection to some host which has connection error |
| string value | EXPERIMENTAL: Possible values are: gzip, bz2. If not set compression will not be used. This option may not be available in future versions. |
| string value | 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. |
| integer value | How long to wait a missing client before abandoning to send it its replies. This value should not be longer than rpc_response_timeout. |
| floating point value | How long to wait before reconnecting in response to an AMQP consumer cancel notification. |
| integer value | Max number of not acknowledged message which RabbitMQ can send to notification listener. |
| boolean value | Persist notification messages. |
| floating point value | Reconnecting retry delay in case of connectivity problem during sending notification message |
| integer value |
Maximum number of connections to create above |
| integer value | Maximum number of connections to keep queued. |
| integer value | Lifetime of a connection (since creation) in seconds or None for no recycling. Expired connections are closed on acquire. |
| integer value | Threshold at which inactive (since release) connections are considered stale in seconds or None for no staleness. Stale connections are closed on acquire. |
| integer value | Default number of seconds to wait for a connections to available |
| boolean value | 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"} " |
| string value | The RabbitMQ broker address where a single node is used. |
| list value | RabbitMQ HA cluster host:port pairs. |
| integer value | Maximum interval of RabbitMQ connection retries. Default is 30 seconds. |
| string value | The RabbitMQ login method. |
| integer value | Maximum number of RabbitMQ connection retries. Default is 0 (infinite retry count). |
| string value | The RabbitMQ password. |
| port value | The RabbitMQ broker port where a single node is used. |
| integer value | Specifies the number of messages to prefetch. Setting to zero allows unlimited messages. |
| integer value | How long to backoff for between retries when connecting to RabbitMQ. |
| integer value | How frequently to retry connecting with RabbitMQ. |
| integer value | 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. |
| string value | The RabbitMQ userid. |
| string value | The RabbitMQ virtual host. |
| integer value | Max number of not acknowledged message which RabbitMQ can send to rpc listener. |
| integer value | Time to live for rpc queues without consumers in seconds. |
| string value | Exchange name for receiving RPC replies |
| integer value | Max number of not acknowledged message which RabbitMQ can send to rpc reply listener. |
| integer value | Reconnecting retry count in case of connectivity problem during sending reply. -1 means infinite retry during rpc_timeout |
| floating point value | Reconnecting retry delay in case of connectivity problem during sending reply. |
| floating point value | Reconnecting retry delay in case of connectivity problem during sending RPC message |
| floating point value | Set socket timeout in seconds for connection’s socket |
| boolean value | Enable SSL |
`ssl_ca_file = ` | string value | SSL certification authority file (valid only if SSL enabled). |
`ssl_cert_file = ` | string value | SSL cert file (valid only if SSL enabled). |
`ssl_key_file = ` | string value | SSL key file (valid only if SSL enabled). |
| dict value | Arguments passed to ssl.wrap_socket |
`ssl_version = ` | string value | 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. |
| floating point value | Set TCP_USER_TIMEOUT in seconds for connection’s socket |
4.1.23. oslo_messaging_zmq
The following table outlines the options available under the [oslo_messaging_zmq]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Number of seconds to wait for an ack from a cast/call. After each retry attempt this timeout is multiplied by some specified multiplier. |
| integer value | Number to multiply base ack timeout by after each retry attempt. |
| integer value | Expiration timeout in seconds of a sent/received message after which it is not tracked anymore by a client/server. |
| integer value | The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired. |
| integer value | 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. |
| integer value | Maximum number of (green) threads to work concurrently. |
| boolean value | Wait for message acknowledgements from receivers. This mechanism works only via proxy without PUB/SUB. |
| string value | ZeroMQ bind address. Should be a wildcard (*), an ethernet interface, or IP. The "host" option should point or resolve to this address. |
| integer value | Number of retries to find free port number before fail with ZMQBindError. |
| integer value | Number of ZeroMQ contexts, defaults to 1. |
| string value | Name of this node. Must be a valid hostname, FQDN, or IP address. Must match "host" option, if running Nova. |
| string value | Directory for holding IPC sockets. |
| string value | MatchMaker driver. |
| integer value | Maximal port number for random ports range. |
| port value | Minimal port number for random ports range. |
| string value | Default serialization mechanism for serializing/deserializing outgoing/incoming messages |
| integer value | Maximum number of ingress messages to locally buffer per topic. Default is unlimited. |
| list value | List of publisher hosts SubConsumer can subscribe on. This option has higher priority then the default publishers list taken from the matchmaker. |
| boolean value | 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). |
| boolean value | Use PUB/SUB pattern for fanout methods. PUB/SUB always uses proxy. |
| boolean value | Use ROUTER remote proxy. |
| integer value | How many additional connections to a host will be made for failover reasons. This option is actual only in dynamic connections mode. |
| boolean value | 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. |
| integer value | 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. |
| integer value | Expiration timeout in seconds of a name service record about existing target ( < 0 means no timeout). |
| integer value | Update period in seconds of a name service record about existing target. |
| integer value | 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. |
| integer value | 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. |
| integer value | 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. |
| integer value | 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. |
4.1.24. oslo_middleware
The following table outlines the options available under the [oslo_middleware]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Whether the application is behind a proxy or not. This determines if the middleware should parse the headers or not. |
| integer value | The maximum body size for each request, in bytes. |
| string value | The HTTP Header that will be used to determine what the original request protocol scheme was, even if it was hidden by a SSL termination proxy. |
4.1.25. oslo_policy
The following table outlines the options available under the [oslo_policy]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value |
This option controls whether or not to enforce scope when evaluating policies. If |
| string value | Default rule. Enforced when a requested rule is not found. |
| multi valued | 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. |
| string value | The file that defines policies. |
| string value | Content Type to send and receive data for REST based policy check |
| string value | Absolute path to ca cert file for REST based policy check |
| string value | Absolute path to client cert for REST based policy check |
| string value | Absolute path client key file REST based policy check |
| boolean value | server identity verification for REST based policy check |
4.1.26. pool_manager_cache:memcache
The following table outlines the options available under the [pool_manager_cache:memcache]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Time in seconds to expire cache. |
| list value | Memcached servers or None for in process cache. |
4.1.27. pool_manager_cache:sqlalchemy
The following table outlines the options available under the [pool_manager_cache:sqlalchemy]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | The back end to use for the database. |
| string value | The SQLAlchemy connection string to use to connect to the database. |
| integer value | Verbosity of SQL debugging information: 0=None, 100=Everything. |
| integer value | Connections which have been present in the connection pool longer than this number of seconds will be replaced with a new one the next time they are checked out from the pool. |
| boolean value | Add Python stack traces to SQL as comment strings. |
| boolean value | If True, increases the interval between retries of a database operation up to db_max_retry_interval. |
| integer value | Maximum retries in case of connection error or deadlock error before error is raised. Set to -1 to specify an infinite retry count. |
| integer value | If db_inc_retry_interval is set, the maximum seconds between retries of a database operation. |
| integer value | Seconds between retries of a database transaction. |
| integer value | If set, use this value for max_overflow with SQLAlchemy. |
| integer value | Maximum number of SQL connections to keep open in a pool. Setting a value of 0 indicates no limit. |
| integer value | Maximum number of database connection retries during startup. Set to -1 to specify an infinite retry count. |
| integer value | Minimum number of SQL connections to keep open in a pool. |
| boolean value | If True, transparently enables support for handling MySQL Cluster (NDB). |
| string value | The SQL mode to be used for MySQL sessions. This option, including the default, overrides any server-set SQL mode. To use whatever SQL mode is set by the server configuration, set this to no value. Example: mysql_sql_mode= |
| integer value | If set, use this value for pool_timeout with SQLAlchemy. |
| integer value | Interval between retries of opening a SQL connection. |
| string value | The SQLAlchemy connection string to use to connect to the slave database. |
| boolean value | If True, SQLite uses synchronous mode. |
| boolean value | Enable the experimental use of database reconnect on connection lost. |
4.1.28. producer_task:delayed_notify
The following table outlines the options available under the [producer_task:delayed_notify]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | How many zones to receive NOTIFY on each run |
| integer value | Run interval in seconds |
| integer value | Default amount of results returned per page |
4.1.29. producer_task:periodic_exists
The following table outlines the options available under the [producer_task:periodic_exists]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Run interval in seconds |
| integer value | Default amount of results returned per page |
4.1.30. producer_task:periodic_secondary_refresh
The following table outlines the options available under the [producer_task:periodic_secondary_refresh]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Run interval in seconds |
| integer value | Default amount of results returned per page |
4.1.31. producer_task:worker_periodic_recovery
The following table outlines the options available under the [producer_task:worker_periodic_recovery]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Run interval in seconds |
| integer value | Default amount of results returned per page |
4.1.32. producer_task:zone_purge
The following table outlines the options available under the [producer_task:zone_purge]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | How many zones to be purged on each run |
| integer value | Run interval in seconds |
| integer value | Default amount of results returned per page |
| integer value | How old deleted zones should be (deleted_at) to be purged, in seconds |
4.1.33. proxy
The following table outlines the options available under the [proxy]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Proxy HTTP requests via this proxy. |
| string value | Proxy HTTPS requests via this proxy |
| list value | These addresses should not be proxied |
4.1.34. service:agent
The following table outlines the options available under the [service:agent]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| list value | List of IP addresses allowed to NOTIFY The Agent |
| string value | The backend driver to use, e.g. bind9, djbdns, knot2 |
| IP address value | Agent Bind Host |
| list value | Agent host:port pairs to listen on |
| list value | List of masters for the Agent, format ip:port |
| floating point value | Delay after a NOTIFY arrives for a zone that the Agent will pause and drop subsequent NOTIFYs for that zone |
| port value | Agent Port Number |
| integer value | The Agent TCP Backlog |
| floating point value | Agent TCP Receive Timeout |
| integer value | Number of agent greenthreads to spawn |
| string value | An IP address to be used to fetch zones transferred in |
| integer value | Number of agent worker processes to spawn |
4.1.35. service:api
The following table outlines the options available under the [service:api]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | the url used as the base for all API responses,This should consist of the scheme (http/https),the hostname, port, and any paths that are addedto the base of Designate is URLs,For example http://dns.openstack.example.com/dns |
| IP address value | API Bind Host |
| string value | File name for the paste.deploy config for designate-api |
| port value | API Port Number |
| string value | The strategy to use for auth. Supports noauth or keystone |
| integer value | Default per-page limit for the Admin API, a value of None means show all results by default |
| integer value | Default per-page limit for the V2 API, a value of None means show all results by default |
| boolean value | enable-api-admin |
| boolean value | enable-api-v2 which enable in a future |
| boolean value | Enable host request headers |
| list value | Enabled Admin API Extensions |
| list value | Enabled API Extensions for the V2 API |
| list value | API host:port pairs to listen on |
| boolean value | Enable API Maintenance Mode |
| string value | Role allowed to bypass maintaince mode |
| integer value | Max per-page limit for the Admin API |
| integer value | Max per-page limit for the V2 API |
| integer value | Maximum line size of message headers to be accepted. max_header_line may need to be increased when using large tokens (typically those generated by the Keystone v3 API with big service catalogs). |
| string value | A scheme that will be used to override the request protocol scheme, even if it was set by an SSL terminating proxy. |
| string value | The HTTP Header that will be used to determine which the original request protocol scheme was, even if it was removed by an SSL terminating proxy. |
| integer value | Number of api greenthreads to spawn |
| integer value | Number of api worker processes to spawn |
4.1.36. service:central
The following table outlines the options available under the [service:central]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | RPC topic name of central service. |
| string value | The name of the default pool |
| list value | Enabled Notification Handlers |
| string value | E-Mail for Managed resources |
| string value | The Tenant ID that will own any managed resources. |
| integer value | Maximum recordset name length |
| integer value | Maximum zone name length |
| integer value | Minimum TTL allowed |
| list value | Enabled Pool Scheduling filters |
| string value | The storage driver to use |
| integer value | Number of central greenthreads to spawn |
| integer value | Number of central worker processes to spawn |
4.1.37. service:mdns
The following table outlines the options available under the [service:mdns]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Send all traffic over TCP |
| IP address value | mDNS Bind Host |
| list value | mDNS host:port pairs to listen on |
| integer value | Maximum message size to emit |
| string value | RPC topic name for mini-DNS |
| port value | mDNS Port Number |
| boolean value | Enforce all incoming queries (including AXFR) are TSIG signed |
| string value | The storage driver to use |
| integer value | mDNS TCP Backlog |
| floating point value | mDNS TCP Receive Timeout |
| integer value | Number of mdns greenthreads to spawn |
| integer value | Number of mdns worker processes to spawn |
4.1.38. service:pool_manager
The following table outlines the options available under the [service:pool_manager]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | The cache driver to use |
| boolean value | The flag for the recovery timer |
| boolean value | The flag for the sync timer |
| integer value | The time between recovering from failures |
| integer value | The time between synchronizing the servers with storage |
| integer value | Number of attempts to update a zone during sync |
| integer value | Interval between zone update attempts during sync |
| integer value | Zones Updated within last N seconds will be syncd.Use an empty value to sync all zones. |
| integer value | The time to wait before sending the first request to a server |
| integer value | The maximum number of times to retry sending a request and wait for a response from a server |
| integer value | The time between retrying to send a request and waiting for a response from a server |
| integer value | The time to wait for a response from a server |
| string value | The ID of the pool managed by this instance of the Pool Manager |
| string value | RPC topic name for pool-manager |
| integer value | Number of Pool Manager greenthreads to spawn |
| integer value | The percentage of servers requiring a successful update for a zone change to be considered active |
| integer value | Number of Pool Manager worker processes to spawn |
4.1.39. service:producer
The following table outlines the options available under the [service:producer]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| list value | Enabled tasks to run |
| boolean value | Whether to allow synchronous zone exports |
| string value | The storage driver to use |
| integer value | Number of Producer greenthreads to spawn |
| integer value | Number of Producer worker processes to spawn |
4.1.40. service:sink
The following table outlines the options available under the [service:sink]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| list value | Enabled Notification Handlers |
| integer value | Number of sink greenthreads to spawn |
| integer value | Number of sink worker processes to spawn |
4.1.41. service:worker
The following table outlines the options available under the [service:worker]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Whether to send events to worker instead of Pool Manager |
| boolean value | Whether to allow synchronous zone exports |
| boolean value | Whether to allow worker to send NOTIFYs, this will noop NOTIFYs in mdns if true |
| integer value | The time to wait before sending the first request to a server |
| integer value | The maximum number of times to retry sending a request and wait for a response from a server |
| integer value | The time between retrying to send a request and waiting for a response from a server |
| integer value | The time to wait for a response from a server |
| string value | The storage driver to use |
| integer value | Number of Worker threads to spawn per process |
| integer value | The percentage of servers requiring a successful update for a domain change to be considered active |
| string value | RPC topic for worker component |
| integer value | Number of Worker worker processes to spawn |
4.1.42. service:zone_manager
The following table outlines the options available under the [service:zone_manager]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| list value | Enabled tasks to run |
| boolean value | Whether to allow synchronous zone exports |
| string value | The storage driver to use |
| integer value | Number of Zone Manager greenthreads to spawn |
| integer value | Number of Zone Manager worker processes to spawn |
4.1.43. ssl
The following table outlines the options available under the [ssl]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | CA certificate file to use to verify connecting clients. |
| string value | Certificate file to use when starting the server securely. |
| string value | Sets the list of available ciphers. value should be a string in the OpenSSL cipher list format. |
| string value | Private key file to use when starting the server securely. |
| string value | 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. |
4.1.44. storage:sqlalchemy
The following table outlines the options available under the [storage:sqlalchemy]
group in the /etc/designate/designate.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | The back end to use for the database. |
| string value | The SQLAlchemy connection string to use to connect to the database. |
| integer value | Verbosity of SQL debugging information: 0=None, 100=Everything. |
| integer value | Connections which have been present in the connection pool longer than this number of seconds will be replaced with a new one the next time they are checked out from the pool. |
| boolean value | Add Python stack traces to SQL as comment strings. |
| boolean value | If True, increases the interval between retries of a database operation up to db_max_retry_interval. |
| integer value | Maximum retries in case of connection error or deadlock error before error is raised. Set to -1 to specify an infinite retry count. |
| integer value | If db_inc_retry_interval is set, the maximum seconds between retries of a database operation. |
| integer value | Seconds between retries of a database transaction. |
| integer value | If set, use this value for max_overflow with SQLAlchemy. |
| integer value | Maximum number of SQL connections to keep open in a pool. Setting a value of 0 indicates no limit. |
| integer value | Maximum number of database connection retries during startup. Set to -1 to specify an infinite retry count. |
| integer value | Minimum number of SQL connections to keep open in a pool. |
| boolean value | If True, transparently enables support for handling MySQL Cluster (NDB). |
| string value | The SQL mode to be used for MySQL sessions. This option, including the default, overrides any server-set SQL mode. To use whatever SQL mode is set by the server configuration, set this to no value. Example: mysql_sql_mode= |
| integer value | If set, use this value for pool_timeout with SQLAlchemy. |
| integer value | Interval between retries of opening a SQL connection. |
| string value | The SQLAlchemy connection string to use to connect to the slave database. |
| boolean value | If True, SQLite uses synchronous mode. |
| boolean value | Enable the experimental use of database reconnect on connection lost. |