Yeah, the only thing this will due will change the default rules that are generated for a user's default security group. They will still be visible via the normal security groups API and users will be able to modify them. On Mar 2, 2016 08:22, "Dean Troyer" <dtroyer at gmail.com> wrote: > On Wed, Mar 2, 2016 at 10:10 AM, Fawad Khaliq <fawad at plumgrid.com> wrote: > >> Neutron security groups APIs should already allow discovery of what >> default gets created. This should work or are you suggesting something >> else? >> > > So the default here for an allow all would be to include a single rule to > do that? That's fine, I was concerned about a config/deploy option that > resulted in no visible change to detect... > > dt > > -- > > Dean Troyer > dtroyer at gmail.com > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > 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/20160302/306af120/attachment.html>