From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH-SERIES v2 qemu-server] Cleanup migration code and improve migration disk cleanup
Date: Mon, 19 Apr 2021 08:49:32 +0200 [thread overview]
Message-ID: <8b189efb-377a-4c98-786a-5cce1525f48f@proxmox.com> (raw)
In-Reply-To: <20210129151143.10014-1-f.ebner@proxmox.com>
Ping for this series.
Patch #13 conflicts with Mira's proposed change for copying the
conntrack information[0].
Patch #1 and Patch #5 are the only ones *not* conflicting with Fabian's
remote migration RFC[1].
[0]: https://lists.proxmox.com/pipermail/pve-devel/2021-February/046873.html
[1]: https://lists.proxmox.com/pipermail/pve-devel/2021-April/047600.html
Am 29.01.21 um 16:11 schrieb Fabian Ebner:
> This series intends to make the migration code more readable by
> simplyfing/unifying how we keep track of local volumes and splitting up
> sync_disks into multiple subroutines.
>
> This is done by keeping more information within the hash of local_volumes we
> obtain in the very beginning and re-using it later. Also a method to filter by
> migration/replication type is introduced, making it possible to get rid of some
> special-case handling when iterating over local volumes.
>
> Still more should be possible, but the series is getting big, so I stopped here.
> Namely, $self->{local_volumes}, $self->{volume_map} and $self->{target_drive}
> still have some overlap and it might be possible to merge them somehow.
>
> Also it might make sense to put abstract more things to the common code, one
> example is to make target storage mapping available for containers too.
>
>
> Changes from v1:
> * dropped already applied patches
> * rebased
> * prefix commit messages with 'migration' (and 'test')
> * increased test coverage a little, see patch #1 and patch #13
> * reordered patches #8+#9 to avoid temporary breakage, see
> patches #8 and patch #13 (added test-case) for the details
> * add patch to fix bandwidth limit calculation
> * add patch to split out run_replication from scan_local_volumes
> * add patch to improve error handling when block job finishing fails
>
>
> Fabian Ebner (13):
> test: migration: add parse_volume_id calls
> migration: split sync_disks into two functions
> migration: avoid re-scanning all volumes
> migration: split out config_update_local_disksizes from
> scan_local_volumes
> migration: fix calculation of bandwith limit for non-disk migration
> migration: save targetstorage and bwlimit in local_volumes hash and
> re-use information
> migration: add nbd migrated volumes to volume_map earlier
> migration: simplify removal of local volumes and get rid of
> self->{volumes}
> migration: cleanup_remotedisks: simplify and include more disks
> migration: use storage_migration for checks instead of
> online_local_volumes
> migration: keep track of replicated volumes via local_volumes
> migration: split out replication from scan_local_volumes
> migration: move finishing block jobs to phase2 for better/uniform
> error handling
>
> PVE/QemuMigrate.pm | 401 ++++++++++++++------------
> PVE/QemuServer.pm | 2 +
> test/MigrationTest/QemuMigrateMock.pm | 9 +
> test/MigrationTest/QmMock.pm | 2 +
> test/MigrationTest/Shared.pm | 4 +
> test/run_qemu_migrate_tests.pl | 40 ++-
> 6 files changed, 267 insertions(+), 191 deletions(-)
>
next prev parent reply other threads:[~2021-04-19 6:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 15:11 Fabian Ebner
2021-01-29 15:11 ` [pve-devel] [PATCH v2 qemu-server 01/13] test: migration: add parse_volume_id calls Fabian Ebner
2021-01-29 15:11 ` [pve-devel] [PATCH v2 qemu-server 02/13] migration: split sync_disks into two functions Fabian Ebner
2021-01-29 15:11 ` [pve-devel] [PATCH v2 qemu-server 03/13] migration: avoid re-scanning all volumes Fabian Ebner
2021-01-29 15:11 ` [pve-devel] [PATCH v2 qemu-server 04/13] migration: split out config_update_local_disksizes from scan_local_volumes Fabian Ebner
2021-01-29 15:11 ` [pve-devel] [PATCH v2 qemu-server 05/13] migration: fix calculation of bandwith limit for non-disk migration Fabian Ebner
2021-01-29 15:11 ` [pve-devel] [PATCH v2 qemu-server 06/13] migration: save targetstorage and bwlimit in local_volumes hash and re-use information Fabian Ebner
2021-01-29 15:11 ` [pve-devel] [PATCH v2 qemu-server 07/13] migration: add nbd migrated volumes to volume_map earlier Fabian Ebner
2021-01-29 15:11 ` [pve-devel] [PATCH v2 qemu-server 08/13] migration: simplify removal of local volumes and get rid of self->{volumes} Fabian Ebner
2021-01-29 15:11 ` [pve-devel] [PATCH v2 qemu-server 09/13] migration: cleanup_remotedisks: simplify and include more disks Fabian Ebner
2021-01-29 15:11 ` [pve-devel] [PATCH v2 qemu-server 10/13] migration: use storage_migration for checks instead of online_local_volumes Fabian Ebner
2021-01-29 15:11 ` [pve-devel] [PATCH v2 qemu-server 11/13] migration: keep track of replicated volumes via local_volumes Fabian Ebner
2021-01-29 15:11 ` [pve-devel] [PATCH v2 qemu-server 12/13] migration: split out replication from scan_local_volumes Fabian Ebner
2021-01-29 15:11 ` [pve-devel] [PATCH v2 qemu-server 13/13] migration: move finishing block jobs to phase2 for better/uniform error handling Fabian Ebner
2021-04-19 6:49 ` Fabian Ebner [this message]
2021-04-19 11:50 ` [pve-devel] applied-series: [PATCH-SERIES v2 qemu-server] Cleanup migration code and improve migration disk cleanup Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8b189efb-377a-4c98-786a-5cce1525f48f@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox