Support DNS for ovn_{nb,sb}_connection

[Mohammed Naser]

At the moment, it seems that when using a DNS hostname for `ovn_nb_connection` or `ovn_sb_connection`, the connection never seems to go up.

It seems that the `ovs` library does not resolve an IP address before proceeding, I'm not sure if we should be resolving things and passing them on resolved to OVS, or tryign to look for fix upstream.

This is pretty critical for HA deployments that rely on multiple replicas with hostnames (i.e. a Kubernetes StatefulSet)

[yatin (yatinkarel)]

@mnaser, it's recently implemented in OVS[1] by Terry, can you check/confirm if that's what works for your case.

[1] https://github.com/openvswitch/ovs/commit/4d55a364ff60d894dce4e2e97a489d81520dc663

[Mohammed Naser (mnaser)]

Nice, this seems to have recently been brought in.. I think we’ll have to somehow use a newer version of the ovs binding to support it

[Terry Wilson (otherwiseguy)]

My patch for adding DNS resolution to python-ovs was recently merged: http://patchwork.ozlabs<email address hidden>/

We'll just need to wait for it to show up in a release.

[Slawek Kaplonski (slaweq)]

Thx Terry and Yatin for confirmation. I'm closing this bug as it's nothing to do in Neutron.