Public bug reported:
The L3 HA mechanism creates a project network for HA (VRRP) traffic
among routers. The HA project network uses the first (default) network
type in 'tenant_network_types' and next available segmentation ID.
Depending on the environment, this combination may not provide a
desirable path for HA traffic. For example, some operators may prefer to
use a specific network for HA traffic to prevent split-brain issues.
Please consider adding configurability for HA networks such as
bridge/interface mapping, network type, and segmentation ID range.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: l3-ha rfe
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1481443
Title:
Add configurability for HA networks in L3 HA
Status in neutron:
New
Bug description:
The L3 HA mechanism creates a project network for HA (VRRP) traffic
among routers. The HA project network uses the first (default)
network type in 'tenant_network_types' and next available segmentation
ID. Depending on the environment, this combination may not provide a
desirable path for HA traffic. For example, some operators may prefer
to use a specific network for HA traffic to prevent split-brain
issues. Please consider adding configurability for HA networks such as
bridge/interface mapping, network type, and segmentation ID range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1481443/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
