a27da62d82
This explains how to actually wire up placement aggregates to allow for filtering on tenant. Change-Id: Idb06e7562d88957a00f52cba7d0a788dbff42a28
14 lines
847 B
YAML
14 lines
847 B
YAML
---
|
|
features:
|
|
- |
|
|
The scheduler can now use placement to more efficiently query for hosts within a
|
|
tenant-restricted aggregate. This requires that a host aggregate is created in
|
|
nova with the ``filter_tenant_id`` key (optionally suffixed with any string for
|
|
multiple tenants, like ``filter_tenant_id3=$tenantid``) and the same aggregate
|
|
is created in placement with an identical UUID. The
|
|
``[scheduler]/limit_tenants_to_placement_aggregate`` config option enables this
|
|
behavior and ``[scheduler]/placement_aggregate_required_for_tenants`` makes it
|
|
either optional or mandatory, allowing only some tenants to be restricted. For
|
|
more information, see the schedulers section__ of the administration guide.
|
|
|
|
__ https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#aggregates-in-placement |