On Fri, Feb 20, 2015 at 7:15 PM, Russell Bryant <rbry...@redhat.com> wrote:
> On 02/20/2015 06:46 PM, Ben Pfaff wrote: > > * Not yet scoped: > > > > ** Neutron plugin. > > > > I'd appreciate input on this. > > I've just started looking into this. As a start, from a high level my > to-do thoughts are: > > *** Create stackforge/networking-ovn repository based on OpenStack's > cookiecutter git repo generator > > ++ > *** Document mappings between Neutron data model and the OVN northbound DB > > *** Create a Neutron ML2 mechanism driver that implements the mappings > on Neutron resource requests > > Do we want to do an ML2 MechanismDriver or do a full-fledged plugin? Since we're starting from scratch here, we should evaluate the pros and cons of this decision. It does save some code, but do we envision running OVN with other ML2 MechanismDrivers at the same time? Note I'm not necessarily saying I'm in favor of doing a full plugin, only that we should think about it a bit before deciding which path to take. > *** Add synchronization for when we need to sanity check that the OVN > northbound DB reflects the current state of the world as intended by > Neutron (needed for various failure scenarios) > > -- > Russell Bryant > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
