openstack-manuals/doc/common/tables/heat-common.xml

62 lines
2.5 KiB
XML

<?xml version='1.0' encoding='UTF-8'?>
<para xmlns="http://docbook.org/ns/docbook" version="5.0">
<!-- Warning: Do not edit this file. It is automatically
generated and your changes will be overwritten.
The tool to do so lives in openstack-doc-tools repository. -->
<table rules="all" xml:id="config_table_heat_common">
<caption>Description of configuration options for common</caption>
<col width="50%"/>
<col width="50%"/>
<thead>
<tr>
<th>Configuration option = Default value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<th colspan="2">[DEFAULT]</th>
</tr>
<tr>
<td>deferred_auth_method = password</td>
<td>(StrOpt) Select deferred auth method, stored password or trusts.</td>
</tr>
<tr>
<td>environment_dir = /etc/heat/environment.d</td>
<td>(StrOpt) The directory to search for environment files.</td>
</tr>
<tr>
<td>event_purge_batch_size = 10</td>
<td>(IntOpt) Controls how many events will be pruned whenever a stack's events exceed max_events_per_stack. Set this lower to keep more events at the expense of more frequent purges.</td>
</tr>
<tr>
<td>instance_driver = heat.engine.nova</td>
<td>(StrOpt) Driver to use for controlling instances.</td>
</tr>
<tr>
<td>instance_user = ec2-user</td>
<td>(StrOpt) The default user for new instances. This option is deprecated and will be removed in the Juno release. If it's empty, Heat will use the default user set up with your cloud image (for OS::Nova::Server) or 'ec2-user' (for AWS::EC2::Instance).</td>
</tr>
<tr>
<td>keystone_backend = heat.common.heat_keystoneclient.KeystoneClientV3</td>
<td>(StrOpt) Fully qualified class name to use as a keystone backend.</td>
</tr>
<tr>
<td>periodic_interval = 60</td>
<td>(IntOpt) Seconds between running periodic tasks.</td>
</tr>
<tr>
<td>plugin_dirs = /usr/lib64/heat, /usr/lib/heat</td>
<td>(ListOpt) List of directories to search for plug-ins.</td>
</tr>
<tr>
<th colspan="2">[revision]</th>
</tr>
<tr>
<td>heat_revision = unknown</td>
<td>(StrOpt) 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.</td>
</tr>
</tbody>
</table>
</para>