Deprecate external_network_bridge option in L3 agent
This option provides another way to attach to a specific bridge
that is not quite equivalent with how bridge_mappings work in the
L2 agent. This creates inconsistencies between how the L3 agent
behaves when configured with a bridge_mapping and provider properties
of the Neutron network vs. when it just ignores all L2 stuff and
plugs itself directly into the bridge.
Reviewed: https:/ /review. openstack. org/219928 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=5aab6a57795 0525d8f656d373f 2e46a229fa600b
Committed: https:/
Submitter: Jenkins
Branch: master
commit 5aab6a577950525 d8f656d373f2e46 a229fa600b
Author: Kevin Benton <email address hidden>
Date: Tue Sep 1 19:35:33 2015 -0700
Deprecate external_ network_ bridge option in L3 agent
This option provides another way to attach to a specific bridge
that is not quite equivalent with how bridge_mappings work in the
L2 agent. This creates inconsistencies between how the L3 agent
behaves when configured with a bridge_mapping and provider properties
of the Neutron network vs. when it just ignores all L2 stuff and
plugs itself directly into the bridge.
See the bug report for more info.
Change-Id: I37de3cd6eaaf34 856fa72753f471f 4f0a9381836
Closes-Bug: #1491668