f924bfb418
This change resolves a long standing issue where a container's mac address regenerates when it was restarted. In most cases when a container is restarted and it's mac address is rotated and nothing bad happens; mac learning will resolve itself given enough time in just about all situations. However services like neutron-agents are long lived and are highly sensitive to network changes. These types of services expect consistent hardware addressing and when mac addresses rotate may become confused. To limit the possibility of prolonged downtime caused by mac address rotation on network sensitive containers an option has been created to allow a container to have a fixed mac address. If this option is enabled the container will generate fixed addresses for all networks assosiated with the specific container. The option is `lxc_container_fixed_mac` and it has a default value of "false". Change-Id: Ie1a8dc172c45fc2b4cfa724a2bafa67cb481ba73 Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
16 lines
757 B
YAML
16 lines
757 B
YAML
---
|
|
features:
|
|
- LXC containers will now generate a fixed mac address on all
|
|
network interfaces when the option `lxc_container_fixed_mac`
|
|
is set to **true**. This feature was implemented to resolve
|
|
issues with dynamic mac addresses in containers generally
|
|
experienced at scale with network intensive services.
|
|
fixes:
|
|
- LXC containers will now have the ability to use a fixed mac
|
|
address on all network interfaces when the option
|
|
`lxc_container_fixed_mac` is set **true**. This change will
|
|
assist in resolving a long standing issue where network intensive
|
|
services, such as neutron and rabbitmq, can enter a confused state
|
|
for long periods of time and require rolling restarts or internal
|
|
system resets to recover.
|