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.3 KiB
2.3 KiB
| Configuration option = Default value | Description |
|---|---|
|
(String) Compute RPC API version cap. By default, we always send messages using the most recent version the client knows about. Where you have old and new compute services running, you should set this to the lowest deployed version. This is to guarantee that all services never send messages that one of the compute nodes can't understand. Note that we only support upgrading from release N to release N+1. Set this option to "auto" if you want to let the compute RPC module automatically determine what version to use based on the service versions in the deployment. Possible values:
|
network = None |
(String) Network RPC API version cap |
conductor = None |
(String) Conductor RPC API version cap |
cells = None |
(String) Cells RPC API version cap |
cert = None |
(String) Cert RPC API version cap |
scheduler = None |
(String) Scheduler RPC API version cap |
intercell = None |
(String) Intercell RPC API version cap |
console = None |
(String) Console RPC API version cap |
consoleauth = None |
(String) Consoleauth RPC API version cap |
baseapi = None |
(String) Base API RPC API version cap |