The AggregateMultiTenancyIsolation filter description in http://docs.openstack.org/trunk/config-reference/content/section_compute-scheduler.html#aggregate-multi-tenancy-isolation gives the impression that it isolates a host aggregate for a specific tenant or list of tenants. This is not exactly true.
What the filter does do is as follows:
- it ensures that any instances created by the tenant (or list of tenants) are created only on that aggregate
- it still allows any other tenant to also build instances on the aggregate
In effect, it only isolates the specific tenant/tenant list to the aggregate - but it doesn't isolate the aggregate from other tenants, which is what the current description implies.
hi, Jesse:
after doing some code walkthrough, I'm afraid the orginal description is right. Tenant can create instances on the host doesn't belong to any aggregate and the host with aggregate that has the metadata key 'filter_tenant_id'.
Did you do some testing on the really deployment?