You can modify certain parameters in your Heat configuration by using viocli update heat or the Kubernetes kubectl command-line utility.
conf:
heat:
DEFAULT:
max_stacks_per_tenant: 150
max_interface_check_attempts: 220
Configuration example using kubectl.
kubectl -n openstack patch heat heat1 --type=merge --patch '{"spec":{"conf":{"heat":{"DEFAULT":{"max_interface_check_attempts":220}}}}}
| Parameter | Default Value | Description |
|---|---|---|
| cron_purge_enabled |
|
Enter |
| purge_age_type |
|
|
| purge_age |
|
|
| purge_cron_time |
|
|
| max_resources_per_stack |
|
Enter the maximum number of resources that a Heat stack can use. |
| max_stacks_per_tenant |
|
Enter the maximum number of Heat stacks that each project can create. |
| event_purge_batch_size |
|
|
| max_events_per_stack |
|
|
| encrypt_parameters_and_properties |
|
|
| max_nested_stack_depth |
|
|
| max_interface_check_attempts |
|
|
| convergence_engine |
|
Enter |
| observe_on_update |
|
|
| max_template_size |
|
Enter the maximum file size (in bytes) of a Heat template. |
| stack_action_timeout |
|
Enter the timeout (in seconds) for Heat stack actions. |
| max_pool_size |
|
Enter the maximum number of SQL connections to keep open in a pool. If you enter |
| max_overflow |
|
|
| rpc_response_timeout |
Enter the time (in seconds) to wait for a response to an RPC. |