From 22631727b937c94e1a819e51a25641c155615ed7 Mon Sep 17 00:00:00 2001 From: melanie witt Date: Fri, 27 May 2022 19:57:02 +0000 Subject: [PATCH] Update [scheduler] limit_tenants_to_placement_aggregate config help Currently the config option help for [scheduler] limit_tenants_to_placement_aggregate says that if no host aggregates matching the tenant id are found, the result will be the same as finding no suitable hosts for scheduling. This is only accurate if [scheduler] placement_aggregate_required_for_tenants = True. This updates the config option help to add detail about the behavior depending on the [scheduler] placement_aggregate_required_for_tenants setting. Change-Id: I1388c39fd84aff18813b47bb002589f2b5059e2a --- nova/conf/scheduler.py | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/nova/conf/scheduler.py b/nova/conf/scheduler.py index 8b3b61698738..6eef902b5f3e 100644 --- a/nova/conf/scheduler.py +++ b/nova/conf/scheduler.py @@ -114,9 +114,15 @@ request, and request results from placement be limited to that aggregate. Multiple tenants may be added to a single aggregate by appending a serial number to the key, such as ``filter_tenant_id:123``. -The matching aggregate UUID must be mirrored in placement for proper -operation. If no host aggregate with the tenant id is found, or that -aggregate does not match one in placement, the result will be the same +The matching aggregate UUID must be mirrored in placement for proper operation. +If the aggregate does not match one in placement, the result will be the same +as not finding any suitable hosts for the request. + +If no host aggregate with the tenant id is found and ``[scheduler] +placement_aggregate_required_for_tenants = False``, the request will not be +restricted to only aggregates matching the tenant. If no host aggregate with +the tenant id is found and ``[scheduler] +placement_aggregate_required_for_tenants = True``, the result will be the same as not finding any suitable hosts for the request. Possible values: