Difference between revisions of "Neutron/OFAgent/ComparisonWithOVS"
| Line 32: | Line 32: | ||
|- | |- | ||
| Device ID | | Device ID | ||
| − | | Neutron port ID (UUID) | + | | Neutron port ID (UUID) stored in ovsdb |
| − | | Port name | + | | Port name as linuxbridge ([https://blueprints.launchpad.net/neutron/+spec/ofagent-port-monitor planned]) |
|- | |- | ||
| "internal" VLAN | | "internal" VLAN | ||
Revision as of 06:36, 25 April 2014
Two neutron agents, openvswitch and ofagent, implement mostly same functionalities in different ways. The following is a summary of the differences.
| openvswitch | ofagent | |
| Advantages | Can provide better performance using Open vSwitch(OVS) specific advanced features | More portable to switches other than OVS. Easier to handle asynchronous messages because it's a full featured OpenFlow controller. |
| OpenFlow version | OpenFlow 1.0 + Nicira Extensions (NX) | OpenFlow 1.3 without vendor extensions |
| How to program switch? | Invoke ovs-ofctl command | An OpenFlow controller embedded in the agent sends messages to the switch |
| Supported switches | OVS only. Thus can use OVS-specific advanced features like NX and patch ports. | OpenFlow 1.3 switches including OVS (planned) |
| Neutron plugin | openvswitch plugin (planned to be deprecated) or ML2 plugin | ML2 plugin |
| Port monitoring | Periodic poll of ovsdb via ovs-vsctl command | OpenFlow port statistics and notification (planned) |
| Device ID | Neutron port ID (UUID) stored in ovsdb | Port name as linuxbridge (planned) |
| "internal" VLAN | 802.1q tagged VLAN | OpenFlow metadata (planned) |
| Local ARP responder | Install NX flows for each FDB entries (planned) | The embedded OpenFlow controller handles packet-ins and sends back ARP responses (planned) |
