Bug 1041200

Summary: [RFE][nova]: Multi-tenancy isolation only schedule instances in selected aggregates
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, sgordon, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/nova/+spec/multi-tenancy-isolation-only-aggregates
Whiteboard: upstream_milestone_none upstream_status_started upstream_definition_drafting
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:31:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 13:55:01 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/multi-tenancy-isolation-only-aggregates.

Description:

The implementation of the blueprint “Multi-tenancy isolation with aggregates” defines that:
“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.”

This use case only excludes instances from non-defined tenant(s) to start in
the aggregate(s).

The goal for this blueprint is to implement a new scheduler filter "ProjectsToAggregateFilter" that isolates a project in a aggregate.

Specification URL (additional information):

None