Fixed issue with connection-info->{local-ip,local-port} not being stored
authorEd Warnicke <hagbard@gmail.com>
Fri, 1 May 2015 17:58:52 +0000 (10:58 -0700)
committerEd Warnicke <hagbard@gmail.com>
Fri, 1 May 2015 17:58:52 +0000 (10:58 -0700)
commite2859b8adab83dccafb7cbb4bb98a92fb0a2ae10
tree69c17545f19cc1c4cf5598fa5d2d4ad4216cef77
parent23db3b447c5530f7539c7e358a0443f1454ea5c9
Fixed issue with connection-info->{local-ip,local-port} not being stored

Use of ConnectionInfo as a key in OvsdbConnectionManager
should only have remote{Ip,port} info... so:

1)  Introduced a method suppressLocalIpPort() to SouthboundMapper
    to strip localIp/Port info out of a ConnectionInfo if needed
2)  Insured that *all* gets to the clients map in OvsdbConnectionManager
    use that method before doing a lookup
3)  Insured that *all* puts to the clients map in OvsdbConnectionManager
    use that method before writing.

Also in passing fixed disconnect to just get the connectionInfo from
the ovsdbNode it has, instead of doing a convoluted dance and
removed the then no longer used createConnectionInfo(ovsdbNode) from
SouthboundMapper.

Change-Id: Idb2b16d52ec23267584c69c6e474652dd25a4ab0
Signed-off-by: Ed Warnicke <hagbard@gmail.com>