Andrew Bonney 71f3fb224a Use Nova management IP for live migrations ... Our installation uses separate networks for deployment and for OpenStack management. By default, live migrations depend upon a hostname, which resolves to an IP on our (lower speed) deployment network. Dependent on the deployment, the hostname may not be a reliable mechanism for determining the correct network for live migrations. Nova exposes a live_migration_inbound_addr which can be used to correct this. This patch defaults the inbound_addr to match the Nova service bind address, but provides the option for it to be overwritten through variables. Whilst the Nova docs suggest that live_migration_inbound_addr is ignored when live_migration_tunnelled is enabled this appears to be inaccurate from our testing. Change-Id: Iff6326f72971364d275ea999418d476007690ef8 Related-Bug: #1576724		2020-07-16 14:46:21 +01:00
..
libvirtd.conf.j2	Add CentOS support for os_nova	2016-11-15 08:10:56 -05:00
nova-key-insert.sh.j2	Clean final newline when distributing SSH keys	2016-08-22 10:05:20 -03:00
nova.conf.j2	Use Nova management IP for live migrations	2020-07-16 14:46:21 +01:00
qemu.conf.j2	remove the use of iteritems	2017-08-02 15:07:37 -05:00
sudoers.j2	Add privsep-helper to nova sudoers file	2019-03-31 21:24:27 -04:00
vendor_data.json.j2	Added vendor_data.json support	2018-03-06 14:57:40 -05:00