2015-08-04 18:48:41 |
Matt Kassawara |
bug |
|
|
added bug |
2015-08-04 18:57:38 |
Sridhar Gaddam |
bug |
|
|
added subscriber Sridhar Gaddam |
2015-08-04 19:15:41 |
Assaf Muller |
bug |
|
|
added subscriber Assaf Muller |
2015-08-11 13:03:58 |
John Schwarz |
neutron: assignee |
|
John Schwarz (jschwarz) |
|
2015-08-11 15:06:41 |
Assaf Muller |
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. |
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: physnet label and segmentation type. |
|
2015-08-12 13:06:35 |
OpenStack Infra |
neutron: status |
New |
In Progress |
|
2015-08-14 02:03:50 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Committed |
|
2015-08-31 12:10:18 |
OpenStack Infra |
tags |
l3-ha rfe |
in-feature-pecan l3-ha rfe |
|
2015-09-03 19:12:07 |
Thierry Carrez |
neutron: status |
Fix Committed |
Fix Released |
|
2015-09-03 19:12:07 |
Thierry Carrez |
neutron: milestone |
|
liberty-3 |
|
2015-09-12 01:37:59 |
Assaf Muller |
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: physnet label and segmentation type. |
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, such that the HA networks will use tunneling while tenant networks use VLANs or vice versa. Alternatively, the physical_network tag of the HA networks may need to be selected so that HA networks will use a separate or different NIC. |
|
2015-09-21 18:46:20 |
OpenStack Infra |
tags |
in-feature-pecan l3-ha rfe |
in-feature-pecan in-stable-kilo l3-ha rfe |
|
2015-10-11 18:31:00 |
Chuck Short |
nominated for series |
|
neutron/kilo |
|
2015-10-11 18:31:00 |
Chuck Short |
bug task added |
|
neutron/kilo |
|
2015-10-11 18:31:17 |
Chuck Short |
neutron/kilo: status |
New |
Fix Committed |
|
2015-10-11 18:31:17 |
Chuck Short |
neutron/kilo: milestone |
|
2015.1.2 |
|
2015-10-13 19:30:11 |
Chuck Short |
neutron/kilo: status |
Fix Committed |
Fix Released |
|
2015-10-15 12:33:05 |
Thierry Carrez |
neutron: milestone |
liberty-3 |
7.0.0 |
|