Hi Carl,

Thanks for kicking this off. I am also willing to help as a core reviewer
of blueprints and code
submissions only.

As for the ML2 agent, we all know that for historic reasons Neutron has
grown to be not only a networking orchestration project but also a
reference implementation that is resembling what some might call an SDN
controller.

I think that most of the Neutron folks realize that we need to move away
from this model and rely on a strong open source SDN alternative; for these
reasons, I don't think that pursuing an ML2 agent would be a path we should
go down to anymore. It's time and energy that could be more effectively
spent elsewhere, especially on the refactoring. Now if the refactoring
effort ends up being labelled ML2 Agent, I would be okay with it, but my
gut feeling tells me that any attempt at consolidating code to embrace more
than one agent logic at once is gonna derail the major goal of paying down
the so called agent debt.

My 2c
Armando
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to