Hi, you can get inspired by the L2-population MD, which call new functions in the agents (like add_fdb_entries) through AMQP. Does your work relate to an existing blueprint?
On Tue, Feb 25, 2014 at 9:23 PM, Sławek Kapłoński <[email protected]> wrote: > Hello, > > Trinath, this presentation I saw before You send me it. There is nice > explanation what methods are (and should be) in type driver and mech driver > but I need exactly that information what sent me Assaf. Thanks both of You for > Your help :) > > -- > Best regards > Sławek Kapłoński > Dnia wtorek, 25 lutego 2014 12:18:50 Assaf Muller pisze: > >> ----- Original Message ----- >> >> > Hi >> > >> > Hope this helps >> > >> > http://fr.slideshare.net/mestery/modular-layer-2-in-openstack-neutron >> > >> > ___ >> > >> > Trinath Somanchi >> > >> > _____________________________________ >> > From: Sławek Kapłoński [[email protected]] >> > Sent: Tuesday, February 25, 2014 9:24 PM >> > To: [email protected] >> > Subject: [openstack-dev] Neutron ML2 and openvswitch agent >> > >> > Hello, >> > >> > I have question to You guys. Can someone explain me (or send to link >> > with such explanation) how exactly ML2 plugin which is working on >> > neutron server is communicating with compute hosts with openvswitch >> > agents? >> >> Maybe this will set you on your way: >> ml2/plugin.py:Ml2Plugin.update_port uses _notify_port_updated, which then >> uses ml2/rpc.py:AgentNotifierApi.port_update, which makes an RPC call with >> the topic stated in that file. >> >> When the message is received by the OVS agent, it calls: >> neutron/plugins/openvswitch/agent/ovs_neutron_agent.py:OVSNeutronAgent.port_ >> update. >> > I suppose that this is working with rabbitmq queues but I need >> > to add own function which will be called in this agent and I don't know >> > how to do that. It would be perfect if such think will be possible with >> > writing for example new mechanical driver in ML2 plugin (but how?). >> > Thanks in advance for any help from You :) >> > >> > -- >> > Best regards >> > Slawek Kaplonski >> > [email protected] >> > >> > _______________________________________________ >> > 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 > > _______________________________________________ > 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
