Update to new version of the artifacts proposed by jenkins-ovsdb-version-changes-1

Change-Id: I89d7c9944b76265650ebbc1839e1cf012b63ec77
Signed-off-by: Jenkins ovsdb silo <jenkins-ovsdb@daylight7.linux-foundation.org>
Harmonize the use of <scm> in pom.xml files

Modify pom.xml files to have the same <scm> section.  Fix typo in some
of the <developerConnection> URLs.

Change-Id: I761cbc67d5230470501eacd8f474ec113c8a73d7
Signed-off-by: Lorand Jakab <lojakab@cisco.com>
Refactored IT's to remove dependency on com.google.code.gson.internal.Pair
Renamed IT's to fix typos and keep case consistent

Change-Id: I97bf39df8a8a6b127309a495e1a8b58cba92d291
Signed-off-by: Dave Tucker <dave.j.tucker@hp.com>
Make automagically adding a controller to each detected bridge after connecting an OVS node a configurable setting. The default is ovsdb.autoconfigurecontroller=true

I've seen multiple configurations where the ip address of a host is configured on the bridge interface.
So for example there is one bridge (cloudbr0) and one interface (eth0). Eth0 would be added as a port to cloudbr0 and the ip address of the host would be configured on cloudbr0. This is actually the recommended configuration when using CloudStack with a Xen or KVM hypervisor running OVS. I've seen this configuration is multiple other setups as well.
When a node with this configuration is added to the ODL controller, all communication will be blocked as a controller implies that the switch will be flow based. This causes ovsdb to lose communication to the outside world and effectively isolates the hypervisor from the network.

This commit adds a property to configure this feature from config.ini. Set "ovsdb.autoconfigurecontroller" to true to configure controllers on all detected openvswitch bridges.

Change-Id: I8285bd2b8a7000997b4b62373bd9e02457c93d8e
Signed-off-by: Hugo Trippaers <hugo@trippaers.nl>
Merge "Refactored IT's to remove dependency on com.google.code.gson.internal.Pair Renamed IT's to fix typos and keep case consistent"
Deleted the POSTMAN script that got invalid after the jackson upgrade.

Change-Id: Ic9bdd7e62cc7f26df41262c14d9b23fae48b8ce1
Signed-off-by: Madhu Venugopal <mavenugo@gmail.com>
Fixed the OVSDB Northbound API Postman Script that works with the Jackson Upgrade

Change-Id: If5b8f744eaaecd38fa6ee96b16268529bcb691c8
Signed-off-by: Madhu Venugopal <mavenugo@gmail.com>
Added OF v1.3 flowmod builders for neutron integration.

Change-Id: Ibbe6123d12bea1d72e097552628a4f22d61a80be
Signed-off-by: Brent Salisbury <brent.salisbury@gmail.com>
Merge "Added OF v1.3 flowmod builders for neutron integration."
OVSDB support for controller restart scenario to work along with Neutron interface.

With the Controller support for neutron config save/restore in, this fix handles the next level
of bootup handling in the ovsdb's neutron handling.
Essentially, the southboundhandler triggers the update for the existing OVSDB connection and that
handles all the programming needs.

Change-Id: Ic72af4eb5d456ac09dcce4eed6bd3cb03804b45f
Signed-off-by: Madhu Venugopal <mavenugo@gmail.com>
Fixed a typo in pom.xml s/includeArtifacIds/includeArtifactIds

Change-Id: Ibcd8d2dbe3ffb500b58c966aef52029a8504cd8c
Signed-off-by: Brent Salisbury <brent.salisbury@gmail.com>
Merge "Fixed a typo in pom.xml s/includeArtifacIds/includeArtifactIds"
Merge remote-tracking branch 'odl/master' into tenant-vs
Dedicated bridges for tenant network