71b6c8c5f7
The live_migration_uri option that was being used in case TLS is used in live migration doesn't permit the usage of a host other than the one detected automatically by nova. This is problematic for cases like TLS where the address needs to match the certificate's SubjectAltName entry. So instead, this patch takes into use the two recommended options: * live_migration_inbound_addr * live_migration_scheme These will be used by nova to determine the URI. On the other hand, libvirt_migration_uri is set to be deprecated at some point. But, a way to add the query parameters to the query is needed before this happens. Change-Id: I0a1684397ebefaa8dc00237e0b7952e9296381fa
12 lines
667 B
YAML
12 lines
667 B
YAML
---
|
|
features:
|
|
- The paremeter 'live_migration_inbound_addr' was introduced to the libvirt
|
|
live migration module. This sets the configuration option with the same
|
|
name in the nova configuration, in the 'libvirt' section.
|
|
- If TLS is enabled for libvirt's live migration, the module will set the
|
|
configuration option named 'live_migration_scheme' in the 'libvirt' section
|
|
to have the value 'tls'. This will be used by nova to form the scheme for
|
|
the live migration URI, e.g. 'qemu+tls://...'.
|
|
- Note that the usage of 'live_migratin_inbound_addr' doesn't permit adding
|
|
extra parameters to the live migration URI as of the writing of this.
|