Open Stack

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:slawek at kaplonski.pl]
Sent: Sunday, May 04, 2014 12:32 PM
To: openstack-dev at 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
slawek at kaplonski.pl

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev