Chapter 4. heat
The following chapter contains information about the configuration options in the heat
service.
4.1. heat.conf
This section contains options for the /etc/heat/heat.conf
file.
4.1.1. DEFAULT
The following table outlines the options available under the [DEFAULT]
group in the /etc/heat/heat.conf
file.
.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Number of times to retry to bring a resource to a non-error state. Set to 0 to disable retries. |
| boolean value | Create trusts with redelegation enabled. This option is only used when reauthentication_auth_method is set to "trusts". Note that enabling this option does have security implications as all trusts created by Heat will use both impersonation and redelegation enabled. Enable it only when there are other services that need to create trusts from tokens Heat uses to access them, examples are Aodh and Heat in another region when configured to use trusts too. |
| string value | Key used to encrypt authentication info in the database. Length of this key must be 32 characters. |
| 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. Inside the path {pid} will be replaced with the PID of the current process. |
| integer value | Number of times to retry when a client encounters an expected intermittent error. Set to 0 to disable retries. |
| string value | Fully qualified class name to use as a client backend. |
| 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 | Enables engine with convergence architecture. All stacks with this option will be created using convergence engine. |
| boolean value | If set to true, the logging level will be set to DEBUG instead of the default INFO level. |
| string value | Template default for how the server should signal to heat with the deployment output values. CFN_SIGNAL will allow an HTTP POST to a CFN keypair signed URL (requires enabled heat-api-cfn). TEMP_URL_SIGNAL will create a Swift TempURL to be signaled via HTTP PUT (requires object-store endpoint which supports TempURL). HEAT_SIGNAL will allow calls to the Heat API resource-signal using the provided keystone credentials. ZAQAR_SIGNAL will create a dedicated zaqar queue to be signaled using the provided keystone credentials. |
| list value | List of package logging levels in logger=LEVEL pairs. This option is ignored if log_config_append is set. |
| string value | Default notification level for outgoing notifications. |
| string value | Default publisher_id for outgoing notifications. |
| string value | Template default for how the server should receive the metadata required for software configuration. POLL_SERVER_CFN will allow calls to the cfn API action DescribeStackResource authenticated with the provided keypair (requires enabled heat-api-cfn). POLL_SERVER_HEAT will allow calls to the Heat API resource-show using the provided keystone credentials (requires keystone v3 API, and configured stack_user_* config options). POLL_TEMP_URL will create and populate a Swift TempURL with metadata for polling (requires object-store endpoint which supports TempURL).ZAQAR_MESSAGE will create a dedicated zaqar queue and post the metadata for polling. |
| string value | Template default for how the user_data should be formatted for the server. For HEAT_CFNTOOLS, the user_data is bundled as part of the heat-cfntools cloud-init boot configuration data. For RAW the user_data is passed to Nova unmodified. For SOFTWARE_CONFIG user_data is bundled as part of the software config data, and metadata is derived from any associated SoftwareDeployment resources. |
| string value | Select deferred auth method, stored password or trusts. Deprecated since: 9.0.0 *Reason:*Stored password based deferred auth is broken when used with keystone v3 and is not supported. |
| boolean value | Enable the legacy OS::Heat::CWLiteAlarm resource. Deprecated since: 10.0.0 *Reason:*Heat CloudWatch Service has been removed. |
| boolean value | Enable the preview Stack Abandon feature. |
| boolean value | Enable the preview Stack Adopt feature. |
| boolean value | Encrypt template parameters that were marked as hidden and also all the resource properties before storing them in database. |
| integer value | RPC timeout for the engine liveness check that is used for stack locking. |
| string value | The directory to search for environment files. |
| integer value | The amount of time in seconds after an error has occurred that tasks may continue to run before being cancelled. |
| integer value | Controls how many events will be pruned whenever a stack’s events are purged. Set this lower to keep more events at the expense of more frequent purges. |
| 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 | URL of the Heat metadata server. NOTE: Setting this is only needed if you require instances to use a different endpoint than in the keystone catalog |
| string value | Keystone role for heat template-defined users. |
| string value | URL of the Heat waitcondition server. |
`heat_watch_server_url = ` | string value | URL of the Heat CloudWatch server. Deprecated since: 10.0.0 *Reason:*Heat CloudWatch Service has been removed. |
| list value | Stacks containing these tag names will be hidden. Multiple tags should be given in a comma-delimited list (eg. hidden_stack_tags=hide_me,me_too). |
| string value | Name of the engine node. This can be an opaque identifier. It is not necessarily a hostname, FQDN, or IP address. |
| string value | Instance connection to CFN/CW API validate certs if SSL is used. |
| string value | Instance connection to CFN/CW API via https. |
`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 | Fully qualified class name to use as a keystone backend. |
| string value | Custom template for the built-in loadbalancer nested stack. |
| 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 | Rough number of maximum events that will be available per stack. Actual number of events can be a bit higher since purge checks take place randomly 200/event_purge_batch_size percent of the time. Older events are deleted when events are purged. Set to 0 for unlimited events per stack. |
| integer value | Number of times to check whether an interface has been attached or detached. |
| integer value | Maximum raw byte size of JSON request body. Should be larger than max_template_size. |
| 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". |
| integer value | Maximum depth allowed when using nested stacks. |
| floating point value | Maximum nova API version for client plugin. With this limitation, any nova feature supported with microversion number above max_nova_api_microversion will not be available. |
| integer value | Maximum resources allowed per top-level stack. -1 stands for unlimited. |
| integer value | Maximum length of a server name to be used in nova. |
| integer value | Maximum number of stacks any one tenant may have active at one time. |
| integer value | Maximum raw byte size of any template. |
| integer value | Number of heat-engine processes to fork and run. Will default to either to 4 or number of CPUs on the host, whichever is greater. |
| boolean value | On update, enables heat to collect existing resource properties from reality and converge to updated template. |
| string value | Deprecated. |
| integer value | Seconds between running periodic tasks. |
| list value | List of directories to search for plug-ins. |
| 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. |
`reauthentication_auth_method = ` | string value | Allow reauthentication on token expiry, such that long-running tasks may complete. Note this defeats the expiry of any provided user tokens. |
| string value | Default region name used to get services endpoints. |
| integer value | Size of RPC connection pool. |
| integer value | Seconds to wait for a response from a call. |
| boolean value | Some periodic tasks can be run in a separate process. Should we run them here? |
`server_keystone_endpoint_type = ` | string value | If set, is used to control which authentication endpoint is used by user-controlled servers to make calls back to Heat. If unset www_authenticate_uri is used. |
| integer value | Timeout in seconds for stack action (ie. create or update). |
| string value | Keystone username, a user with roles sufficient to manage users and projects in the stack_user_domain. |
| string value | Keystone password for stack_domain_admin user. |
| boolean value | When this feature is enabled, scheduler hints identifying the heat stack context of a server or volume resource are passed to the configured schedulers in nova and cinder, for creates done using heat resource types OS::Cinder::Volume, OS::Nova::Server, and AWS::EC2::Instance. heat_root_stack_id will be set to the id of the root stack of the resource, heat_stack_id will be set to the id of the resource’s parent stack, heat_stack_name will be set to the name of the resource’s parent stack, heat_path_in_stack will be set to a list of comma delimited strings of stackresourcename and stackname with list[0] being rootstackname, heat_resource_name will be set to the resource’s name, and heat_resource_uuid will be set to the resource’s orchestration id. |
| string value | Keystone domain ID which contains heat template-defined users. If this option is set, stack_user_domain_name option will be ignored. |
| string value |
Keystone domain name which contains heat template-defined users. If |
| string value | Syslog facility to receive log lines. This option is ignored if log_config_append is set. |
| string value | The directory to search for template files. |
| 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 |
| list value | Subset of trustor roles to be delegated to heat. If left unset, all roles of a user will be delegated to heat when creating a stack. |
| 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. |
4.1.2. auth_password
The following table outlines the options available under the [auth_password]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| list value | Allowed keystone endpoints for auth_uri when multi_cloud is enabled. At least one endpoint needs to be specified. |
| boolean value | Allow orchestration of multiple clouds. |
4.1.3. clients
The following table outlines the options available under the [clients]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.4. clients_aodh
The following table outlines the options available under the [clients_aodh]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.5. clients_barbican
The following table outlines the options available under the [clients_barbican]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.6. clients_cinder
The following table outlines the options available under the [clients_cinder]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | Allow client’s debug log output. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.7. clients_designate
The following table outlines the options available under the [clients_designate]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.8. clients_glance
The following table outlines the options available under the [clients_glance]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.9. clients_heat
The following table outlines the options available under the [clients_heat]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
`url = ` | string value | Optional heat url in format like http://0.0.0.0:8004/v1/%(tenant_id)s. |
4.1.10. clients_keystone
The following table outlines the options available under the [clients_keystone]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
`auth_uri = ` | string value | Unversioned keystone url in format like http://0.0.0.0:5000. |
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.11. clients_magnum
The following table outlines the options available under the [clients_magnum]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.12. clients_manila
The following table outlines the options available under the [clients_manila]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.13. clients_mistral
The following table outlines the options available under the [clients_mistral]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.14. clients_monasca
The following table outlines the options available under the [clients_monasca]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.15. clients_neutron
The following table outlines the options available under the [clients_neutron]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.16. clients_nova
The following table outlines the options available under the [clients_nova]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | Allow client’s debug log output. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.17. clients_octavia
The following table outlines the options available under the [clients_octavia]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.18. clients_sahara
The following table outlines the options available under the [clients_sahara]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.19. clients_senlin
The following table outlines the options available under the [clients_senlin]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.20. clients_swift
The following table outlines the options available under the [clients_swift]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.21. clients_trove
The following table outlines the options available under the [clients_trove]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.22. clients_zaqar
The following table outlines the options available under the [clients_zaqar]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| string value | Type of endpoint in Identity service catalog to use for communication with the OpenStack service. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
4.1.23. cors
The following table outlines the options available under the [cors]
group in the /etc/heat/heat.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.24. database
The following table outlines the options available under the [database]
group in the /etc/heat/heat.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. |
4.1.25. ec2authtoken
The following table outlines the options available under the [ec2authtoken]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| list value | Allowed keystone endpoints for auth_uri when multi_cloud is enabled. At least one endpoint needs to be specified. |
| string value | Authentication Endpoint URI. |
| string value | Optional CA cert file to use in SSL connections. |
| string value | Optional PEM-formatted certificate chain file. |
| boolean value | If set, then the server’s certificate will not be verified. |
| string value | Optional PEM-formatted file that contains the private key. |
| boolean value | Allow orchestration of multiple clouds. |
4.1.26. eventlet_opts
The following table outlines the options available under the [eventlet_opts]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Timeout for client connections' socket operations. If an incoming connection is idle for this number of seconds it will be closed. A value of 0 means wait forever. |
| boolean value | If False, closes the client socket connection explicitly. |
4.1.27. healthcheck
The following table outlines the options available under the [healthcheck]
group in the /etc/heat/heat.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. |
4.1.28. heat_api
The following table outlines the options available under the [heat_api]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Number of backlog requests to configure the socket with. |
| IP address value | Address to bind the server. Useful when selecting a particular network interface. |
| port value | The port on which the server will listen. |
| string value | Location of the SSL certificate file to use for SSL mode. |
| string value | Location of the SSL key file to use for enabling SSL mode. |
| 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). |
| integer value | The value for the socket option TCP_KEEPIDLE. This is the time in seconds that the connection must be idle before TCP starts sending keepalive probes. |
| integer value | Number of workers for Heat service. Default value 0 means, that service will start number of workers equal number of cores on server. |
4.1.29. heat_api_cfn
The following table outlines the options available under the [heat_api_cfn]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Number of backlog requests to configure the socket with. |
| IP address value | Address to bind the server. Useful when selecting a particular network interface. |
| port value | The port on which the server will listen. |
| string value | Location of the SSL certificate file to use for SSL mode. |
| string value | Location of the SSL key file to use for enabling SSL mode. |
| 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). |
| integer value | The value for the socket option TCP_KEEPIDLE. This is the time in seconds that the connection must be idle before TCP starts sending keepalive probes. |
| integer value | Number of workers for Heat service. |
4.1.30. heat_api_cloudwatch
The following table outlines the options available under the [heat_api_cloudwatch]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Number of backlog requests to configure the socket with. Deprecated since: 10.0.0 *Reason:*Heat CloudWatch API has been removed. |
| IP address value | Address to bind the server. Useful when selecting a particular network interface. Deprecated since: 10.0.0 *Reason:*Heat CloudWatch API has been removed. |
| port value | The port on which the server will listen. Deprecated since: 10.0.0 *Reason:*Heat CloudWatch API has been removed. |
| string value | Location of the SSL certificate file to use for SSL mode. Deprecated since: 10.0.0 *Reason:*Heat CloudWatch API has been Removed. |
| string value | Location of the SSL key file to use for enabling SSL mode. Deprecated since: 10.0.0 *Reason:*Heat CloudWatch API has been Removed. |
| 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.) Deprecated since: 10.0.0 *Reason:*Heat CloudWatch API has been Removed. |
| integer value | The value for the socket option TCP_KEEPIDLE. This is the time in seconds that the connection must be idle before TCP starts sending keepalive probes. Deprecated since: 10.0.0 *Reason:*Heat CloudWatch API has been Removed. |
| integer value | Number of workers for Heat service. Deprecated since: 10.0.0 *Reason:*Heat CloudWatch API has been Removed. |
4.1.31. keystone_authtoken
The following table outlines the options available under the [keystone_authtoken]
group in the /etc/heat/heat.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" or "admin"(default). |
| 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. |
4.1.32. noauth
The following table outlines the options available under the [noauth]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
`token_response = ` | string value | JSON file containing the content returned by the noauth middleware. |
4.1.33. oslo_messaging_amqp
The following table outlines the options available under the [oslo_messaging_amqp]
group in the /etc/heat/heat.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. |
4.1.34. oslo_messaging_kafka
The following table outlines the options available under the [oslo_messaging_kafka]
group in the /etc/heat/heat.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 |
4.1.35. oslo_messaging_notifications
The following table outlines the options available under the [oslo_messaging_notifications]
group in the /etc/heat/heat.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.36. oslo_messaging_rabbit
The following table outlines the options available under the [oslo_messaging_rabbit]
group in the /etc/heat/heat.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 | EXPERIMENTAL: Run the health check heartbeat threadthrough a native python thread. By default if thisoption isn’t provided the health check heartbeat willinherit the execution model from the parent process. Byexample if the parent process have monkey patched thestdlib by using eventlet/greenlet then the heartbeatwill be run through a green thread. |
| 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. |
4.1.37. oslo_middleware
The following table outlines the options available under the [oslo_middleware]
group in the /etc/heat/heat.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.38. oslo_policy
The following table outlines the options available under the [oslo_policy]
group in the /etc/heat/heat.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 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 |
4.1.39. paste_deploy
The following table outlines the options available under the [paste_deploy]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | The API paste config file to use. |
| string value | The flavor to use. |
4.1.40. profiler
The following table outlines the options available under the [profiler]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Connection string for a notifier backend.
Default value is Examples of possible values:
|
| boolean value | Enable the profiling for all services on this node. Default value is False (fully disable the profiling feature). Possible values:
|
| string value | Document type for notification indexing in elasticsearch. |
| integer value | Elasticsearch splits large requests in batches. This parameter defines maximum size of each batch (for example: es_scroll_size=10000). |
| string value | This parameter is a time value parameter (for example: es_scroll_time=2m), indicating for how long the nodes that participate in the search will maintain relevant resources in order to continue and support it. |
| boolean value | Enable filter traces that contain error/exception to a separated place. Default value is set to False. Possible values:
|
| string value | Secret key(s) to use for encrypting context data for performance profiling. This string value should have the following format: <key1>[,<key2>,…<keyn>], where each key is some random string. A user who triggers the profiling via the REST API has to set one of these keys in the headers of the REST API call to include profiling results of this node for this particular project. Both "enabled" flag and "hmac_keys" config options should be set to enable profiling. Also, to generate correct profiling information across all services at least one key needs to be consistent between OpenStack projects. This ensures it can be used from client side to generate the trace, containing information from all possible resources. |
| string value |
Redissentinel uses a service name to identify a master redis service. This parameter defines the name (for example: |
| floating point value | Redissentinel provides a timeout option on the connections. This parameter defines that timeout (for example: socket_timeout=0.1). |
| boolean value | Enable SQL requests profiling in services. Default value is False (SQL requests won’t be traced). Possible values:
|
4.1.41. revision
The following table outlines the options available under the [revision]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Heat build revision. If you would prefer to manage your build revision separately, you can move this section to a different file and add it as another config option. |
4.1.42. ssl
The following table outlines the options available under the [ssl]
group in the /etc/heat/heat.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.43. trustee
The following table outlines the options available under the [trustee]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Authentication URL |
| string value | Config Section from which to load plugin specific options |
| string value | Authentication type to load |
| 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 |
| 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 |
| string value | Scope for system operations |
| string value | Trust ID |
| string value | User’s domain id |
| string value | User’s domain name |
| string value | User id |
| string value | Username |
4.1.44. volumes
The following table outlines the options available under the [volumes]
group in the /etc/heat/heat.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Indicate if cinder-backup service is enabled. This is a temporary workaround until cinder-backup service becomes discoverable, see LP#1334856. |