Host Aggregate Restrictions.

asked 2018-11-20 09:40:34 -0500

Fernando.S gravatar image

I'm familiar with restricting specific projects to a host aggregate via AggregateMultiTenancyIsolation filter_tenant_id metadata. I'm also aware you can target a host aggregate using aggregate_instance_extra_specs metadata on the flavor. Unfortunately instances/flavors without that aggregate_instance_extra_specs metadata can still land on that aggregate.

Is there a way to restrict all instances from launching on a host aggregate unless specific metadata is within the flavor. I need another method of restricting host aggregates other than by filter_tenant_id

edit retag flag offensive close merge delete


Did you ever figure out a simple solution for this?

szeestraten gravatar imageszeestraten ( 2019-03-21 15:37:20 -0500 )edit