cleanup: reduce configuration vars

Code Issues Proposed changes

This patch reduces the number of configuration defaults that we
ship with no functional changes for users that were not overriding
them.
Change-Id: Iec7e7b0ca13e2503344d23095c0f1c30b46bb702

This commit is contained in:

Mohammed Naser

2019年08月14日 21:43:12 -04:00

parent ecfedcb0b8

commit 3d99b2bd80

4 changed files with 48 additions and 91 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

12
doc/source/configure-nova.rst

View File

@@ -10,10 +10,10 @@ Availability zones

~~~~~~~~~~~~~~~~~~

Deployers with multiple availability zones can set the

``nova_default_schedule_zone`` Ansible variable to specify an availability zone

for new requests. This is useful in environments with different types

of hypervisors, where builds are sent to certain hardware types based on

their resource requirements.

``nova_nova_conf_overrides.DEFAULT.default_schedule_zone`` Ansible

variable to specify an availability zone for new requests. This is useful

in environments with different types of hypervisors, where builds are sent

to certain hardware types based on their resource requirements.

For example, if you have servers running on two racks without sharing the PDU.

These two racks can be grouped into two availability zones.

@@ -93,7 +93,9 @@ with every virtual machine:

.. code-block:: yaml

nova_force_config_drive:True

nova_nova_conf_overrides:

DEFAULT:

force_config_drive:True

Certain formats of config drives can prevent instances from migrating properly

between hypervisors. If you need forced config drives and the ability

cleanup: reduce configuration vars

12 doc/source/configure-nova.rst Unescape Escape View File

12
doc/source/configure-nova.rst

View File