23f7da3021
In L2 agent extensions, when the agent extension needed access to a datastructure within the L2 agent, an agent extension API object was created. This API object would be the interface permitting agent extensions to have access to those objects internal to the L2 agent. This change implements a similar agent extension API object for the L3 agent extensions. This is necessary to allow L3 agent extensions to have access to the RouterInfo class, so that they can do lookups on it, for example determining the namespace for a specific router. Without this API object, the L3 agent extension would not have access to this structure. Co-Authored-By: Margaret Frances <margaret_frances@cable.comcast.com> Partially-Implements: blueprint l3-agent-extensions Change-Id: I85f89accbeefd820130335674fd56cb54f1449de
10 lines
335 B
YAML
10 lines
335 B
YAML
---
|
|
features:
|
|
- The neutron L3 agent now has the ability to load
|
|
agent extensions, which allows other services to
|
|
integrate without additional agent changes. An
|
|
API for exposing the l3 agent's router info data
|
|
to the extensions is also provided so that
|
|
extensions can remain consistent with router
|
|
state.
|