Neutron/ModularL2Agent - Revision history

Banix at 13:51, 6 May 2014

2014-05-06T13:51:52Z

Banix: /* Introduction */

2014-05-06T13:50:13Z

‎Introduction

Banix at 13:46, 6 May 2014

2014-05-06T13:46:08Z

Banix at 13:20, 6 May 2014

2014-05-06T13:20:55Z

Irenab: /* Comparison Chart */

2014-05-01T06:13:49Z

‎Comparison Chart

Banix at 15:56, 30 April 2014

2014-04-30T15:56:31Z

Banix at 21:11, 29 April 2014

2014-04-29T21:11:12Z

Banix: /* Comparison Chart */

2014-04-28T15:09:44Z

‎Comparison Chart

Yamamoto: /* Related documents */

2014-04-28T03:06:00Z

‎Related documents

Yamamoto at 03:05, 28 April 2014

2014-04-28T03:05:25Z

← Older revision		Revision as of 13:51, 6 May 2014
Line 7:		Line 7:
	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.		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.

		+	Here is the ether pad for the Juno design session: [https://etherpad.openstack.org/p/juno-neutron-modular-l2-agent juno/neutron/modular-l2-agent ]
	== Possible Directions ==		== Possible Directions ==

@@ Line 3: / Line 3: @@
 == 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.
+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. Furthermore, as more plugins and mechanism drivers are added, those which require L2 agents can benefit from a modular L2 agent and possibly use pieces of the agent that suits them.
-While the focus of the effort will be on L2 agents we may look into establishing a framework for all Neutron 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 ==

@@ Line 18: / Line 18: @@
 == Related Design Sessions and Blueprints ==
-* Support for mechanism driver specific extensions [https://blueprints.launchpad.net/neutron/+spec/neutron-ml2-mechanismdriver-extensions here]
+* Support for mechanism driver specific extensions: [https://etherpad.openstack.org/p/ML2_mechanismdriver_extensions_support design session] and [https://blueprints.launchpad.net/neutron/+spec/neutron-ml2-mechanismdriver-extensions blueprint]
-* DVR Progress Update session [https://etherpad.openstack.org/p/Distributed-Virtual-Router here]
+* DVR Progress Update session: [https://etherpad.openstack.org/p/Distributed-Virtual-Router design session]
-* Support for multiple OVS switches, one for each feature/extension [http://summit.openstack.org/cfp/details/391 here]
+* Support for multiple OVS switches, one for each feature/extension: [http://summit.openstack.org/cfp/details/391 here]
-* OVS based security groups [http://summit.openstack.org/cfp/details/155 here]
+* OVS based security groups: [http://summit.openstack.org/cfp/details/155 here]
-* Configuration agents [http://summit.openstack.org/cfp/details/409 here]
+* Configuration agents: [http://summit.openstack.org/cfp/details/409 here]
-* Device agents [http://summit.openstack.org/cfp/details/395 here]
+* Device agents: [http://summit.openstack.org/cfp/details/395 here]
 == Comparison Chart ==
@@ Line 44: / Line 44: @@
 | Flows
 | ovs-ofctl
+| -
+|
 | Embedded OF controller
@@ Line 51: / Line 51: @@
 | Local isolation
 | vlan tag
+| bridge/vlan
+|
 | Currently VLAN tag.  <br/> [https://blueprints.launchpad.net/neutron/+spec/ofagent-merge-bridges Planned: OF metadata]

@@ Line 19: / Line 19: @@
 * Support for mechanism driver specific extensions [https://blueprints.launchpad.net/neutron/+spec/neutron-ml2-mechanismdriver-extensions here]
 * Support for multiple OVS switches, one for each feature/extension [http://summit.openstack.org/cfp/details/391 here]
 * OVS based security groups [http://summit.openstack.org/cfp/details/155 here]

@@ Line 39: / Line 39: @@
 | Msvm
 | Currently ovsdb.  <br/> [https://blueprints.launchpad.net/neutron/+spec/ofagent-port-monitor Planned: OpenFlow]
+| OS
 |-
 | Flows
@@ Line 53: / Line 53: @@
+|
 | Currently VLAN tag.  <br/> [https://blueprints.launchpad.net/neutron/+spec/ofagent-merge-bridges Planned: OF metadata]
+| vlan tag
 |-
 ||
@@ Line 67: / Line 67: @@
 | Y
 | Y
-| Y
+| N
 |-
 | L2pop

← Older revision		Revision as of 21:11, 29 April 2014
Line 1:		Line 1:
		+	Here we are collecting information on possible directions wrt building a modular L2 agent.

−	~~Here we are collecting information on possible directions wrt building a modular L2 agent.~~	+	== Introduction ==

		+	== Dimensions
	== Comparison Chart ==		== Comparison Chart ==

@@ Line 16: / Line 16: @@
 | OS
 | Msvm
-| Currently ovsdb.  [https://blueprints.launchpad.net/neutron/+spec/ofagent-port-monitor Planned to use OpenFlow instead]
+| Currently ovsdb.  <br/> [https://blueprints.launchpad.net/neutron/+spec/ofagent-port-monitor Planned: OpenFlow]
+|
 |-
@@ Line 23: / Line 23: @@
+|
+|
-| Embedded OpenFlow controller
+| Embedded OF controller
+|
 |-
@@ Line 30: / Line 30: @@
+|
+|
-| Currently VLAN tag.  [https://blueprints.launchpad.net/neutron/+spec/ofagent-merge-bridges Planned to use OpenFlow metadata instead]
+| Currently VLAN tag.  <br/> [https://blueprints.launchpad.net/neutron/+spec/ofagent-merge-bridges Planned: OF metadata]
+|
 |-

← Older revision		Revision as of 03:06, 28 April 2014
Line 57:		Line 57:

	== Related documents ==		== Related documents ==
−	* A summary of the differences between ~~ova~~ and ofagent (current and planned) agents are listed [https://wiki.openstack.org/wiki/Neutron/OFAgent/ComparisonWithOVS here]	+	* A summary of the differences between openvswitch and ofagent (current and planned) agents are listed [https://wiki.openstack.org/wiki/Neutron/OFAgent/ComparisonWithOVS here]