Comment 2 for bug 1328400

Hi Lingxian - yes, I've verified this behaviour in both a testing and production environment.

Please see http://lists.openstack.org/pipermail/openstack-dev/2014-June/036990.html for a discussion on the topic and agreement from others.

Steps to reproduce:

1) In an environment with a single compute node, such as a devstack installation, create host aggregate and add the compute node to the host aggregate
2) Add the metadata key 'filter_tenant_id' with any arbitrary value (eg: 'thisisatest')
3) Using any project, build an instance
4) Observe that the instance is still built on the compute node, even though the aggregate has the metadata key 'filter_tenant_id'

This is the way that the filter was designed - it only isolates the tenant list in the metadata key 'filter_tenant_id' to the host aggregate, but still allows all other tenants to build instances on that host. The documentation implies that it is exclusive.