← Back to team overview

openstack team mailing list archive

Re: nova scheduler: AggregateMultiTenancyIsolation enhanced for domain level tenancy

 

Hi,
I never thought about domains but it seems a great idea!
If you want to extend it would be great.

Remember that at the moment the "AggregateMultiTenancyIsolation" filter only guaranties that the nodes in the aggregate will run instances from the specified tenant. But it isn't exclusive…
There is a blueprint to extend it: https://blueprints.launchpad.net/nova/+spec/multi-tenancy-isolation-only-aggregates
At CERN we already implemented this blueprint and we also support of multiple tenants in the same aggregate. We use this filter to have dedicated resources for some tenants.

I didn't upload the code yet… in my TODO list 
but also waiting for the blueprint approval.

cheers,
Belmiro


On May 3, 2013, at 8:21 PM, boden <boden@xxxxxxxxxxxxxxxxxx> wrote:

> Hi,
> I was poking around for a way to scope host aggregates at the domain level and moreover support the notion multiple tenant access.
> 
> For example:
> * As an Cloud provider, I want to isolate aggregates/availability zones at the domain level (i.e. assign which domain can spawn instances on a given aggregate/az)
> * As an Cloud provider, I want to isolate aggregates/availability zones at the domain level and permit multiple domains or projects access (i.e. same as previous UC but permit a set of domains access to the aggregate/az)
> 
> I came across the AggregateMultiTenancyIsolation scheduler filter and it appears it might be fairly simple to enhance this filter to:
> (a) support domains in addition to tenants/project (i.e. filter_domain_id in aggregate metadata)
> (b) support multiple domains/projects access (i.e. allow a comma list or array or domains/tenants on the aggregate metadata)
> 
> Anyone else see a need for this?
> 
> Disclaimer: nova n00b here, so my above assertions may be off target.
> 
> Thx
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp



References