The original intent behind 'all_tenants=1' was whether or not to include all instances for all tenants in the filtering process. Basically it means "Should I operate as admin or not?". I still view it this way, and would prefer it still mean this (although it might be more clear with a different name). This means that if you're an admin… you're not treated as one UNTIL you specify all_tenants=1. So technically I think specifying a 'tenant_id' filter should raise or do whatever it does for a normal user. I don't think specifying a 'tenant_id' filter should mean that we automatically turn 'all_tenants' on. I don't see the bug deal in needing to remember to use all_tenants=1 so that all instances will be filtered, not just the instances belong to the admin user. My opinion, - Chris On Jun 16, 2013, at 11:09 PM, Aarti Mahesh Kriplani <aarti.kriplani at RACKSPACE.COM> wrote: > Hello all, > > There have been a few contrasting views on this bug<https://bugs.launchpad.net/nova/+bug/1185290>. > I would really like some views on how we want to use the all-tenenats flag going ahead. > Comments/Suggestions? > > Thanks, > Aarti > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130617/52c31381/attachment.html>