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 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 the flag l2population in config file of > the agent. > > just to be curious, what your MD which inherit from l2_pop MD is made for? > > regards > > Mathieu > > On Mon, May 5, 2014 at 11:06 PM, Sławek Kapłoński <sla...@kaplonski.pl> wrote: > > 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 > > Slawek Kaplonski > > sla...@kaplonski.pl > > > > Dnia poniedziałek, 5 maja 2014 00:29:56 Narasimhan, Vivekanandan pisze: > >> 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 mechanism_drivers=openvswitch,l2population in your > >> ml2_conf.ini and restart your neutron-server, you'll notice that > >> bind_port > >> is handled by OVS mechanism driver (via AgentMechanismDriverBase inside > >> ml2/drivers/mech_agent.py). > >> > >> -- > >> Thanks, > >> > >> Vivek > >> > >> > >> -----Original Message----- > >> From: Sławek Kapłoński [mailto:sla...@kaplonski.pl] > >> Sent: Sunday, May 04, 2014 12:32 PM > >> To: openstack-dev@lists.openstack.org > >> Subject: [openstack-dev] [ML2] L2 population mechanism driver > >> > >> Hello, > >> > >> Last time I want to try using L2pop mechanism driver in ML2 (and > >> openvswitch agents on compute nodes). But every time when I try to spawn > >> instance I have got error "binding failed". After some searching in code > >> I found that l2pop driver have not implemented method "bind_port" and as > >> it inherit directly from "MechanismDriver" this method is in fact not > >> implemented. Is is ok and this mechanism driver should be used in other > >> way or maybe there is some bug in this driver and it miss this method? > >> > >> Best regards > >> Slawek Kaplonski > >> sla...@kaplonski.pl > >> > >> _______________________________________________ > >> OpenStack-dev mailing list > >> OpenStack-dev@lists.openstack.org > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >> > >> _______________________________________________ > >> OpenStack-dev mailing list > >> OpenStack-dev@lists.openstack.org > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > > OpenStack-dev mailing list > > OpenStack-dev@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
