Open Stack

Hi nader,

The easiest way would be to register a new RPC callback in the current
ovs agent. This is what we have done for the l2-pop MD, with fdb_add
and fdb_remove callbacks.
However, it could become a mess if every MD adds it own callback
directly into the code of the agent. L2 agent should be able to load
drivers, which might register new callbacks.
This could potentially be something to do while refactoring the agent
: https://review.openstack.org/#/c/57627/

On Tue, Mar 18, 2014 at 7:42 AM, Nader Lahouti <nader.lahouti at gmail.com> wrote:
> Hi All,
>
> In a multi-node setup, I'm using Ml2Plugin (as core plugin) and OVS
> (OVSNeutronAgent) as an agent on compute nodes. From controller I need to
> call a *new method* on agent ( on all compute nodes - using  RPC), to
> perform a task (i.e. to communicate with an external process). As I need to
> use OVSNeutronAgent, I am thinking the following as potential solution for
> adding the new method to the agent:
> 1. Create new plugin based on existing OVS agent - That means cloning
> OVSNeutronAgent and add the new method to that.
> 2. Create new plugin, which inherits OVSNeutronPlugin - the new plugin
> defines the new method, setup_rpc,...
> 3. Add the new method to the existing OVSNeutronAgent
>
> Please let me know your thought and comments.
>
> Regards,
> Nader.
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>