Fix nits in allocation candidate limit handling
In the review for I5f3d4f49c34fd3cd6b9d2e12b3c3c4cdcb409bec some non-blocking issues were identified. They are fixed here: * inconsistent indentation in configuration setting * creation of a uuid tracking set in the wrong block Change-Id: I848d60f9a5d66cae584279f99a50b9e871540baf
This commit is contained in:
@@ -50,9 +50,10 @@ Possible values:
|
||||
Endpoint interface for this node. This is used when picking the URL in the
|
||||
service catalog.
|
||||
"""),
|
||||
cfg.BoolOpt('randomize_allocation_candidates',
|
||||
default=False,
|
||||
help="""
|
||||
cfg.BoolOpt(
|
||||
'randomize_allocation_candidates',
|
||||
default=False,
|
||||
help="""
|
||||
If True, when limiting allocation candidate results, the results will be
|
||||
a random sampling of the full result set. If False, allocation candidates
|
||||
are returned in a deterministic but undefined order. That is, all things
|
||||
|
||||
Reference in New Issue
Block a user