This significant rework occurs due to recent changes in the openstack-doc-tools project. There are some manual fixes to the following options, where invalid rST was included. These have been fixed on nova master but still need to be backported to stable/ocata. This will be done separately. - block_device_allocate_retries_interval (DEFAULT) - torrent_images (xenserver) Change-Id: Ia6ecbf025f1a2de19db896d3d72412461603093b Depends-On: I4ef80825598cc7d98a4046afd5b131484e5a3469
8.9 KiB
| Configuration option = Default value | Description |
|---|---|
max_limit = 1000 |
(Integer) As a query can potentially return many thousands of items, you can limit the maximum number of items in a single response by setting this option. |
|
(Integer) Maximum wait time for an external REST service to return data once connected. Possible values:
Related options:
|
|
(String) Path to an optional certificate file or CA bundle to verify dynamic vendordata REST services ssl certificates against. Possible values:
Related options:
|
|
(String) Tenant ID for getting the default network from Neutron API (also referred in some places as the 'project ID') to use. Related options:
|
|
(String) When gathering the existing metadata for a config drive, the EC2-style metadata is returned for all versions that don't appear in this option. As of the Liberty release, the available versions are:
The option is in the format of a single string, with each version separated by a space. Possible values:
|
|
(List) This option is a list of all instance states for which network address information should not be returned from the API. Possible values:
|
|
(Integer) Maximum wait time for an external REST service to connect. Possible values:
Related options:
|
fping_path = /usr/sbin/fping |
(String) The full path to the fping binary. |
allow_instance_snapshots = True |
(Boolean) Operators can turn off the ability for a user to take snapshots of their instances by setting this option to False. When disabled, any attempt to take a snapshot will result in a HTTP 400 response ("Bad Request"). |
|
(String) This string is prepended to the normal URL that is returned in links to the OpenStack Compute API. If it is empty (the default), the URLs are returned unchanged. Possible values:
|
|
(String) Cloud providers may store custom data in vendor data file that will then be available to the instances via the metadata service, and to the rendering of config-drive. The default class for this, JsonFileVendorData, loads this information from a JSON file, whose path is configured by this option. If there is no path set by this option, the class returns an empty dictionary. Possible values:
|
|
(String) This string is prepended to the normal URL that is returned in links to Glance resources. If it is empty (the default), the URLs are returned unchanged. Possible values:
|
enable_instance_password = True |
(Boolean) Enables returning of the instance password by the relevant server API calls such as create, rebuild, evacuate, or rescue. If the hypervisor does not support password injection, then the password returned will not be correct, so if your hypervisor does not support password injection, set this to False. |
|
(List) A list of targets for the dynamic vendordata provider. These targets are of the form <name>@<url>. The dynamic vendordata provider collects metadata by contacting external REST services and querying them for information about the instance. This behaviour is documented in the vendordata.rst file in the nova developer reference. |
|
(Boolean) When True, the 'X-Forwarded-For' header is treated as the canonical remote address. When False (the default), the 'remote_address' header is used. You should only enable this if you have an HTML sanitizing proxy. |
|
(Boolean) When True, the TenantNetworkController will query the Neutron API to get the default networks to use. Related options:
|
|
(Boolean) Should failures to fetch dynamic vendordata be fatal to instance boot? Related options:
|
|
(List) A list of vendordata providers. vendordata providers are how deployers can provide metadata via configdrive and metadata that is specific to their deployment. There are currently two supported providers: StaticJSON and DynamicJSON. StaticJSON reads a JSON file configured by the flag vendordata_jsonfile_path and places the JSON from that file into vendor_data.json and vendor_data2.json. DynamicJSON is configured via the vendordata_dynamic_targets flag, which is documented separately. For each of the endpoints specified in that flag, a section is added to the vendor_data2.json. For more information on the requirements for implementing a vendordata dynamic endpoint, please see the vendordata.rst file in the nova developer reference. Possible values:
Related options:
|
metadata_cache_expiration = 15 |
(Integer) This option is the time (in seconds) to cache metadata. When set to 0, metadata caching is disabled entirely; this is generally not recommended for performance reasons. Increasing this setting should improve response times of the metadata API when under heavy load. Higher values may increase memory usage, and result in longer times for host metadata changes to take effect. |
auth_strategy = keystone |
(String) This determines the strategy to use for authentication: keystone or noauth2. 'noauth2' is designed for testing only, as it does no actual credential checking. 'noauth2' provides administrative credentials only if 'admin' is specified as the username. |