| 2024-02-29 00:43:12 |
Nobuto Murata |
bug |
|
|
added bug |
| 2024-02-29 00:43:48 |
Nobuto Murata |
description |
The charm has support of assigning a dedicated network space for live_migration_inbound_addr already:
- https://docs.openstack.org/nova/latest/configuration/config.html#libvirt.live_migration_inbound_addr
- https://bugs.launchpad.net/charm-nova-compute/+bug/1680531
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
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.
- https://blueprints.launchpad.net/nova/+spec/libvirt-migrate-with-hostname-instead-of-ip
- https://docs.openstack.org/nova/latest/configuration/config.html#libvirt.migration_inbound_addr |
The charm has support of assigning a dedicated network space for live_migration_inbound_addr already:
- https://docs.openstack.org/nova/latest/configuration/config.html#libvirt.live_migration_inbound_addr
- https://bugs.launchpad.net/charm-nova-compute/+bug/1680531
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 to allow SSH both in the main and migration networks in:
https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1969971
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.
- https://blueprints.launchpad.net/nova/+spec/libvirt-migrate-with-hostname-instead-of-ip
- https://docs.openstack.org/nova/latest/configuration/config.html#libvirt.migration_inbound_addr |
|
| 2024-02-29 00:45:15 |
Nobuto Murata |
description |
The charm has support of assigning a dedicated network space for live_migration_inbound_addr already:
- https://docs.openstack.org/nova/latest/configuration/config.html#libvirt.live_migration_inbound_addr
- https://bugs.launchpad.net/charm-nova-compute/+bug/1680531
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 to allow SSH both in the main and migration networks in:
https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1969971
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.
- https://blueprints.launchpad.net/nova/+spec/libvirt-migrate-with-hostname-instead-of-ip
- https://docs.openstack.org/nova/latest/configuration/config.html#libvirt.migration_inbound_addr |
The charm has support of assigning a dedicated network space for live_migration_inbound_addr already:
- https://docs.openstack.org/nova/latest/configuration/config.html#libvirt.live_migration_inbound_addr
- https://bugs.launchpad.net/charm-nova-compute/+bug/1680531
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 to allow SSH both in the main and migration networks in:
https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1969971
Now the upstream introduced a new config option "migration_inbound_addr" (for 2024.1) so we should support that to move out those high-volume traffic from the main management network.
- https://blueprints.launchpad.net/nova/+spec/libvirt-migrate-with-hostname-instead-of-ip
- https://docs.openstack.org/nova/latest/configuration/config.html#libvirt.migration_inbound_addr |
|
| 2024-03-03 12:19:55 |
Alex Kavanagh |
charm-nova-compute: importance |
Undecided |
Wishlist |
|
| 2024-03-03 12:19:55 |
Alex Kavanagh |
charm-nova-compute: status |
New |
Triaged |
|
| 2024-03-04 06:46:27 |
DUFOUR Olivier |
bug |
|
|
added subscriber DUFOUR Olivier |
