hi,
please consider that maintaining drivers from one openstack version to
others is really hard when those drivers are out of the scope of
neutron developers/continuous Integration process. For instance, ML2
is currently refactored by this patch :
https://review.openstack.org/#/c/82945/
you
Hi slawek,
As soon as you declare l2population in the MD section of the config
file, it will be loaded by ML2 plugin. l2population MD will listen to
ML2 DB events and send RPC messages to ovs agent when needed.
l2population MD will not bind the port, ovs MD will.
By the way, you need to ad add
Hello,
Thanks for explanation. Now it is clear for me :) I made my own driver because
I made config on hosts in special way but I can't describe details :/
Best regards
Slawek Kaplonski
sla...@kaplonski.pl
Dnia wtorek, 6 maja 2014 10:35:05 Mathieu Rohon pisze:
Hi slawek,
As soon as you
Hello,
Thanks for answear. Now I made my own mech_driver which inherits from l2_pop
driver and it is working ok. But If I will set it as:
mechanism_drivers=openvswitch,l2population than ports will be binded with
ovs driver so population mechanism will be working in such network?
Best regards
Hi Slawek,
I think L2 pop driver needs to be used in conjunction with other mechanism
drivers.
It only deals with pro-actively informing agents on which MAC Addresses became
available/unavailable on cloud nodes and is not meant for binding/unbinding
ports
on segments.
If you configure
