However, the option wasn't enough to cover some supplementary traffic during the pre/post live-migration tasks and/or cold migration traffic. And a workaround has been implemented in to allow SSH both in the main and migration networks: https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1969971
The charm has support of assigning a dedicated network space for live_migration_ inbound_ addr already: /docs.openstack .org/nova/ latest/ configuration/ config. html#libvirt. live_migration_ inbound_ addr /bugs.launchpad .net/charm- nova-compute/ +bug/1680531
- https:/
- https:/
However, the option wasn't enough to cover some supplementary traffic during the pre/post live-migration tasks and/or cold migration traffic. And a workaround has been implemented in to allow SSH both in the main and migration networks: /bugs.launchpad .net/charm- nova-cloud- controller/ +bug/1969971
https:/
Now the upstream introduced a new config option "migration_ inbound_ addr" so we should support that to move those high-volume traffic from the main management network. /blueprints. launchpad. net/nova/ +spec/libvirt- migrate- with-hostname- instead- of-ip /docs.openstack .org/nova/ latest/ configuration/ config. html#libvirt. migration_ inbound_ addr
- https:/
- https:/