TODO
=====================

* Document mappings between Neutron data model and the OVN northbound DB

* Add implementation of creating/deleting resources in the OVN northbound DB

** Create ML2 MechanismDriver

** Create L3 service plugin

* Add sync functionality to ensure that the OVN northbound DB reflects the
  current state of the world according to Neutron.

* Add devstack integration

* Add jenkins job that uses devstack integration.  Until we're able to test with
  OVN itself, this job can at least ensure that Neutron can start properly with
  this driver enabled.

TODO
=====================

* Document mappings between Neutron data model and the OVN northbound DB

* Add implementation of creating/deleting resources in the OVN northbound DB

** Create Neutron Plugin with appropriate mixins

* Add sync functionality to ensure that the OVN northbound DB reflects the
  current state of the world according to Neutron.

* Add devstack integration

* Add jenkins job that uses devstack integration.  Until we're able to test with
  OVN itself, this job can at least ensure that Neutron can start properly with
  this driver enabled.

Change from ML2 to monolithic plugin
Change from ML2 to monolithic plugin

Per discussion on the mailing list [1], I think moving to
implementing a full plugin with appropriate mixins is the
preferred approach for OVN. OVN implements it's own control
plane, and I don't see the benefit of running OVN with other
ML2 drivers since OVN can also control physical devices
implementing the VTEP schema from OVSDB.

[1] http://lists.openstack.org/pipermail/openstack-dev/2015-February/057560.html

Change-Id: I1d8cf7d47c012be798ce02f22f81f7e9b50fdd94
