public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Stefan Hanreich <s.hanreich@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-container/qemu-server/pve-guest-common/pve-docs 0/1] Add pre/post-migrate hooks
Date: Mon, 26 Sep 2022 17:51:09 +0200	[thread overview]
Message-ID: <e6a53350-79f4-b3ec-7f65-663af9aa9171@proxmox.com> (raw)
In-Reply-To: <20220922141321.1510795-1-s.hanreich@proxmox.com>

Am 22/09/2022 um 16:13 schrieb Stefan Hanreich:
> I have decided to create distinct event types for source/target nodes, since
> otherwise the same script would run essentially twice on the source/target node.
> With distinct event types, the hooks should be more flexible in their usage.

just make that a parameter, same flexibility but less cmd explosion and complexity.

Also, _iff_ (see reply  we keep the CLI entries for pct/qm it should just be a single command
there, any difference should be handled in the parameters; it's internal after all
and we want to avoid that there's more internal commands then externals someday ;)

Target and source should be part of the parameters on either call (pre/post, src/target),
it is relevant info and should be easily available. Some param info like offline/online
migration could be relevant too, but we can always extend on that, so in that regard it
can be fine to stop smaller, to avoid going over board and having to keep all that info
for backward compat. Any parameter would need to be encoded in the example then.

Some more general note, the example is better than nothing, but a nice list/table
directly in the docs would be really good to have. This could be done upfront, before
adding new hooks - best for now to duplicate it for both CT and VM chapter (if sensible
it can live in its own guest-hook-list.adoc and just get included twice). Including
the example script as an appendix would be a nice touch too.




  parent reply	other threads:[~2022-09-26 15:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 14:13 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 ` [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 ` Thomas Lamprecht [this message]
2022-09-27  7:40   ` [pve-devel] [PATCH pve-container/qemu-server/pve-guest-common/pve-docs 0/1] Add pre/post-migrate hooks 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=e6a53350-79f4-b3ec-7f65-663af9aa9171@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.hanreich@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal