From 1e617ea3a1ad65aef02498b30988cfbefe7b1595 Mon Sep 17 00:00:00 2001 From: Tetsuro Nakamura Date: Thu, 27 Sep 2018 20:26:55 +0900 Subject: [PATCH] Follow up for placement usage document This patche addresses the following review comments from earlier in this series: https://review.openstack.org/#/c/604243/4/doc/source/usage/index.rst@28 https://review.openstack.org/#/c/604243/4/doc/source/usage/provider-tree.rst@190 https://review.openstack.org/#/c/604243/4/doc/source/usage/provider-tree.rst@264 Change-Id: I15097a850cf6f6f33d42234f6e3a72d103d6bc42 --- doc/source/usage/index.rst | 2 +- doc/source/usage/provider-tree.rst | 10 +++++----- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/source/usage/index.rst b/doc/source/usage/index.rst index 28ec6a116..ad59e7a4c 100644 --- a/doc/source/usage/index.rst +++ b/doc/source/usage/index.rst @@ -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 `. diff --git a/doc/source/usage/provider-tree.rst b/doc/source/usage/provider-tree.rst index b966b098d..cacf5a687 100644 --- a/doc/source/usage/provider-tree.rst +++ b/doc/source/usage/provider-tree.rst @@ -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.