A little confusion on this etherpad topic: <Neutron is not a controller! Can OpenDaylight become The Controller?>
Is this the common consensus of the Whole Neutron community, and what does the word "controller" mean here? If Neutron controller nodes are not doing anything related with "controlling", then what about the default built-in implementation of L2population in the ML2 plugin, and DVR in the L3 plugin, and the upcoming features like dynamic routing, BGP VPN, and so on? By my thought, ODL is a standalone controller separated from Neutron, and could co-exist with Neutron if customers choose to do so. But Neutron built-in implementation in the plugins is already a sort of *Controller*, there are no logical function difference in the natural positioning between them. What is the standpoint of Neutron community: is the built-in implementation just a reference for POC (waiting some future 3rd Controller like ODL for commercialized deployment), or aimed at large scale production deployment by itself? Who will be the first citizen? On Mon, Nov 3, 2014 at 7:15 PM, Carl Baldwin <[email protected]> wrote: > https://etherpad.openstack.org/p/odl-neutron-plugin > > On Mon, Nov 3, 2014 at 4:05 AM, Richard Woo <[email protected]> wrote: >> Hi, what is etherpad link for opendaylight neutron plugin design session? >> >> http://kilodesignsummit.sched.org/event/5a430f46842e9239ea6c29a69cbe4e84#.VFdhdPTF-0E >> >> Thanks, >> >> Richard >> >> _______________________________________________ >> OpenStack-dev mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
