yahoo-eng-team team mailing list archive

[Nate Johnston <1580239@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Neutron advanced services (*aaS) projects need a standardized method to
gain access to resources internal to the L3 agent.  Previously, the
proper methodology was using inheritance from L3NATAgent and it's
subclasses.  But now it is necessary to decouple these things, so that
each *aaS can be a separate extension that registers with the L3 agent,
can interrogate the L3 agent for necessary information, and receives
notifications of events through callbacks.

Some examples of what this would enable FWaaS and other advanced
services to do are:

- The ability to map router_id to router info so we can program iptables to the correct namespace.
- The ability to load the Service Agent - so we have an RPC endpoint in the context of L3Agent.

FWaaS can then use the existing observer hierarchy pattern to listen for
notifications.  This would prevent the need to patch the agent code for
advanced services to function.

Note: This must be executed in such a way that multiple *aaS services
can plug in simultaneously without interfering with each other.

** Affects: neutron
     Importance: Wishlist
         Status: New


** Tags: rfe

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1580239

Title:
  Add agent extension framework for L3 agent

Status in neutron:
  New

Bug description:
  Neutron advanced services (*aaS) projects need a standardized method
  to gain access to resources internal to the L3 agent.  Previously, the
  proper methodology was using inheritance from L3NATAgent and it's
  subclasses.  But now it is necessary to decouple these things, so that
  each *aaS can be a separate extension that registers with the L3
  agent, can interrogate the L3 agent for necessary information, and
  receives notifications of events through callbacks.

  Some examples of what this would enable FWaaS and other advanced
  services to do are:

  - The ability to map router_id to router info so we can program iptables to the correct namespace.
  - The ability to load the Service Agent - so we have an RPC endpoint in the context of L3Agent.

  FWaaS can then use the existing observer hierarchy pattern to listen
  for notifications.  This would prevent the need to patch the agent
  code for advanced services to function.

  Note: This must be executed in such a way that multiple *aaS services
  can plug in simultaneously without interfering with each other.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1580239/+subscriptions