grizzly: new scheduler filter for Multi-tenancy isolation with aggregates
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
Medium
|
Tom Fifield |
Bug Description
If https:/
A new scheduler filter that allows the creation of instances from
specific tenants in selected aggregates.
With this filter is possible to isolate tenants in a specific set
of compute nodes (aggregates).
If a host is in an aggregate that has the metadata key
"filter_tenant_id" it can only create instances from that tenant(s).
A host can be in different aggregates.
If a host doesn't belong to an aggregate with the metadata key
"filter_tenant_id" it can create instances from all tenants.
The scheduler documentation should be updated to include this new filter
https:/
The goal is to schedule instances from specific tenants to selected aggregate(s).
In different cases is necessary to isolate instances from specific tenant(s). This means that they can only be created in a set of hosts. To define the set of hosts we can use "aggregates".
The idea is to create a new scheduler filter "AggregateMulti
If an aggregate has the metadata filter_
An host can belong to different aggregates. So, a host can create instances from different tenants if the different aggregates have defined the metadata filter_
If a host doesn't belongs to any aggregate it can create instances from all tenants. Also, if a host belongs to aggregates that don't define the metadata filter_tenant_id it can create instances from all tenants.
Using Availability Zones can't solve this problem because a host can only be in one availability zone, also the filter "AggregateInsta
Changed in openstack-manuals: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
milestone: | none → grizzly |
tags: | added: nova |
Changed in openstack-manuals: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
patch in review