Kevin Carter f924bfb418 Add an option to generate fixed MAC addresses ... 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>		2016-10-15 05:30:47 +00:00
..
autodev.j2	IRR for lxc_container_create	2015-11-03 08:00:45 -06:00
container-interface.ini.j2	Add an option to generate fixed MAC addresses	2016-10-15 05:30:47 +00:00
container-setup.sh.j2	Change the container prep using more intelligent commands	2016-09-15 02:34:10 +00:00
debian-interface.cfg.j2	Change the container prep using more intelligent commands	2016-09-15 02:34:10 +00:00
environment.j2	Template /etc/environment rather than use lineinfile	2016-05-03 14:17:49 +00:00
rhel-interface.j2	Change the container prep using more intelligent commands	2016-09-15 02:34:10 +00:00
rhel-routes.j2	Change the container prep using more intelligent commands	2016-09-15 02:34:10 +00:00
veth-cleanup.sh.j2	Don't fail veth-cleanup template when no container_networks	2016-10-14 12:09:22 -05:00