zuul/nodepool
Code Issues Proposed changes

Docs: Correct availability-zones documentation.

Browse Source 
Change-Id: I0395087d66acb3541d6ea24d89cb50583e14ce34
This commit is contained in:
David Shrewsbury 2017-03-23 09:29:45 -04:00
parent 6da49fe732
commit 9fcee45482
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/configuration.rst
View File

@ -367,11 +367,12 @@ Example::
``availability-zones`` (list)
Without it nodepool will rely on nova to schedule an availability zone.
If it is provided the value should be a list of availability zone names.
Nodepool will select one at random and provide that to nova. This should
give a good distribution of availability zones being used. If you need more
control of the distribution you can use multiple logical providers each
providing a different list of availabiltiy zones.
If it is provided, the value should be a list of availability zone names.
If you have more than one availability zone, you should specify them all
here, rather than letting one get selected by nova. By doing so, you allow
nodepool to group all nodes allocated for a node request into the same
zone, which will be selected at random from the list. If you do not list
your zones here, this grouping cannot be guaranteed.
``networks`` (list)
Specify custom Neutron networks that get attached to each