Multi-tenancy isolation with aggregates
Multi-tenancy isolation with aggregates.
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
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- Low
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Belmiro Moreira
- Definition:
- Approved
- Series goal:
- Accepted for grizzly
- Implementation:
- Implemented
- Milestone target:
- 2013.1
- Started by
- Belmiro Moreira
- Completed by
- Thierry Carrez
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Multi-tenancy isolation with aggregates
Addressed by: https:/
Multi-tenancy isolation with aggregates