You can update certain parameters in your Heat service configuration by using the viocli update heat command.

For more information about Heat configuration, see the OpenStack Heat Configuration documentation.

Configuration options example using viocli update heat. 
conf:
  heat:
    DEFAULT:
      max_resources_per_stack: 1000
      max_stacks_per_tenant: 100
      event_purge_batch_size: 200
      max_events_per_stack: 1000
      encrypt_parameters_and_properties: false
      max_nested_stack_depth: 5
      max_interface_check_attempts: 60
      convergence_engine: true
      observe_on_update: false
      max_template_size: 524288
      stack_action_timeout: 3600
      max_pool_size: 5
      max_overflow: 50
      rpc_response_timeout: 60
      client_retry_limit: 2

You can also update heat parameters in a non-interactive mode as given in the following example:

kubectl -n openstack patch heat heat1 --type=merge --patch '{"spec":{"conf":{"heat":{"DEFAULT":{"rpc_response_timeout":360}}}}}'

Updating heat parameters in a non-interactive mode yields the same result as the viocli update heat command.

Table 1. viocli update Heat Parameters
Parameter Default Value Description

max_resources_per_stack

 1000

Enter the maximum number of resources that a heat stack can use.

max_stacks_per_tenant

 100

Enter the maximum number of heat stacks that each project can create.

event_purge_batch_size

 200

Enter the size of the stack events purged.

max_events_per_stack

 1000

Enter the number of maximum events that are available per stack.

encrypt_parameters_and_properties

 false

Encrypt template parameters that are marked as hidden and also all the resource properties before storing them in database.

max_nested_stack_depth

 5

Enter the maximum number of times to check whether an interface has been attached or detached.

max_interface_check_attempts

 10

Enter the number of times to check whether an interface has been attached or detached

convergence_engine

 true

This option enables the engine with convergence architecture.

observe_on_update

 false

On update enables heat to collect existing resource properties from reality and converge to updated template

max_template_size

 524288

Enter the maximum file size in bytes of a heat template.

stack_action_timeout

 3600

Enter the timeout in seconds for heat stack actions.

max_pool_size

 5

Enter the maximum number of SQL connections to keep open in a pool.

max_overflow

 50

If set, enter the maximum value with SQLAlchemy.

rpc_response_timeout

 60

Enter the seconds to wait for a response from a call.

client_retry_limit

 2

Enter the number of times to retry when a client encounters an expected intermittent error.