564f5330c3
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
2.1 KiB
| Configuration option = Default value | Description |
|---|---|
auth_type = None |
(Unknown) Authentication type to load |
|
(Boolean) When True, if sending a user token to an REST API, also send a service token. Nova often reuses the user token provided to the nova-api to talk to other REST APIs, such as Cinder and Neutron. It is possible that while the user token was valid when the request was made to Nova, the token may expire before it reaches the other service. To avoid any failures, and to make it clear it is Nova calling the service on the users behalf, we include a server token along with the user token. Should the user's token have expired, a valid service token ensures the REST API request will still be accepted by the keystone middleware. This feature is currently experimental, and as such is turned off by default while full testing and performance tuning of this feature is completed. |
certfile = None |
(String) PEM encoded client certificate cert file |
keyfile = None |
(String) PEM encoded client certificate key file |
insecure = False |
(Boolean) Verify HTTPS connections. |
timeout = None |
(Integer) Timeout value for http requests |
cafile = None |
(String) PEM encoded Certificate Authority to use when verifying HTTPs connections. |
auth_section = None |
(Unknown) Config Section from which to load plugin specific options |