yahoo-eng-team team mailing list archive

[Ihar Hrachyshka <1517903@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

L2 agent extensions were introduced in Liberty. Currently they don't
have any way to influence agents that they run inside. For example,
there is no way they can set flows for OVS bridges, create new tables,
add patch ports, etc.

Multiple subprojects (SFC, BGP-VPN) expressed the need for such
mechanism that would allow them all mentioned above. Without it, they
are forced to patch the agent code, which does not help their adoption,
and makes Neutron platform more scattered.

The feature request was covered on one of Tokyo summit sessions. The
etherpad to track requests for the mechanism is at:
https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion

The current idea for the feature implementation is that extension
manager will receive an agent specific API object that would expose some
internals into extensions and provide stable API with all compatibility
guarantees. The manager will proxy the API object into extensions, and
then they will be able to use it as they see fit.

Current discussion goes around OVS agent only. The mechanism will allow
for other agent types to opt-in the mechanism as they see fit (stub API
objects with no actual interface exposed can be added to adopt the new
extensions API).

** Affects: neutron
     Importance: Wishlist
     Assignee: Ihar Hrachyshka (ihar-hrachyshka)
         Status: New


** Tags: rfe

** Changed in: neutron
   Importance: Undecided => Wishlist

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

Title:
  Add agent specific API for l2 agent extensions

Status in neutron:
  New

Bug description:
  L2 agent extensions were introduced in Liberty. Currently they don't
  have any way to influence agents that they run inside. For example,
  there is no way they can set flows for OVS bridges, create new tables,
  add patch ports, etc.

  Multiple subprojects (SFC, BGP-VPN) expressed the need for such
  mechanism that would allow them all mentioned above. Without it, they
  are forced to patch the agent code, which does not help their
  adoption, and makes Neutron platform more scattered.

  The feature request was covered on one of Tokyo summit sessions. The
  etherpad to track requests for the mechanism is at:
  https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion

  The current idea for the feature implementation is that extension
  manager will receive an agent specific API object that would expose
  some internals into extensions and provide stable API with all
  compatibility guarantees. The manager will proxy the API object into
  extensions, and then they will be able to use it as they see fit.

  Current discussion goes around OVS agent only. The mechanism will
  allow for other agent types to opt-in the mechanism as they see fit
  (stub API objects with no actual interface exposed can be added to
  adopt the new extensions API).

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