doc: Fix term mismatch warnings in glossary
The term role has became case sensitive since sphinx 3.0.1. It causes the following warnings and makes a check job fail. WARNING: term not in glossary: availability zone This patch fixes the issue. Change-Id: I1f993b503ef769da0950afa206d6ac4a54f903b4 Closes-Bug: #1872260
This commit is contained in:
parent
8e7d26e0b4
commit
2e299a6e72
@ -25,7 +25,7 @@ per-aggregate basis by setting the desired ``xxx_weight_multiplier`` aggregate
|
||||
metadata.
|
||||
|
||||
Administrators are able to optionally expose a host aggregate as an
|
||||
:term:`availability zone`. Availability zones are different from host
|
||||
:term:`Availability Zone`. Availability zones are different from host
|
||||
aggregates in that they are explicitly exposed to the user, and hosts can only
|
||||
be in a single availability zone. Administrators can configure a default
|
||||
availability zone where instances will be scheduled when the user fails to
|
||||
|
@ -24,7 +24,7 @@ By default, the scheduler ``driver`` is configured as a filter scheduler, as
|
||||
described in the next section. In the default configuration, this scheduler
|
||||
considers hosts that meet all the following criteria:
|
||||
|
||||
* Are in the requested :term:`availability zone` (``AvailabilityZoneFilter``).
|
||||
* Are in the requested :term:`Availability Zone` (``AvailabilityZoneFilter``).
|
||||
|
||||
* Can service the request (``ComputeFilter``).
|
||||
|
||||
|
@ -33,7 +33,7 @@ Glossary
|
||||
|
||||
Host Aggregate
|
||||
Host aggregates can be regarded as a mechanism to further partition an
|
||||
:term:`availability zone`; while availability zones are visible to
|
||||
:term:`Availability Zone`; while availability zones are visible to
|
||||
users, host aggregates are only visible to administrators. Host
|
||||
aggregates provide a mechanism to allow administrators to assign
|
||||
key-value pairs to groups of machines. Each node can have multiple
|
||||
|
Loading…
Reference in New Issue
Block a user