host address
\nvirt64b
i-capture-the-hostname
Name of this node. This can be an opaque identifier. It is not necessarily a hostname, FQDN, or IP address. However, the node name must be valid within an AMQP key.
\n90
Maximum time since last check-in for up service.
\n \n \ninteger
\n+30
1
\n+Size of RPC connection pool.
\n+Group | \n+Name | \n+
|---|---|
DEFAULT | \n+rpc_conn_pool_size | \n+
integer
\n+2
The pool size limit for connections expiration policy
\n+integer
\n+1200
The time-to-live in sec of idle connections in the pool
\n+integer
\n+64
Size of executor thread pool when executor is threading or eventlet.
\n+Group | \n+Name | \n+
|---|---|
DEFAULT | \n+rpc_thread_pool_size | \n+
integer
\n+60
Seconds to wait for a response from a call.
\n+string
\n+rabbit://
The network address and optional user credentials for connecting to the messaging backend, in URL format. The expected format is:
\n+driver://[user:pass@]host:port[,[userN:passN@]hostN:portN]/virtual_host?query
\n+Example: rabbit://rabbitmq:password@127.0.0.1:5672//
\n+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
\n+string
\n+openstack
The default exchange under which topics are scoped. May be overridden by an exchange name specified in the transport_url option.
\n+boolean
\n+False
Add an endpoint to answer to ping calls. Endpoint is named oslo_rpc_server_ping
\n+boolean
\n+True
Some periodic tasks can be run in a separate process. Should we run them here?
\n+string
\n+<None>
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\u2019s log file.
\n+string
\n+<None>
Enable eventlet backdoor, using the provided path as a unix socket that can receive connections. This option is mutually exclusive with \u2018backdoor_port\u2019 in that only one should be provided. If both are provided then the existence of this option overrides the usage of that option. Inside the path {pid} will be replaced with the PID of the current process.
\n+boolean
\n+True
Enables or disables logging values of all registered options when starting a service (at DEBUG level).
\n+integer
\n+60
Specify a timeout after which a gracefully shutdown server will exit. Zero value means endless wait.
\n+string
\n+api-paste.ini
File name for the paste.deploy config for api service
\n+string
\n+%(client_ip)s "%(request_line)s" status: %(status_code)s len: %(body_length)s time: %(wall_seconds).7f
A python format string that is used as the template to generate log lines. The following values can beformatted into it: client_ip, date_time, request_line, status_code, body_length, wall_seconds.
\n+integer
\n+600
Sets the value of TCP_KEEPIDLE in seconds for each server socket. Not supported on OS X.
\n+integer
\n+100
Size of the pool of greenthreads used by wsgi
\n+integer
\n+16384
Maximum line size of message headers to be accepted. max_header_line may need to be increased when using large tokens (typically those generated when keystone is configured to use PKI tokens with big service catalogs).
\n+boolean
\n+True
If False, closes the client socket connection explicitly.
\n+integer
\n+900
Timeout for client connections\u2019 socket operations. If an incoming connection is idle for this number of seconds it will be closed. A value of \u20180\u2019 means wait forever.
\n+boolean
\n+False
True if the server should send exception tracebacks to the clients on 500 errors. If False, the server will respond with empty bodies.
\n+boolean
\n<None>
This option can be changed without restarting.
\nThe 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, log-date-format).
\n-Group | \n Name | \n |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
DEFAULT | \n@@ -288,16 +614,16 @@\n
Group | \n Name | \n ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
DEFAULT | \n@@ -315,16 +641,16 @@\n
Group | \n Name | \n |||||||
|---|---|---|---|---|---|---|---|---|
DEFAULT | \n@@ -734,340 +1060,14 @@\n
Group | \n-Name | \n-
|---|---|
DEFAULT | \n-rpc_conn_pool_size | \n-
integer
\n-2
The pool size limit for connections expiration policy
\n-integer
\n-1200
The time-to-live in sec of idle connections in the pool
\n-integer
\n-64
Size of executor thread pool when executor is threading or eventlet.
\n-Group | \n-Name | \n-
|---|---|
DEFAULT | \n-rpc_thread_pool_size | \n-
integer
\n-60
Seconds to wait for a response from a call.
\n-string
\n-rabbit://
The network address and optional user credentials for connecting to the messaging backend, in URL format. The expected format is:
\n-driver://[user:pass@]host:port[,[userN:passN@]hostN:portN]/virtual_host?query
\n-Example: rabbit://rabbitmq:password@127.0.0.1:5672//
\n-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
\n-string
\n-openstack
The default exchange under which topics are scoped. May be overridden by an exchange name specified in the transport_url option.
\n-boolean
\n-False
Add an endpoint to answer to ping calls. Endpoint is named oslo_rpc_server_ping
\n-