We are trying to use a single management cluster to support compute clusters in multiple security zones (to reduce operational overhead). Ideally we could use multiple transport zones so that we can't spin up a VM in security zone A on a compute cluster in security zone B.
Has anyone run into this issue and had any luck in hacking nsx.ini to support multiple vdn_scope_ids? I couldn't find any proposed changes that would resolve this (but maybe I'm missing it). It seems like an alternate way to "filter" this would be use a host aggregate, but it seems a little convoluted to do it that way... Thanks in advance! Liz
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
