[openstack-dev] [nova][neutron] Is it still valid/supported to create a network with a br-<uuid> id?

Doug Wiegley dougwig at parksidesoftware.com
Sun May 15 23:30:54 UTC 2016

> On May 15, 2016, at 10:17 AM, Matt Riedemann <mriedem at linux.vnet.ibm.com> wrote:
>> On 5/15/2016 10:56 AM, Sean M. Collins wrote:
>> Matt Riedemann wrote:
>>> The nova create-server API allows passing a network id that's prefixed with
>>> br-<uuid> [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.
>> 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.
>> That commit shouldn't have been accepted into Nova, and I don't think
>> that we should support anything but a UUID for a network id. Period.
> Yeah, I agree. Remember, this was Folsom, when Neutron was a young and brash Quantum.
> I was just trying to sort out if there is still anything out there in the stadium that relies on this working. If not, I'll microversion it out of support for the Nova API when we add support for auto-allocated-topology.

I agree with Sean.  Even if there is anything that relies on non uuid, it's totally fair to break it. 


> -- 
> Thanks,
> Matt Riedemann
> __________________________________________________________________________
> 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

More information about the OpenStack-dev mailing list