Chapter 13. octavia
The following chapter contains information about the configuration options in the octavia
service.
13.1. octavia.conf Copy linkLink copied to clipboard!
This section contains options for the /etc/octavia/octavia.conf
file.
13.1.1. DEFAULT Copy linkLink copied to clipboard!
The following table outlines the options available under the [DEFAULT]
group in the /etc/octavia/octavia.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 | 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. |
| 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. |
| hostname value | The hostname Octavia is running on |
`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, log-date-format). |
| 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). |
| integer value | The amount of time before the log files are rotated. This option is ignored unless log_rotation_type is setto "interval". |
| string value | Rotation interval type. The time of the last file change (or the time when the service was started) is used when scheduling the next rotation. |
| string value | Log rotation type. |
| string value | Format string to use for log messages with context. Used by oslo_log.formatters.ContextFormatter |
| string value | Additional data to append to log message when logging level for the message is DEBUG. Used by oslo_log.formatters.ContextFormatter |
| string value | Format string to use for log messages when context is undefined. Used by oslo_log.formatters.ContextFormatter |
| string value | Prefix each line of exception output with this format. Used by oslo_log.formatters.ContextFormatter |
| string value | Defines the format string for %(user_identity)s that is used in logging_context_format_string. Used by oslo_log.formatters.ContextFormatter |
| integer value | Maximum number of rotated log files. |
| integer value | Log file maximum size in MB. This option is ignored if "log_rotation_type" is not set to "size". |
| string value | Name of the controller plugin to use |
| boolean value | Enables or disables publication of error events. |
| 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. |
| integer value | Size of RPC connection pool. |
| boolean value | Add an endpoint to answer to ping calls. Endpoint is named oslo_rpc_server_ping |
| integer value | Seconds to wait for a response from a call. |
| string value | Syslog facility to receive log lines. This option is ignored if log_config_append is set. |
| 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 | Log output to Windows Event Log. |
| 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. |
13.1.2. amphora_agent Copy linkLink copied to clipboard!
The following table outlines the options available under the [amphora_agent]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| list value | List of log server ip and port pairs for Administrative logs. Additional hosts are backup to the primary server. If none is specified remote logging is disabled. Example 127.0.0.1:10514, 192.168.0.1:10514 |
| integer value | LOG_LOCAL facility number to use for amphora processes logs. |
| integer value | The time in seconds to allow a request from the controller to run before terminating the socket. |
| string value | The ca which signed the client certificates |
| string value | The server certificate for the agent server to use |
| string value | The directory where new network interfaces are located |
| string value | The file where the network interfaces are located. Specifying this will override any value set for agent_server_network_dir. Deprecated since: Xena *Reason:*New amphora interface management does not support single interface file. |
| string value | Minimum TLS protocol for communication with the amphora agent. |
| string value | The amphora ID. |
| string value | The UDP API backend for amphora agent. Deprecated since: Wallaby *Reason:*amphora-agent will not support any other backend than keepalived_lvs. |
| boolean value | When True, no logs will be written to the amphora filesystem. When False, log files will be written to the local filesystem. |
| boolean value | When True, the amphora will forward all of the system logs (except tenant traffic logs) to the admin log target(s). When False, only amphora specific admin logs will be forwarded. |
| string value | The log forwarding transport protocol. One of UDP or TCP. |
| integer value | The queue size (messages) to buffer log messages. |
| integer value | The maximum attempts to retry connecting to the logging host. |
| integer value | The time, in seconds, to wait between retries connecting to the logging host. |
| string value | Custom logging configuration template. |
| list value | List of log server ip and port pairs for tenant traffic logs. Additional hosts are backup to the primary server. If none is specified remote logging is disabled. Example 127.0.0.1:10514, 192.168.0.1:10514 |
| integer value | LOG_LOCAL facility number to use for user traffic logs. |
13.1.3. api_settings Copy linkLink copied to clipboard!
The following table outlines the options available under the [api_settings]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Allow the usage of field selection |
| boolean value | Allow the usage of filtering |
| boolean value | Allow the usage of pagination |
| boolean value | Allow users to create PING type Health Monitors? |
| boolean value | Allow the usage of sorting |
| boolean value | Allow users to create TLS Terminated listeners? |
| string value | Base URI for the API for use in pagination links. This will be autodetected from the request if not overridden here. |
| string value | The auth strategy for API requests. |
| IP address value | The host IP to bind to |
| port value | The port to bind to |
| list value | List of ALPN protocols to use for new TLS-enabled listeners. |
| string value | Default OpenSSL cipher string (colon-separated) for new TLS-enabled listeners. |
| list value | List of TLS versions to use for new TLS-enabled listeners. |
| list value | List of ALPN protocols to use for new TLS-enabled pools. |
| string value | Default OpenSSL cipher string (colon-separated) for new TLS-enabled pools. |
| list value | List of TLS versions to use for new TLS-enabled pools. |
| string value | Default provider driver. |
| dict value | A comma separated list of dictionaries of the enabled provider driver names and descriptions. Must match the driver name in the octavia.api.drivers entrypoint. Example: amphora:The Octavia Amphora driver.,octavia:Deprecated alias of the Octavia Amphora driver. |
| boolean value | When True, the oslo middleware healthcheck endpoint is enabled in the Octavia API. |
| integer value | The interval healthcheck plugins should cache results, in seconds. |
| string value | Minimum allowed TLS version for listeners and pools. |
| string value | The maximum number of items returned in a single response. The string infinite or a negative integer value means no limit |
`tls_cipher_prohibit_list = ` | string value | Colon separated list of OpenSSL ciphers. Usage of these ciphers will be blocked. |
| integer value | The minimum health monitor delay interval for the UDP-CONNECT Health Monitor type. A negative integer value means no limit. |
13.1.4. audit Copy linkLink copied to clipboard!
The following table outlines the options available under the [audit]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Path to audit map file for octavia-api service. Used only when API audit is enabled. |
| boolean value | Enable auditing of API requests |
`ignore_req_list = ` | string value | Comma separated list of REST API HTTP methods to be ignored during audit. For example: auditing will not be done on any GET or POST requests if this is set to "GET,POST". It is used only when API audit is enabled. |
13.1.5. barbican Copy linkLink copied to clipboard!
The following table outlines the options available under the [barbican]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Use this endpoint to connect to Keystone |
| string value | Version of the Barbican API, for example: "v1" |
| string value | Use this endpoint to connect to Barbican, for example: "http://localhost:9311/" |
| string value | Specifies the type of endpoint. Allowed values are: public, private, and admin |
| integer value | Number of times to retry poll for key creation completion |
| integer value | Number of seconds to wait before retrying poll for key creation completion |
| boolean value | Specifies if insecure TLS (https) requests. If False, the server’s certificate will not be validated, if True, we can set the verify_ssl_path config meanwhile. |
| string value | A path to a bundle or CA certs to check against, or None for requests to attempt to locate and use certificates which verify_ssh is True. If verify_ssl is False, this is ignored. |
13.1.6. certificates Copy linkLink copied to clipboard!
The following table outlines the options available under the [certificates]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Name of the Barbican authentication method to use |
| string value | Absolute path to the CA Certificate for signing. Defaults to env[OS_OCTAVIA_TLS_CA_CERT]. |
| string value | CA certificates file path for the key manager service (such as Barbican). |
| string value | Absolute path to the Private Key for signing. Defaults to env[OS_OCTAVIA_TLS_CA_KEY]. |
| string value | Passphrase for the Private Key. Defaults to env[OS_OCTAVIA_CA_KEY_PASS] or None. |
| string value | Name of the cert generator to use |
| string value | Name of the cert manager to use |
| integer value | The validity time for the Amphora Certificates (in seconds). |
| string value | A new endpoint to override the endpoint in the keystone catalog. |
| string value | The endpoint_type to be used for barbican service. |
| boolean value | Disable certificate validation on SSL connections |
| string value | Region in Identity service catalog to use for communication with the barbican service. |
| string value | Passphrase for encrypting Amphora Certificates and Private Keys. Must be 32, base64(url) compatible, characters long. Defaults to env[TLS_PASS_AMPS_DEFAULT] or insecure-key-do-not-use-this-key |
| string value | The name of the certificate service in the keystone catalog |
| string value | Certificate signing digest. Defaults to env[OS_OCTAVIA_CA_SIGNING_DIGEST] or "sha256". |
13.1.7. compute Copy linkLink copied to clipboard!
The following table outlines the options available under the [compute]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | The maximum attempts to retry an action with the compute service. |
| integer value | The seconds to backoff retry attempts. |
| integer value | Seconds to wait before retrying an action with the compute service. |
| integer value | The maximum interval in seconds between retry attempts. |
13.1.8. controller_worker Copy linkLink copied to clipboard!
The following table outlines the options available under the [controller_worker]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Retry attempts to wait for Amphora to become active |
| integer value | Seconds to wait between checks on whether an Amphora has become active |
`amp_boot_network_list = ` | list value | List of networks to attach to the Amphorae. All networks defined in the list will be attached to each amphora. |
`amp_flavor_id = ` | string value | Nova instance flavor id for the Amphora |
`amp_image_owner_id = ` | string value | Restrict glance image selection to a specific owner ID. This is a recommended security setting. |
`amp_image_tag = ` | string value | Glance image tag for the Amphora image to boot. Use this option to be able to update the image without reconfiguring Octavia. |
`amp_secgroup_list = ` | list value | List of security groups to attach to the Amphora. |
`amp_ssh_key_name = ` | string value | Optional SSH keypair name, in nova, that will be used for the authorized_keys inside the amphora. |
| integer value | Number of times an amphora delete should be retried. |
| integer value | Time, in seconds, between amphora delete retries. |
| string value | Name of the amphora driver to use |
| string value | Client CA for the amphora agent to use |
| string value | Name of the compute driver to use |
| integer value | The number of times the database action will be attempted. |
| integer value | The time to backoff retry attempts. |
| integer value | The initial delay before a retry attempt. |
| integer value | The maximum amount of time to wait between retry attempts. |
| string value | Name of the distributor driver to use |
| string value | Name of the image driver to use |
| string value | Load balancer topology configuration. SINGLE - One amphora per load balancer. ACTIVE_STANDBY - Two amphora per load balancer. |
| string value | Name of the network driver to use |
| list value | List of drivers for updating amphora statistics. Deprecated since: Victoria *Reason:*None |
| boolean value | If True, build cloud-init user-data that is passed to the config drive on Amphora boot instead of personality files. If False, utilize personality files. |
| string value | Name of the volume driver to use |
| integer value | Number of workers for the controller-worker service. |
13.1.9. cors Copy linkLink copied to clipboard!
The following table outlines the options available under the [cors]
group in the /etc/octavia/octavia.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. |
13.1.10. database Copy linkLink copied to clipboard!
The following table outlines the options available under the [database]
group in the /etc/octavia/octavia.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. |
`connection_parameters = ` | string value | Optional URL parameters to append onto the connection URL at connect time; specify as param1=value1¶m2=value2&… |
| 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. |
| 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. |
13.1.11. driver_agent Copy linkLink copied to clipboard!
The following table outlines the options available under the [driver_agent]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
`enabled_provider_agents = ` | list value | List of enabled provider agents. The driver-agent will launch these agents at startup. |
| integer value | Maximum number of concurrent processes to use servicing get requests. |
| integer value | Time, in seconds, to wait for a get request. |
| string value | Path to the driver get unix domain socket file. |
| floating point value | Percentage of max_processes (both status and stats) in use to start logging warning messages about an overloaded driver-agent. |
| integer value | The time, in seconds, to wait for provider agents to shutdown after the exit event has been set. |
| integer value | Maximum number of concurrent processes to use servicing statistics updates. |
| integer value | Time, in seconds, to wait for a statistics update request. |
| string value | Path to the driver statistics unix domain socket file. |
| integer value | Maximum number of concurrent processes to use servicing status updates. |
| integer value | Time, in seconds, to wait for a status update request. |
| string value | Path to the driver status unix domain socket file. |
13.1.12. glance Copy linkLink copied to clipboard!
The following table outlines the options available under the [glance]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | CA certificates file path |
| string value | A new endpoint to override the endpoint in the keystone catalog. |
| string value | Endpoint interface in identity service to use |
| boolean value | Disable certificate validation on SSL connections |
| string value | Region in Identity service catalog to use for communication with the OpenStack services. |
| string value | The name of the glance service in the keystone catalog |
13.1.13. haproxy_amphora Copy linkLink copied to clipboard!
The following table outlines the options available under the [haproxy_amphora]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Retry threshold for connecting to active amphorae. |
| integer value | Retry timeout between connection attempts in seconds for active amphora. |
| integer value | The number of times the database action will be attempted. |
| integer value | The time to backoff retry attempts. |
| integer value | The initial delay before a retry attempt. |
| integer value | The maximum amount of time to wait between retry attempts. |
| string value | Base directory for cert storage. |
| string value | Base directory for amphora files. |
| IP address value | The host IP to bind to |
| port value | The port to bind to |
| integer value | Retry threshold for waiting for a build slot for an amphorae. |
| integer value | Number of amphorae that could be built per controller worker, simultaneously. |
| integer value | Retry timeout between build attempts in seconds. |
| string value | The client certificate to talk to the agent |
| boolean value | Set this to False to disable connection logging. |
| integer value | Retry threshold for connecting to amphorae. |
| integer value | Retry timeout between connection attempts in seconds. |
| integer value | Default connection_limit for listeners, used when setting "-1" or when unsetting connection_limit with the listener API. |
| integer value | Retry threshold for connecting to an amphora in failover. |
| integer value | Retry timeout between connection attempts in seconds for amphora in failover. |
| string value | The full path to haproxy |
| string value | Size of the HAProxy stick table. Accepts k, m, g suffixes. Example: 10k |
| string value | Custom haproxy template. |
| string value | Network interface through which to reach amphora, only required if using IPv6 link local addresses. |
| integer value | The respawn count for haproxy’s upstart script |
| integer value | The respawn interval for haproxy’s upstart script |
| floating point value | The time in seconds to wait for a REST API to connect. |
| floating point value | The time in seconds to wait for a REST API response. |
| string value | The ca which signed the server certificates |
| integer value | Frontend client inactivity timeout. |
| integer value | Backend member connection timeout. |
| integer value | Backend member inactivity timeout. |
| integer value | Time to wait for TCP packets for content inspection. |
| boolean value | If False, use sysvinit. |
| string value | Log format string for user flow logging. |
13.1.14. health_manager Copy linkLink copied to clipboard!
The following table outlines the options available under the [health_manager]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| IP address value | IP address the controller will listen on for heart beats |
| port value | Port number the controller will listen on for heart beats |
| list value | List of controller ip and port pairs for the heartbeat receivers. Example 127.0.0.1:5555, 192.168.0.1:5555 |
| integer value | Number of threads performing amphora failovers. |
| integer value | Sleep time between health checks in seconds. |
| string value | Driver for updating amphora health system. Deprecated since: Victoria *Reason:*This driver interface was removed. |
| integer value | Number of processes for amphora health update. |
| integer value | Sleep time between sending heartbeats. |
| string value | key used to validate amphora sending the message |
| integer value | Interval, in seconds, to wait before failing over an amphora. |
| integer value | sets the value of the heartbeat recv buffer |
| integer value | Number of processes for amphora stats update. |
13.1.15. healthcheck Copy linkLink copied to clipboard!
The following table outlines the options available under the [healthcheck]
group in the /etc/octavia/octavia.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. Security note: Enabling this option may expose sensitive details about the service being monitored. Be sure to verify that it will not violate your security policies. |
| 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. |
13.1.16. house_keeping Copy linkLink copied to clipboard!
The following table outlines the options available under the [house_keeping]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Amphora expiry age in seconds |
| integer value | Seconds until certificate expiration |
| integer value | Certificate check interval in seconds |
| integer value | Number of threads performing amphora certificate rotation |
| integer value | DB cleanup interval in seconds |
| integer value | Load balancer expiry age in seconds |
| integer value | Number of spare amphorae Deprecated since: Victoria *Reason:*Spares Pool support will be removed in the X release. |
| integer value | Spare check interval in seconds Deprecated since: Victoria *Reason:*Spares Pool support will be removed in the X release. |
13.1.17. keepalived_vrrp Copy linkLink copied to clipboard!
The following table outlines the options available under the [keepalived_vrrp]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Amphora role and priority advertisement interval in seconds. |
| integer value | VRRP health check script run interval in seconds. |
| integer value | Number of successive failures before transition to a fail state. |
| integer value | Number of gratuitous ARP announcements to make on each refresh interval. |
| integer value | Time in seconds between gratuitous ARP announcements from the MASTER. |
| integer value | Number of consecutive successes before transition to a success state. |
13.1.18. key_manager Copy linkLink copied to clipboard!
The following table outlines the options available under the [key_manager]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | The type of authentication credential to create. Possible values are token, password, keystone_token, and keystone_password. Required if no context is passed to the credential factory. |
| string value | Use this endpoint to connect to Keystone. |
| string value | Specify the key manager implementation. Options are "barbican" and "vault". Default is "barbican". Will support the values earlier set using [key_manager]/api_class for some time. |
| string value | Domain ID for domain scoping. Optional for keystone_token and keystone_password auth_type. |
| string value | Domain name for domain scoping. Optional for keystone_token and keystone_password auth_type. |
| string value | Password for authentication. Required for password and keystone_password auth_type. |
| string value | Project’s domain ID for project. Optional for keystone_token and keystone_password auth_type. |
| string value | Project’s domain name for project. Optional for keystone_token and keystone_password auth_type. |
| string value | Project ID for project scoping. Optional for keystone_token and keystone_password auth_type. |
| string value | Project name for project scoping. Optional for keystone_token and keystone_password auth_type. |
| boolean value | Allow fetching a new token if the current one is going to expire. Optional for keystone_token and keystone_password auth_type. |
| string value | Token for authentication. Required for token and keystone_token auth_type if no context is passed to the credential factory. |
| string value | Trust ID for trust scoping. Optional for keystone_token and keystone_password auth_type. |
| string value | User’s domain ID for authentication. Optional for keystone_token and keystone_password auth_type. |
| string value | User’s domain name for authentication. Optional for keystone_token and keystone_password auth_type. |
| string value | User ID for authentication. Optional for keystone_token and keystone_password auth_type. |
| string value | Username for authentication. Required for password auth_type. Optional for the keystone_password auth_type. |
13.1.19. keystone_authtoken Copy linkLink copied to clipboard!
The following table outlines the options available under the [keystone_authtoken]
group in the /etc/octavia/octavia.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. Deprecated since: Queens *Reason:*The auth_uri option is deprecated in favor of www_authenticate_uri and will be removed in the S release. |
| string value | API version of the 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 | 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. |
| 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 | Interface to use for the Identity API endpoint. Valid values are "public", "internal" (default) or "admin". |
| 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. |
| 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 | The name or type of the service as it appears in the service catalog. This is used to validate tokens that have restricted access rules. |
| 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. |
13.1.20. networking Copy linkLink copied to clipboard!
The following table outlines the options available under the [networking]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | When True, users can use network resources they cannot normally see as VIP or member subnets. Making this True may allow users to access resources on subnets they do not normally have access to via neutron RBAC policies. |
| boolean value | Can users supply a network_id for their VIP? |
| boolean value | Can users supply a port_id for their VIP? |
| boolean value | Can users supply a subnet_id for their VIP? |
| integer value | The maximum attempts to retry an action with the networking service. |
| integer value | Seconds to wait for a port to detach from an amphora. |
| list value | List of IP addresses reserved from being used for member addresses. IPv6 addresses should be in expanded, uppercase form. |
| integer value | The seconds to backoff retry attempts. |
| integer value | Seconds to wait before retrying an action with the networking service. |
| integer value | The maximum interval in seconds between retry attempts. |
| list value | List of network_ids that are valid for VIP creation. If this field is empty, no validation is performed. |
13.1.21. neutron Copy linkLink copied to clipboard!
The following table outlines the options available under the [neutron]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | CA certificates file path |
| string value | A new endpoint to override the endpoint in the keystone catalog. |
| string value | Endpoint interface in identity service to use |
| boolean value | Disable certificate validation on SSL connections |
| string value | Region in Identity service catalog to use for communication with the OpenStack services. |
| string value | The name of the neutron service in the keystone catalog |
13.1.22. nova Copy linkLink copied to clipboard!
The following table outlines the options available under the [nova]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Sets the anti-affinity policy for nova |
| string value | Availability zone to use for creating Amphorae |
| string value | CA certificates file path |
| boolean value | Flag to indicate if nova anti-affinity feature is turned on. This option is only used when creating amphorae in ACTIVE_STANDBY topology. |
| string value | A new endpoint to override the endpoint in the keystone catalog. |
| string value | Endpoint interface in identity service to use |
| boolean value | Disable certificate validation on SSL connections |
| integer value | If non-zero, generate a random name of the length provided for each amphora, in the format "a[A-Z0-9]*". Otherwise, the default name format will be used: "amphora-{UUID}". |
| string value | Region in Identity service catalog to use for communication with the OpenStack services. |
| string value | The name of the nova service in the keystone catalog |
13.1.23. oslo_messaging Copy linkLink copied to clipboard!
The following table outlines the options available under the [oslo_messaging]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value |
13.1.24. oslo_messaging_amqp Copy linkLink copied to clipboard!
The following table outlines the options available under the [oslo_messaging_amqp]
group in the /etc/octavia/octavia.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 |
| 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 |
| 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. |
13.1.25. oslo_messaging_kafka Copy linkLink copied to clipboard!
The following table outlines the options available under the [oslo_messaging_kafka]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | The compression codec for all data generated by the producer. If not set, compression will not be used. Note that the allowed values of this depend on the kafka version |
| 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 |
| boolean value | Enable asynchronous consumer commits |
| floating point value | Default timeout(s) for Kafka consumers |
| integer value | Max fetch bytes of Kafka consumer |
| integer value | The maximum number of records returned in a poll call |
| 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 |
| string value | Mechanism when security protocol is SASL |
| string value | Protocol used to communicate with brokers |
`ssl_cafile = ` | string value | CA certificate PEM file used to verify the server certificate |
`ssl_client_cert_file = ` | string value | Client certificate PEM file used for authentication. |
`ssl_client_key_file = ` | string value | Client key PEM file used for authentication. |
`ssl_client_key_password = ` | string value | Client key password file used for authentication. |
13.1.26. oslo_messaging_notifications Copy linkLink copied to clipboard!
The following table outlines the options available under the [oslo_messaging_notifications]
group in the /etc/octavia/octavia.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. |
13.1.27. oslo_messaging_rabbit Copy linkLink copied to clipboard!
The following table outlines the options available under the [oslo_messaging_rabbit]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Auto-delete queues in AMQP. |
| boolean value | Use durable queues in AMQP. |
| boolean value | (DEPRECATED) Enable/Disable the RabbitMQ mandatory flag for direct send. The direct send is used as reply, so the MessageUndeliverable exception is raised in case the client queue does not exist.MessageUndeliverable exception will be used to loop for a timeout to lets a chance to sender to recover.This flag is deprecated and it will not be possible to deactivate this functionality anymore |
| boolean value | Enable x-cancel-on-ha-failover flag so that rabbitmq server will cancel and notify consumerswhen queue is down |
| boolean value | Run the health check heartbeat thread through a native python thread by default. If this option is equal to False then the health check heartbeat will inherit the execution model from the parent process. For example if the parent process has monkey patched the stdlib by using eventlet/greenlet then the heartbeat will be run through a green thread. This option should be set to True only for the wsgi services. |
| 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 disables heartbeat). |
| 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. |
| 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"} " |
| integer value | Maximum interval of RabbitMQ connection retries. Default is 30 seconds. |
| string value | The RabbitMQ login method. |
| 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. |
| boolean value | Connect over 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). |
`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. |
13.1.28. oslo_middleware Copy linkLink copied to clipboard!
The following table outlines the options available under the [oslo_middleware]
group in the /etc/octavia/octavia.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. |
13.1.29. oslo_policy Copy linkLink copied to clipboard!
The following table outlines the options available under the [oslo_policy]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value |
This option controls whether or not to use old deprecated defaults when evaluating policies. If |
| 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 relative or absolute path of a file that maps roles to permissions for a given service. Relative paths must be specified in relation to the configuration file setting this option. |
| 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 |
13.1.30. quotas Copy linkLink copied to clipboard!
The following table outlines the options available under the [quotas]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Default per project health monitor quota. |
| integer value | Default per project l7policy quota. |
| integer value | Default per project l7rule quota. |
| integer value | Default per project listener quota. |
| integer value | Default per project load balancer quota. |
| integer value | Default per project member quota. |
| integer value | Default per project pool quota. |
13.1.31. service_auth Copy linkLink copied to clipboard!
The following table outlines the options available under the [service_auth]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Authentication URL |
| string value | Authentication type to load |
| string value | PEM encoded Certificate Authority to use when verifying HTTPs connections. |
| string value | PEM encoded client certificate cert file |
| boolean value | Collect per-API call timing information. |
| string value | 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. |
| string value | 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. |
| string value | Domain ID to scope to |
| string value | Domain name to scope to |
| boolean value | Verify HTTPS connections. |
| string value | PEM encoded client certificate key file |
| string value | User’s password |
| string value | Domain ID containing project |
| string value | Domain name containing project |
| string value | Project ID to scope to |
| string value | Project name to scope to |
| boolean value | Log requests to multiple loggers. |
| string value | Scope for system operations |
| string value | Tenant ID |
| string value | Tenant Name |
| integer value | Timeout value for http requests |
| string value | Trust ID |
| string value | User’s domain id |
| string value | User’s domain name |
| string value | User id |
| string value | Username |
13.1.32. task_flow Copy linkLink copied to clipboard!
The following table outlines the options available under the [task_flow]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | If True, disables the controller worker taskflow flows from reverting. This will leave resources in an inconsistent state and should only be used for debugging purposes. |
| string value | TaskFlow engine to use. serial - Runs all tasks on a single thread. parallel - Schedules tasks onto different threads to allow for running non-dependent tasks simultaneously |
| string value | Jobboard backend driver that will monitor job state. |
| list value | Jobboard backend server host(s). |
| string value | Jobboard name that should be used to store taskflow job id and claims for it. |
`jobboard_backend_password = ` | string value | Jobboard backend server password |
| port value | Jobboard backend server port |
| boolean value | If True, enables TaskFlow jobboard. |
| integer value | For backends like redis claiming jobs requiring setting the expiry - how many seconds the claim should be retained for. |
| dict value | Redis jobboard backend ssl configuration options. |
| string value | Sentinel name if it is used for Redis. |
| boolean value | If for analysis required saving logbooks info, set this parameter to True. By default remove logbook from persistence backend when job completed. |
| dict value | Zookeeper jobboard backend ssl configuration options. |
| integer value | The maximum number of workers |
| string value | Persistence database, which will be used to store tasks states. Database connection url with db name |
13.1.33. vault Copy linkLink copied to clipboard!
The following table outlines the options available under the [vault]
group in the /etc/octavia/octavia.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | AppRole role_id for authentication with vault |
| string value | AppRole secret_id for authentication with vault |
| string value | Mountpoint of KV store in Vault to use, for example: secret |
| integer value | Version of KV store in Vault to use, for example: 2 |
| string value | root token for vault |
| string value | Absolute path to ca cert file |
| boolean value | SSL Enabled/Disabled |
| string value | Use this endpoint to connect to Vault, for example: "http://127.0.0.1:8200" |