It should be noted that the AggregateMultiTenancyIsolation does support multiple tenant ids in the filter_tenant_id metadata. https://github.com/openstack/nova/blob/master/nova/scheduler/filters/aggregate_multitenancy_isolation.py#L47-L51 (See code here). You would specify it by doing:

nova aggregate-set-metadata <aggregateid> filter_tenant_id=tenant1uuid,tenant2uuid

The cli is not smart enough to automatically detect the duplication of settings and combine them into a comma separated list. Make sure not to put any spaces in there or you'll have to wrap the "filter_tenant_id=..." in quotes so it gets parsed correctly.

I'm afraid that it's not supported.

Nova client will send only the last value via API call to server. When I modified the client to send a JSON containing two values, server bombed out with HTTP 500.

The workaround is to create two identical aggregates with different value of "filter_tenant_id".