Difference between revisions of "Neutron/OFAgent"
< Neutron
Line 14: | Line 14: | ||
*** port-based VLAN | *** port-based VLAN | ||
**** install appropriate flows to push/pop tags. | **** install appropriate flows to push/pop tags. | ||
− | *** tunnel ports | + | *** tunnel ports |
+ | **** factor out the code into "OVS" sub-driver. | ||
*** the way to configure physical networks | *** the way to configure physical networks | ||
**** it would be more straightforward to specify an interface (eth0) rather than a bridge (br-eth0) | **** it would be more straightforward to specify an interface (eth0) rather than a bridge (br-eth0) |
Revision as of 04:13, 14 April 2014
OFAgent is a neutron core-plugin (ML2 mechanism driver) aims to support pure OpenFlow1.3 switches.
- Todo
- Reduce OVS dependencies
- patch ports, multiple logical bridges
- https://blueprints.launchpad.net/neutron/+spec/ofagent-merge-bridges
- https://wiki.openstack.org/wiki/Neutron/OFAgent/FlowTable
- implement learning based on flows and packet-in. possibly with l2pop.
- OVSDB
- port scanning
- use port desc and ofp_port_status instead
- port external id
- probably use tapXXXX, which is available as ofp_port.name. ML2 plugin already accepts tapXXXX for linuxbridge.
- port scanning
- port-based VLAN
- install appropriate flows to push/pop tags.
- tunnel ports
- factor out the code into "OVS" sub-driver.
- the way to configure physical networks
- it would be more straightforward to specify an interface (eth0) rather than a bridge (br-eth0)
- stop assuming the existence of local ports
- eg. setup_physical_bridges
- patch ports, multiple logical bridges
- neutron interface driver
- nova interface driver
- security group. ideally implement with flows.
- l2pop
- Reduce OVS dependencies