On Wed, May 03, 2017 at 07:42:46PM -0400, Russell Bryant wrote: > On Wed, May 3, 2017 at 11:45 AM, Ben Pfaff <b...@ovn.org> wrote: > > It's much easier to see what's going on in the southbound database if > > human-friendly names are available. > > > > Really it's too bad that we didn't put the human-friendly name in "name" > > and the UUID in something like "external_ids:neutron-uuid", but it'll take > > more coordination to change that at this point and it may not be worth it. > > Definitely a fair criticism. I had to think a bit about how we ended > up here ... > > The original OVN integration used ovn-nbctl instead of the Python ovs > library. I found it a quick and easy way to get the first POC driver > working. It was later converted to use the Python lib and we dropped > ovn-nbctl usage. > > When we create a resource in OVN, we have nowhere in the Neutron DB to > stash OVN's UUID, so we need to look up the OVN resource using > Neutron's UUID (name's are not unique). With ovn-nbctl, we only > supporting looking up by UUID or "name", so I had to use Neutron's > UUID there. So, this is a case of a quick decision made in the first > POC driver sticking and taking over 2 years for someone to notice the > odd choice and question it. I imagine everyone assumed it was for > good reason and that OVN required unique names. Oops. > > I see how you've made the best of it in your series and I really > appreciate that effort.
I thought that it was probably something like that. It's a very minor thing and I think that this is an OK workaround. _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
