Reviewed: https://review.openstack.org/373624 Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=cec525097907ee593a7f4c88c6f7b4f1b0daef1a Submitter: Jenkins Branch: master
commit cec525097907ee593a7f4c88c6f7b4f1b0daef1a Author: Hong Hui Xiao <email address hidden> Date: Wed Sep 21 11:23:11 2016 +0800
Use ovs.db.idl to monitor ovsdb
When the ovs idl client connects to the ovsdb-server, it gets a dump of all DB resources. DF can just use the idl to monitor ovsdb. This could simplify the code, and save the procedure to explicitly notify ovs interface creation.
Change-Id: I08be04d90f709e54ffb91f2fff4dc3efba9506ed Partial-Bug: #1622879
Reviewed: https:/ /review. openstack. org/373624 /git.openstack. org/cgit/ openstack/ dragonflow/ commit/ ?id=cec52509790 7ee593a7f4c88c6 f7b4f1b0daef1a
Committed: https:/
Submitter: Jenkins
Branch: master
commit cec525097907ee5 93a7f4c88c6f7b4 f1b0daef1a
Author: Hong Hui Xiao <email address hidden>
Date: Wed Sep 21 11:23:11 2016 +0800
Use ovs.db.idl to monitor ovsdb
When the ovs idl client connects to the ovsdb-server, it gets a dump
of all DB resources. DF can just use the idl to monitor ovsdb. This
could simplify the code, and save the procedure to explicitly notify
ovs interface creation.
Change-Id: I08be04d90f709e 54ffb91f2fff4dc 3efba9506ed
Partial-Bug: #1622879