IIUC, the required policy change is to allow a tenant to list ports that don't belong to you. I don't think the policy.json is powerful enough to allow tenants to list their external ports but no other ports they don't own. On Sep 8, 2014 10:30 AM, "Carl Baldwin" <carl at ecbaldwin.net> wrote: > I think there could be some discussion about the validity of this as a > bug report vs a feature enhancement. Personally, I think I could be > talked in to accepting a small change to address this "bug" but I > won't try to speak for everyone. > > This bug report [1] -- linked by devvesa to the bug report to which > Kevin linked -- suggests that the external IP address can be seen by > an admin user. Is there a policy.json setting that can be set at > deployment time to allow this without making a change to the code > base? > > Carl > > [1] https://bugs.launchpad.net/neutron/+bug/1189358 > > On Sun, Sep 7, 2014 at 3:41 AM, Kevin Benton <blak111 at gmail.com> wrote: > > https://review.openstack.org/#/c/83664/ > > _______________________________________________ > 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/20140908/7939f9d6/attachment.html>