Create physnet bridges+ports and patch to br-int 25/41925/21
authorJosh <jhershbe@redhat.com>
Sun, 17 Jul 2016 12:09:54 +0000 (14:09 +0200)
committerSam Hague <shague@redhat.com>
Sat, 30 Jul 2016 10:37:44 +0000 (10:37 +0000)
commit9eaee29f3257244c474a51b8087f63d9315e3ca5
treecd29ac7fc900c54245468e026e3d3df2f2d984a8
parent3e834ddd72967f2dd9052c36dbeb6e9596830733
Create physnet bridges+ports and patch to br-int

NB: This commit depends on changes in the ovsdb
project: https://git.opendaylight.org/gerrit/#/c/41946/

AND NOW ALSO:
https://git.opendaylight.org/gerrit/#/c/42693/

Assume "provider_mappings=physnet1:ABC". ABC will either be (in this
order) (1) the name of a port already configured on br-int, (2) the name
of a bridge already configured on OVS, or (3) the name of a physical
interface. So for each option:

(1) ABC is a port already on br-int
At OVSDB node add/update event:
  no op
When adding the ElanInterface to the ElanInstance:
  ABC is the name of the port, use that

(2) ABC is the name of a bridge on OVS
At OVSDB node add/update event:
  patch the bridge to br-int, br-int side port name is ABC-patch
When adding the ElanInterface to the ElanInstance:
  ABC-patch is the name of the port, use that

(3) ABC is the name of a NIC
At OVSDB node add/update event:
  add the port directly to br-int
When adding the ElanInterface to the ElanInstance:
  ABC is the name of the port, use that

Change-Id: Ibf6851d420c8197e11a6503b950fa381b829499c
Signed-off-by: Josh <jhershbe@redhat.com>
vpnservice/elanmanager/elanmanager-impl/src/main/java/org/opendaylight/netvirt/elan/internal/ElanBridgeManager.java [new file with mode: 0644]
vpnservice/elanmanager/elanmanager-impl/src/main/java/org/opendaylight/netvirt/elan/internal/ElanOvsdbNodeListener.java
vpnservice/elanmanager/elanmanager-impl/src/main/java/org/opendaylight/netvirt/elan/internal/ElanServiceProvider.java
vpnservice/elanmanager/elanmanager-impl/src/main/java/org/opendaylight/netvirt/elan/utils/BridgeUtils.java [deleted file]