The Big Switch ML2 driver needs to be responsible for binding the IVS VIF type since there is no binding agent running for this virtual switch.
Currently, the Big Switch ML2 driver is only responsible for configuring VLANs in the fabric. It doesn’t do anything with the vSwitch so it leaves the responsibility of binding the ports to the OpenVSwitch driver. However, it needs to support IVS switches as well, which will not have a binding driver since they are directly controlled by the backend controller. Therefore, it will need to be responisble for responding to the bind_port calls for hosts with the IVS switches and mark them as bound.
At the port binding method to the Big Switch ML2 driver and have it respond to port binding calls for IVS ports.
Deployers will be able to deploy IVS vswitches with the Big Switch ML2 plugin.
In addition to the unit tests, a new 3rd party CI test case will be added for IVS deployed under ML2.
Mention that IVS can be used in conjuction with Big Switch Ml2 deployments.