From: Stefan Hanreich <s.hanreich@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-guest-common 1/1] Add abstract methods for pre/post-migrate hooks
Date: Tue, 27 Sep 2022 09:40:31 +0200 [thread overview]
Message-ID: <33c05af8-058d-6056-7d9d-9b731b4de58b@proxmox.com> (raw)
In-Reply-To: <953a9847-4560-495f-6c2f-62f2b1696793@proxmox.com>
On 9/26/22 17:27, Thomas Lamprecht wrote:
> Am 22/09/2022 um 16:13 schrieb Stefan Hanreich:
>> Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
>> ---
>> src/PVE/AbstractMigrate.pm | 14 ++++++++++++++
>> 1 file changed, 14 insertions(+)
>>
>
> for the record, if we do it like this (not much rationale given in the commit message)
> this breaks containers and qemu-server without such an implementation and needs the
> respective Breaks/Depends entries in d/control (which you cannot add as you cannot
> predict the exact version this would get actually added).
>
I figured this might pose some problems when releasing. Is there any way
I can work around this (also for future patches)? Or do we have to bump
all 3 packages at once? Anything I should change in particular in this
case (if we stick to having the hooks in the common package..)
Do you think it might be smarter to move the hooks into the respective
backend? It shouldn't be too much of a hassle. Maybe it is a smarter
idea after all, since it allows for more fine-grained control of when
the hooks should be run exactly.
>> diff --git a/src/PVE/AbstractMigrate.pm b/src/PVE/AbstractMigrate.pm
>> index d90e5b7..5e03488 100644
>> --- a/src/PVE/AbstractMigrate.pm
>> +++ b/src/PVE/AbstractMigrate.pm
>> @@ -178,6 +178,8 @@ sub migrate {
>> "public key authentication\n" if $@;
>> }
>>
>> + $self->pre_migration_hooks($self->{vmid});
>> +
>> &$eval_int($self, sub { $self->phase1($self->{vmid}); });
>> my $err = $@;
>> if ($err) {
>> @@ -228,6 +230,8 @@ sub migrate {
>> $self->log('err', $err);
>> $self->{errors} = 1;
>> }
>> +
>> + $self->post_migration_hooks($self->{vmid});
>> })};
>>
>> my $err = $@;
>> @@ -368,4 +372,14 @@ sub get_bwlimit {
>> return $bwlimit;
>> }
>>
>> +sub pre_migration_hooks {
>> + my ($self, $vmid) = @_;
>> + die "abstract method - implement me";
>> +}
>> +
>> +sub post_migration_hooks {
>> + my ($self, $vmid) = @_;
>> + die "abstract method - implement me";
>> +}
>> +
>> 1;
>
next prev parent reply other threads:[~2022-09-27 7:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 14:13 [pve-devel] [PATCH pve-container/qemu-server/pve-guest-common/pve-docs 0/1] Add " Stefan Hanreich
2022-09-22 14:13 ` [pve-devel] [PATCH pve-guest-common 1/1] Add abstract methods for " Stefan Hanreich
2022-09-26 15:27 ` Thomas Lamprecht
2022-09-27 7:40 ` Stefan Hanreich [this message]
2022-09-27 8:05 ` Thomas Lamprecht
2022-09-22 14:13 ` [pve-devel] [PATCH pve-container 1/1] Add CT hooks for pre/post-migrate on target/source Stefan Hanreich
2022-09-22 14:13 ` [pve-devel] [PATCH pve-docs 1/1] Add pre/post-migrate events for target and source to example hookscript Stefan Hanreich
2022-09-22 14:13 ` [pve-devel] [PATCH qemu-server 1/1] Add VM hooks for pre/post-migrate on target/source Stefan Hanreich
2022-09-26 15:38 ` Thomas Lamprecht
2022-09-27 7:40 ` Stefan Hanreich
2022-09-26 15:51 ` [pve-devel] [PATCH pve-container/qemu-server/pve-guest-common/pve-docs 0/1] Add pre/post-migrate hooks Thomas Lamprecht
2022-09-27 7:40 ` Stefan Hanreich
2022-09-27 7:47 ` 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=33c05af8-058d-6056-7d9d-9b731b4de58b@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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