openstack
/
nova
Code Issues Proposed changes

Mention meta key suffix in tenant isolation with placement docs 

This changes does two things to the admin scheduler configuration
docs:

1. Notes the limitation from bug 1802111 for the older
   AggregateMultiTenancyIsolation filter and mentions that
   starting in Rocky, using tenant isolation with placement
   is better.

2. Notes that when isolating tenants via placement, the metadata
   key "filter_tenant_id" can be suffixed to overcome the limitation
   in bug 1802111.

Change-Id: I792c5df01b7cbc46c8363e261bc7422b09180e56
Closes-Bug: #1802111
(cherry picked from commit 1fa09acf08)
This commit is contained in:
Matt Riedemann 2018-11-09 11:30:44 -05:00
parent 8865e8fe0b
commit 4c0342bf1d
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/source/admin/configuration/schedulers.rst
View File

@ -222,6 +222,13 @@ instances from all tenants. This setting does not isolate the aggregate from
other tenants. Any other tenant can continue to build instances on the
specified aggregate.
.. note:: There is a
`known limitation <https://bugs.launchpad.net/nova/+bug/1802111>`_ with
the number of tenants that can be isolated per aggregate using this
filter. This limitation does not exist, however, for the
`Tenant Isolation with Placement`_ filtering capability added in the
18.0.0 Rocky release.
AggregateNumInstancesFilter
---------------------------
@ -1223,7 +1230,7 @@ Tenant Isolation with Placement
In order to use placement to isolate tenants, there must be placement
aggregates that match the membership and UUID of nova host aggregates
that you want to use for isolation. The same key pattern in aggregate
metadata used by the `AggregateMultiTenancyIsolation` filter controls
metadata used by the `AggregateMultiTenancyIsolation`_ filter controls
this function, and is enabled by setting
`[scheduler]/limit_tenants_to_placement_aggregate=True`.
@ -1265,6 +1272,9 @@ this function, and is enabled by setting
$ openstack --os-placement-api-version=1.2 resource provider aggregate set --aggregate 019e2189-31b3-49e1-aff2-b220ebd91c24 815a5634-86fb-4e1e-8824-8a631fee3e06
Note that the ``filter_tenant_id`` metadata key can be optionally suffixed
with any string for multiple tenants, such as ``filter_tenant_id3=$tenantid``.
Availability Zones with Placement
---------------------------------