On Thu, May 04, 2017 at 10:01:00AM +0200, Miguel Angel Ajo Pelayo wrote: > Relates to previous comments: would it make sense to use a more generic > name instead of 'neutron' to avoid coupling to one solution?
Yes. The situation we have now, for Logical_Switch, is that "name" is a unique identifier and "external_ids:neutron:network_name" is a friendly name. As a technical matter, this works fine for any situation and any CMS. From a non-technical point of view, it is surprising in two ways, first that "name" is a unique identifier rather than a friendly name and second that non-OpenStack CMSes would use a key that contains "neutron". The ideal situation is probably to have "name" be a friendly name and to use an external_ids key for the unique name. It may not be necessary to standardize the unique name, but if we want to then we could choose external_ids:id or external_ids:unique_id or whatever. I didn't propose that change here because it requires coordination with networking-ovn, including some care for upgrades, which might include support for both keys for one or more releases. If folks who work on the Neutron side judge it worthwhile, then I'm more than willing to help out. (There is some precedent for this kind of change in OVS itself. In OVS, we first developed bindings to XenServer, then to other systems. If you search through ovs-vswitchd.conf.db(5), you will find various keys with an "xs-" prefix for XenServer, and you will also find similar keys without those prefixes. The "xs-" keys are the counterparts to the "neutron:" keys. We invented them before we realized that we needed to generalize. It might be possible to remove the "xs-" keys now; the main obstacle to that is that XenServer users don't speak up until a couple of releases have gone by because they don't keep up, so we'd have a very delayed reaction to any problems we might introduce.) _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
