Neutron/OFAgent/Todo


 * OFAgent Todo
 * Reduce OVS dependencies
 * OVSDB
 * bridge identity
 * currently bridges are identified by name (eg. br-int)
 * it's more portable to use datapath-id
 * or use OFPMP_DESC dp_desc? Note: OVS returns "None" by default.
 * add-br, set-controller, set bridge protocols
 * factor out to "OVS" sub-driver
 * use OF-Config
 * move the one-time setup code to devstack
 * tunnel ports
 * ideally use OF-Config
 * but this likely remains switch-dependant
 * factor out the code into "OVS" sub-driver.
 * https://blueprints.launchpad.net/neutron/+spec/ofagent-sub-driver
 * the way to configure physical networks
 * remove bridge_mapping in Kilo
 * stop assuming the existence of local ports
 * not a big deal
 * neutron interface driver
 * ideally use OF-Config
 * investigate if the existing IVS driver is usable for our purpose, at least for IVS.
 * nova interface driver
 * ideally use OF-Config
 * investigate if the existing IVS driver is usable for our purpose, at least for IVS.
 * probably it's better to avoid touching libvirt unless absolutely necessary
 * security group. ideally implement with flows.
 * cf. similar BP for OVS agent https://wiki.openstack.org/wiki/Neutron/blueprint_ovs-firewall-driver