[ovs-discuss] ovs-vswitchd tcp:openvswitch-db:6640

[Justin Pettit]

> On Aug 3, 2016, at 7:19 AM, Serguei Bezverkhi (sbezverk) <sbezverk at cisco.com> wrote:
> 
> Hello,
> 
> I need to run openvswitch in the environment where there is no way to use fixed ip addresses and dns names must be used to discover the actual location (ip address) of database process. Here is the command line I used:
> 
> ovs-vswitchd tcp:openvswitch-db:6640
> 
> where openvswitch-db is the dns name which is resolvable by a simple dns query. It seems ovs-vswitchd supports only IP address as an argument of tcp keyword.
> 
> Here is the log:
> 2016-08-03T13:59:51.393Z|00004|socket_util|ERR|openvswitch-db:6640: bad IPv4 address "openvswitch-db"
> 2016-08-03T13:59:51.393Z|00005|stream_tcp|ERR|tcp:openvswitch-db:6640: connect: Address family not supported by protocol
> 2016-08-03T13:59:51.393Z|00006|reconnect|INFO|tcp:openvswitch-db:6640: connecting...
> 2016-08-03T13:59:51.393Z|00007|reconnect|INFO|tcp:openvswitch-db:6640: connection attempt failed (Address family not supported by protocol)
> 2016-08-03T13:59:51.393Z|00008|reconnect|INFO|tcp:openvswitch-db:6640: waiting 1 seconds before reconnect
> 
> Is there any way to make tcp to use dns name as well as ip address?

No, there is not.  If I remember correctly, the primary of the reason is that it's very hard to do DNS with in-band control without white-listing a ton of ports and addresses, which is how OVS is generally deployed.  If you need the ability (and aren't deploying OVS in-band), I think you could get around it with some scripting pretty easily.

--Justin