Why not just --public or not ? Why do you need --public True ? That just adds confusion... Endre. 2012/7/12 Gary Kotton <gkotton at redhat.com> > ** > Hi, > 1. Is this also applicable to the agents? Say for example a user wants to > ensure that a public network is attached to network interface em1 and the > private network attached to em2. Is this something that will be addressed > by the blueprint? > 2. I prefer option #3. This seems to be a cleaner approach for the user > interface. > Thanks > Gary > > > On 07/12/2012 01:52 AM, Salvatore Orlando wrote: > > Hi, > > A proposal for the implementation of the public networks feature has > been published. > It can be reached from the quantum-v2-public-networks blueprint page [1]. > Feedback is more than welcome! > > Regards, > Salvatore > > [1]: > https://blueprints.launchpad.net/quantum/+spec/quantum-v2-public-networks > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > > Post to : openstack at lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack at lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120712/6ce2fbf8/attachment.html>