Thank you again for your feedback. On the discussion about two or three-way logic, I understand Yong's point of being able to fetch public and private networks in one call, but I also I agree with Endre that using a boolean flag for something which is actually Yes/No/Whatever sounds confusing and is different by what the Openstack CLI usually does.
Hence, if we have a large agreement on the need of being able to specify whether we want public networks, private networks or both, I'd go for the approach #3 in the design proposal, as suggested by Gary, and the CLI option would became something like --network_type={public|private|both}. On the agent issue raised by Gary - I'm afraid I don't understand. Gary, could you please elaborate more? Regards, Salvatore On 12 July 2012 05:37, Yong Sheng Gong <gong...@cn.ibm.com> wrote: > > If we just use one flag, it can represent just two values True or False. > If we want to represent three values True, False or not specified, we have > to use --public True or --public False or nothing at all. > > So it is a three-values logic. > > > -----openstack-bounces+gongysh=cn.ibm....@lists.launchpad.net wrote: ----- > To: openstack@lists.launchpad.net > From: Endre Karlson ** > Sent by: openstack-bounces+gongysh=cn.ibm....@lists.launchpad.net > Date: 07/12/2012 07:53PM > Subject: [Openstack] Fwd: [Quantum] Public Network spec proposal > > > Why not just --public or not ? Why do you need --public True ? That just > adds confusion... > > Endre. > > > 2012/7/12 Gary Kotton <gkot...@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@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> >> > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > ** > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp