> I wouldn't expect Neutron to use the field. My thinking for adding it
> was just for convenience when doing dev and test from the command line.
>
> Neutron networks map to an OVN logical switch [1]. Neutron uses a UUID
> to uniquely identify a network, and I was proposing we stick that in as
> an external:id. I was also proposing sticking neutron's network name in
> as an external:id, but that could be moved to the new "name" field.
> Again though, the name is just for convenience and shouldn't need to be
> unique.
>
> On the command line (ovn-nbctl) side, I suppose it could accept either a
> name or UUID and fail if a given name isn't unique. That's typically
> how OpenStack utilities behave.
All of that sounds good. Thanks!
_______________________________________________
dev mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/dev
