From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs 1/1] Add pre/post-migrate events for target and source to example hookscript
Date: Thu, 22 Sep 2022 16:13:20 +0200 [thread overview]
Message-ID: <20220922141321.1510795-4-s.hanreich@proxmox.com> (raw)
In-Reply-To: <20220922141321.1510795-1-s.hanreich@proxmox.com>
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
examples/guest-example-hookscript.pl | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/examples/guest-example-hookscript.pl b/examples/guest-example-hookscript.pl
index adeed59..e4adf6d 100755
--- a/examples/guest-example-hookscript.pl
+++ b/examples/guest-example-hookscript.pl
@@ -54,6 +54,34 @@ if ($phase eq 'pre-start') {
print "$vmid stopped. Doing cleanup.\n";
+} elsif ($phase eq 'pre-migrate-source') {
+
+ # Phase 'pre-migrate-source' will be run before a migration on the source
+ # node of the VM/CT
+
+ print "preparing $vmid for migration on source.\n";
+
+} elsif ($phase eq 'post-migrate-source') {
+
+ # Phase 'post-migrate-source' will be run after a migration on the source
+ # node of the VM/CT
+
+ print "$vmid finished migrating on source.\n";
+
+} elsif ($phase eq 'pre-migrate-target') {
+
+ # Phase 'pre-migrate-target' will be run before a migration on the target
+ # node of the VM/CT
+
+ print "preparing $vmid for migration on target.\n";
+
+} elsif ($phase eq 'post-migrate-target') {
+
+ # Phase 'post-migrate-target' will be run after a migration on the target
+ # node of the VM/CT
+
+ print "$vmid finished migrating on target.\n";
+
} else {
die "got unknown phase '$phase'\n";
}
--
2.30.2
next prev parent reply other threads:[~2022-09-22 14:13 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 pre/post-migrate hooks 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
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 ` Stefan Hanreich [this message]
2022-09-22 14:13 ` [pve-devel] [PATCH qemu-server 1/1] Add VM " 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=20220922141321.1510795-4-s.hanreich@proxmox.com \
--to=s.hanreich@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.