A possible "simplification" might be to combine the openvswitch [bridge_mappings] and [bridge_mappings_interface] properties into a single entity. For example, instead of "Comma-separated list of <physical_network>:<bridge> tuples" it could be a "Comma-separated list of <physical_network>:<bridge>:<interface> triples".
The first 2 of this triple would be placed in the "bridge_mappings" field of ovs_neutron_plugin.ini. The last 2 fields would be used by the IP movement logic to create the necessary OVS bridge(s).
A possible "simplification" might be to combine the openvswitch [bridge_mappings] and [bridge_ mappings_ interface] properties into a single entity. For example, instead of "Comma-separated list of <physical_ network> :<bridge> tuples" it could be a "Comma-separated list of <physical_ network> :<bridge> :<interface> triples".
The first 2 of this triple would be placed in the "bridge_mappings" field of ovs_neutron_ plugin. ini. The last 2 fields would be used by the IP movement logic to create the necessary OVS bridge(s).