Set live_migration_inbound_addr for ssh transport

Currently this is only set when TLS is enabled, which means that with the ssh
transport we cannot control the network used, and we are relying on DNS or
hosts file to be correct, which is not guaranteed (especially with DNS).

Related-Bug: 1765462
Depends-On: Ifdc5fbd05195604ab6ea6564d0905f9385c6df67
Change-Id: I89011d06233dafb5ca3bbb45431387ebda521711
This commit is contained in:
Oliver Walsh 2018-04-19 21:09:20 +01:00
parent 4e1e6528c7
commit 9faea7204c
2 changed files with 16 additions and 1 deletions

View File

@ -276,7 +276,13 @@ outputs:
template: "libvirt/%{hiera('fqdn_NETWORK')}"
params:
NETWORK: {get_param: [ServiceNetMap, NovaLibvirtNetwork]}
- {}
-
nova::migration::libvirt::live_migration_inbound_addr:
str_replace:
template:
"%{hiera('$NETWORK')}"
params:
$NETWORK: {get_param: [ServiceNetMap, NovaLibvirtNetwork]}
-
if:
- use_tls_for_vnc

View File

@ -0,0 +1,9 @@
---
fixes:
- |
Set live_migration_inbound_addr for ssh transport
Previously this was only set when TLS is enabled, which means that with the ssh
transport we could not control the network used, and were relying on DNS or
hosts file to be correct, which is not guaranteed (especially with DNS).