Comment 8 for bug 1328400

I confirm since we hit this on multinode environment. We're using Havana, but the description for Havana is the same and still incorrect. AggregateMultiTenancyIsolation behaviour in Havana is :
1. If a host is in host aggregate which has filter_tenant_id - the host can only contain a VM's from that tenant, and not from any other tenant
2. If the tenant mentioned in filter_tenant_id attribute spawn a VM, it chooses from ALL the hosts, and it does not guarantees that a VM will we spawned exactly in hosts from that aggregate.

So currently it just isolates host from any tenant except ones mentioned in filter_tenant_id attribute. But it does not isolates tenant to hosts from that aggregate, tenant can still spawn everywhere, dependent of other filters.