diff options
Diffstat (limited to 'doc/source/admin/availability-zones.rst')
| -rw-r--r-- | doc/source/admin/availability-zones.rst | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/doc/source/admin/availability-zones.rst b/doc/source/admin/availability-zones.rst index 95cc44e10c..678aff2c5a 100644 --- a/doc/source/admin/availability-zones.rst +++ b/doc/source/admin/availability-zones.rst @@ -65,7 +65,7 @@ placement aggregates that match the membership and UUID of nova host aggregates that you assign as availability zones. The same key in aggregate metadata used by the `AvailabilityZoneFilter` filter controls this function, and is enabled by setting :oslo.config:option:`scheduler.query_placement_for_availability_zone` -to ``True``. +to ``True``. As of 24.0.0 (Xena), this is the default. .. code-block:: console @@ -102,11 +102,9 @@ to ``True``. $ openstack --os-placement-api-version=1.2 resource provider aggregate set --aggregate 019e2189-31b3-49e1-aff2-b220ebd91c24 815a5634-86fb-4e1e-8824-8a631fee3e06 -With the above configuration, the `AvailabilityZoneFilter` filter can be -disabled in :oslo.config:option:`filter_scheduler.enabled_filters` while -retaining proper behavior (and doing so with the higher performance of -placement's implementation). - +Without the above configuration, the `AvailabilityZoneFilter` filter must be +enabled in :oslo.config:option:`filter_scheduler.enabled_filters` to retain +proper behavior. Implications for moving servers ------------------------------- |