Merge "Follow up for placement usage document"

This commit is contained in:
Zuul 2018-10-02 13:01:56 +00:00 committed by Gerrit Code Review
commit bff065567a
2 changed files with 6 additions and 6 deletions

View File

@ -25,7 +25,7 @@ via the placement REST API.
The nova resource tracker is responsible for creating the resource provider
record corresponding to the compute host on which the resource tracker runs.
If other projects -- for example, Neutron or Cyborg -- wish to manage resources
on a compute host, the should create resource providers as children of the
on a compute host, they should create resource providers as children of the
compute host provider and register their own managed resources as inventory on
those child providers. For more information, see the
:doc:`Modeling with Provider Trees <provider-tree>`.

View File

@ -187,8 +187,8 @@ would return two candidates.
2. ``NUMA1_2`` (``VCPU``) + ``CN1`` (``MEMORY_MB``, ``DISK_GB``)
This is because ``SS1`` is not in aggregate A, and because aggregate B on
``NUMA2_1`` doesn't span the whole tree since it isn't a root resource
provider.
``NUMA2_1`` doesn't span the whole tree since the ``NUMA2_1`` resource
provider isn't a root resource provider.
Filtering by Traits
===================
@ -261,9 +261,9 @@ Granular Resource Requests
==========================
If you want to get the same kind of resources from multiple resource providers
at once, or if you don't want to spread the trait/aggregate constraints across
multiple resource providers, you can use the `Granular Resource Request`_
feature.
at once, or if you require a provider of a particular requested resource
class to have a specific trait or aggregate membership, you can use the
`Granular Resource Request`_ feature.
This feature is enabled by numbering the ``resources``, ``member_of`` and
``required`` query parameters respectively.