[ovs-dev] [PATCH] ovn: Design and Schema changes for Container integration.

[Gurucharan Shetty]

> It might be worth giving the back-story on rationale for change #2.
Here is the backstory:
Before the introduction to Container (spawned inside VMs) networking
in OVN, OVN's architecture was designed with VMs in mind. In this
case, ovn-controller could create a record in Bindings table as soon
as it could see a VIF created as a port in Open vSwitch integration
bridge (in the hypervisor). But when a container is created inside a
VM, ovn-controller does not have any information about it and it
cannot create a record in the Bindings table.  So the RFC proposed
that just in case of containers, this record would be created by
ovn-nbd. This made the workflow a little ugly, wherein 2 components
were involved in creation and deletion of the records in Bindings
table. So in this change, we bring consistency in the Bindings table
creation. Now, Bindings table is exclusively created by ovn-nbd and
ovn-controller is only responsible in changing the chassis column
inside it.