Re: [Openstack] [Quantum] Network, Subnet and Port names

2012-07-18 Thread Jay Pipes
On 07/18/2012 04:53 AM, Hua ZZ Zhang wrote: > All networks information of all tenants are stored in one table. If the > name is defined unique, it implicates all tenants have to make sure the > name of new network will not be conflict with others even they don't > know each other. the system has to

Re: [Openstack] [Quantum] Network, Subnet and Port names

2012-07-18 Thread Hua ZZ Zhang
cc m@lists.launchpad openstack@lists.launchpad.net .net Subject Re: [Openstack] [Quantum] Network, Su

Re: [Openstack] [Quantum] Network, Subnet and Port names

2012-07-17 Thread Dolph Mathews
The philosophy from the keystone side of the fence is that once you have non-unique names you can't go back; whereas, it's trivial to go from unique to non-unique names. So, without a solid business case to push us in either direction, we started by enforcing uniqueness. With the Identity API v3 d

Re: [Openstack] [Quantum] Network, Subnet and Port names

2012-07-17 Thread Jay Pipes
On 07/17/2012 01:27 AM, Dan Wendlandt wrote: > Hi Gary, this is an example of when I wish openstack APIs had a > "style-guide" to try to ensure some consistency across projects. Yeah, we actually discussed this a long time ago on the PPB and, IIRC, the decision was made to not have some strict A

Re: [Openstack] [Quantum] Network, Subnet and Port names

2012-07-17 Thread Gary Kotton
On 07/17/2012 10:39 AM, Salvatore Orlando wrote: I don't think either of you is wrong. I too think that in cases where it's not easy to find a majority, it might make sense to just do what the other projects are doing. Unfortunately for us, Keystone adopts the "name is unique" phylosophy, where

Re: [Openstack] [Quantum] Network, Subnet and Port names

2012-07-17 Thread Salvatore Orlando
I don't think either of you is wrong. I too think that in cases where it's not easy to find a majority, it might make sense to just do what the other projects are doing. Unfortunately for us, Keystone adopts the "name is unique" phylosophy, whereas nova adopts "name is a label". Is it worth consid

Re: [Openstack] [Quantum] Network, Subnet and Port names

2012-07-16 Thread Dan Wendlandt
Hi Gary, this is an example of when I wish openstack APIs had a "style-guide" to try to ensure some consistency across projects. For those new to the conversation, the original topic of discussion is whether "names" for API objects should be forced to be unique (presumably within a tenant?) or all

[Openstack] [Quantum] Network, Subnet and Port names

2012-07-16 Thread Gary Kotton
Hi, If the name is intended to be a description then how about the idea of calling the field "description" instead. This is far more descriptive and does not lend the user to think that this should be unique. Thanks Gary ___ Mailing list: https://lau