On Thu, Aug 27, 2015 at 10:27:41AM -0400, raju wrote: > Tried the below way, still able to access other AVzones also > > nova aggregate-set-metadata <aggregate_ID> filter_tenant_id=<tenant_ID>
you need to give that tenant special flavors, and add to the flavors and aggregates a key like special_tenant=Yes and enable AggregateInstanceExtraSpecsFilter in nova.conf > > Thanks for all your replies, appreciate it. > > > On Wed, Aug 26, 2015 at 9:55 PM, gustavo panizzo <gfa> <[email protected]> > wrote: > > > On Thu, Aug 27, 2015 at 11:26:42 +1000, Marcus Furlong wrote: > > > On 27 August 2015 at 06:48, raju <[email protected]> wrote: > > > > Hi, > > > > > > > > I want to restrict Avzones to particular Tenant so that users in the > > Tenant > > > > can only see the particular Avzone from drop down while provisioning > > > > instances. > > > > you can add a *filter_tenant_id* key on the aggregate which makes the AZ > > and configure AggregateMultiTenancyIsolation filter, that will exclude > > other tenants from those hypervisors, AZ will still be visible by other > > tenants but they won't be able to use it > > > > -- > > 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 > > > > keybase: http://keybase.io/gfa > > -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: http://keybase.io/gfa _______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
