Difference between revisions of "Neutron/ModularL2Agent"

Revision as of 13:46, 6 May 2014

Here we are collecting information on possible directions wrt building a modular L2 agent.

Introduction

As the number of L2 agents increase and considering similarities between these agents, we are making an effort to identify possible strategies for building a unified L2 agent where we reduce the amount of redundant code currently used by L2 agents. This effort aims to design and develop a framework for reducing the cost of maintaining the agent code and reducing the effort required for building a new agent. Furthermore, we will look into possible opportunities in improving the performance and stability of agents.

While the focus of the effort will be on L2 agents we may look into establishing a framework for all Neutron agents.

Possible Directions

Agent Drivers

One of the possible directions is to model the L2 agent after how ML2 plugin is organized and provide support for "drivers."

Extension Drivers

Another direction is to separate the support for the core API and that for extensions being supported by the plugin. Right now security groups and l2pop use the L2 agent and with the proposal for supporting arbitrary number of extensions by the ML2 plugin and mechanism drivers, other extensions may require support from the L2 agent. One possible solution is having pluggable drivers for every extension. The outstanding issue to resolve is the coordination mechanism between these drivers.

Related Design Sessions and Blueprints

• Support for mechanism driver specific extensions: design session and blueprint
• DVR Progress Update session: design session
• Support for multiple OVS switches, one for each feature/extension: here
• OVS based security groups: here
• Configuration agents: here
• Device agents: here

Comparison Chart

Related documents

• A summary of the differences between openvswitch and ofagent (current and planned) agents are listed here