From e5a00fbdbdc8770818281c013a37570f3e0e4538 Mon Sep 17 00:00:00 2001 From: Dan Smith Date: Wed, 28 Mar 2018 12:29:14 -0700 Subject: [PATCH] Documentation for tenant isolation with placement This explains how to actually wire up placement aggregates to allow for filtering on tenant. Change-Id: Idb06e7562d88957a00f52cba7d0a788dbff42a28 --- .../tenant_aggregate_placement_filter-c2fed8889f43b6e3.yaml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/releasenotes/notes/tenant_aggregate_placement_filter-c2fed8889f43b6e3.yaml b/releasenotes/notes/tenant_aggregate_placement_filter-c2fed8889f43b6e3.yaml index d6c8afc37..def6d58a1 100644 --- a/releasenotes/notes/tenant_aggregate_placement_filter-c2fed8889f43b6e3.yaml +++ b/releasenotes/notes/tenant_aggregate_placement_filter-c2fed8889f43b6e3.yaml @@ -8,4 +8,7 @@ features: 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. \ No newline at end of file + 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 \ No newline at end of file