From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 manager 2/2] close #3476: vzdump: add job-init hook
Date: Mon, 17 Jan 2022 16:54:07 +0100 [thread overview]
Message-ID: <7bf45434-3b45-da5e-6ca4-e187bc87cdca@proxmox.com> (raw)
In-Reply-To: <1642433537.xfl9w24g55.astroid@nora.none>
On 17.01.22 16:37, Fabian Grünbichler wrote:
> On January 17, 2022 12:35 pm, Fabian Ebner wrote:
>> which allows users to prepare the backup storage for activation (e.g.
>> by waking up a remote node).
>>
>> Suggested-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
>> Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
>
> Reviewed-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
>
> but giving others a chance to object to the new phase before applying ;)
For the general approach of adding this hook
Acked-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
>> @@ -26,6 +28,14 @@ if ($phase eq 'job-start' ||
>> print "storeid=$storeid;" if defined($storeid);
>> print "\n";
>>
>> + # example: wake up remote storage node and enable storage
>> + if ($phase eq 'job-init') {
>> + #system ("") == 0 ||
nit: maybe add a command there so that it's easier to adapt for non-perl people, whom
may not know that above is not some required magic incantation that they must keep as
is. So, e.g.:
#system("wakeonlan AA:BB:CC:DD:EE:FF")
#sleep(30);
but as said, just a nit that caught my eyes, no hard feelings on that whatsoever.
next prev parent reply other threads:[~2022-01-17 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 11:35 [pve-devel] [PATCH v2 manager 1/2] vzdump: example hook script: avoid undef warnings Fabian Ebner
2022-01-17 11:35 ` [pve-devel] [PATCH v2 manager 2/2] close #3476: vzdump: add job-init hook Fabian Ebner
2022-01-17 15:37 ` Fabian Grünbichler
2022-01-17 15:54 ` Thomas Lamprecht [this message]
2022-01-17 15:32 ` [pve-devel] applied: [PATCH v2 manager 1/2] vzdump: example hook script: avoid undef warnings Fabian Grünbichler
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=7bf45434-3b45-da5e-6ca4-e187bc87cdca@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.gruenbichler@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