Workaround to fix southbound it 20/18120/1
authorSam Hague <shague@redhat.com>
Fri, 10 Apr 2015 15:22:48 +0000 (11:22 -0400)
committerSam Hague <shague@redhat.com>
Fri, 10 Apr 2015 15:22:48 +0000 (11:22 -0400)
commitb3108fcb0dd1ffa31ffcb7825a635b5fe6ce5842
tree960753a3458da56bafc76604ea65e25525a73d01
parent820420cd141b81c5c3f23166f781951b1f491d51
Workaround to fix southbound it

The problem was the dataBroker in the southbound-it was not right. Something from outside ovsdb changed and caused issues with the way the soutbound-it was getting the broker.

The workaround was to get the broker from the SouthboundProvider.

Also added basic NetworkTopology and Topology to read the OVSDBTopology from the datastores since those values have to exist for southbound-impl to work.

Change-Id: Ie24c2bed42976efc64c142c30f6b1a8935435209
Signed-off-by: Sam Hague <shague@redhat.com>
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/SouthboundProvider.java
southbound/southbound-it/src/test/java/org/opendaylight/ovsdb/southbound/it/MdsalUtils.java [new file with mode: 0644]
southbound/southbound-it/src/test/java/org/opendaylight/ovsdb/southbound/it/SouthboundIT.java