yahoo-eng-team team mailing list archive

[Paul Michali <1433552@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

This bug is to do some cleanup refactoring of the *aaS and L3 agent
interactions. It has several goals:

1) Switch from the L3EventObservers to the CallbacksManager mechanism for all *aaS agents.
2) Remove/reduce the dependency of *aaS agents on the L3 agent
3) Eliminate the AdvancedService base class
4) Eliminate the *(now) unused advanced_service.py and event_observer.py modules.

This will reduce from having two separate mechanisms to manage callbacks
from the L3 agent to the *aaS agents and their device drivers. (#1, #4)

It also simplifies the code. Instead of the classes, like VPNService,
from handling callbacks, forwarding calls to L3 agent to get router info
(removed in previous refactoring), maintaining another copy of L3 agent
and config settings( #2), and loading device drivers, the classes can
focus just on driver loading. Will no longer need a class hierarchy for
this as well (#3)

** Affects: neutron
     Importance: Undecided
     Assignee: Paul Michali (pcm)
         Status: In Progress


** Tags: vpnaas

** Changed in: neutron
     Assignee: (unassigned) => Paul Michali (pcm)

** Changed in: neutron
       Status: New => In Progress

** Summary changed:

- Refactor *aaS and L2 agent interaction
+ Refactor *aaS and L3 agent interaction

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

Title:
  Refactor *aaS and L3 agent interaction

Status in OpenStack Neutron (virtual network service):
  In Progress

Bug description:
  This bug is to do some cleanup refactoring of the *aaS and L3 agent
  interactions. It has several goals:

  1) Switch from the L3EventObservers to the CallbacksManager mechanism for all *aaS agents.
  2) Remove/reduce the dependency of *aaS agents on the L3 agent
  3) Eliminate the AdvancedService base class
  4) Eliminate the *(now) unused advanced_service.py and event_observer.py modules.

  This will reduce from having two separate mechanisms to manage
  callbacks from the L3 agent to the *aaS agents and their device
  drivers. (#1, #4)

  It also simplifies the code. Instead of the classes, like VPNService,
  from handling callbacks, forwarding calls to L3 agent to get router
  info (removed in previous refactoring), maintaining another copy of L3
  agent and config settings( #2), and loading device drivers, the
  classes can focus just on driver loading. Will no longer need a class
  hierarchy for this as well (#3)

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