Re: [openstack-dev] [nova][neutron] Is it still valid/supported to create a network with a br- id?
On Sun, May 15, 2016 at 3:56 PM, Sean M. Collins wrote: > Matt Riedemann wrote: >> The nova create-server API allows passing a network id that's prefixed with >> br- [1]. That was added due to this bug from Folsom [2]. >> >> I'm wondering if that's still valid? Looking at the network.id data model in >> Neutron it doesn't look like it would be [3]. > > Wow. That bug is awful. Network IDs should be UUIDs and ONLY UUIDs. I agree, I'm having flashbacks to the dark days right now > Just because some vendor plugin decides that their going to break the > Networking API contract and define their own ID scheme, > doesn't mean that we should fix it to help them. The networking API at the time (quantum 1.0/1.1, the 2.0 that we know and loath today was added about 20 days prior, but not yet stable, or deployed anywhere), used identifiers that were opaque strings. The docs used uuid's as the identifiers for the examples, but the api punted on validation to individual plugins. > That commit shouldn't have been accepted into Nova, Obviously I disagree, see below for the history. > and I don't think > that we should support anything but a UUID for a network id. Period. Which is why this was fixed in the 2.0 api by checking the network identifer for uuid-ness. This was the result of the fun of shoe-horning every vendor's backend into quantum, without quantum being the authority. Not to mention that the reason it was prefixed with `br-` in the first place was established in the nova network api. It exposed out the bridge that implemented the network in the nova api, So the return from list networks on the nova side would list out things like br-public, br-int, etc. This got carried over into the quantum api when the project was founded. I think we can all agree that this compat shim should be dropped now that the v2.0 neutron api is merged and used (for quite sometime). Happy Hacking! 7-11 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] [RFC] Floating IP idea solicitation and collaboration
On Mon, Dec 8, 2014 at 7:57 PM, Carl Baldwin wrote: > I'll be traveling around the time of the L3 meeting this week. My > flight leaves 40 minutes after the meeting and I might have trouble > attending. It might be best to put it off a week or to plan another > time -- maybe Friday -- when we could discuss it in IRC or in a > Hangout. Carl, Very glad to see the work the L3 team has been working towards in this. I'm still digesting the specs/blueprints, but as you stated they are very much in the direction we'd like to head as well. I'll start lurking in the L3 meetings to get more familiar with the current state of things as I've been disconnected from upstream for a while. I'm `jkoelker` on freenode or `jkoel...@gmail.com` for hangouts if you wanna chat. Happy Hacking! 7-11 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Revisiting current column number limit in code
On Wed, Oct 30, 2013 at 6:19 AM, Ravi Kumar Pasumarthy wrote: > Hello, > > Looks like the current column limit for the code base is 80. Because of this > large space on the right hand side is not used. Please find the attached > pictures of couple of developer screens working on openstack codebase. > > Are there any thoughts to increase the current column limit to 120 atleast. > > How does this help ? I can see more lines of code, it is easier on the eyes. > Some external monitors supports rotation, but for laptops we cannot rotate. > > So is it possible to revisit the column number limit ? It looks from the screenshots that the common thread is using GUI IDE's. Using vim/emacs with splits, 3 views can be comfortably seen side by side on most high dpi monitors at 80 columns which is totes useful when coding against multiple projects at the same time. Happy Hacking! 7-11 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
