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
71f3fb224a