all lists on 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>,
	Lukas Wagner <l.wagner@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-cluster 1/1] notify: add common_template_data
Date: Thu, 27 Mar 2025 16:31:40 +0100	[thread overview]
Message-ID: <79bed8e2-741b-49f9-b6cf-cb0d740fe692@proxmox.com> (raw)
In-Reply-To: <20250327142320.247169-2-l.wagner@proxmox.com>

Am 27.03.25 um 15:23 schrieb Lukas Wagner:
> This commit add the `common_template_data` sub to PVE::Notify,
> providing a convenient way to get a hash with properties that
> should be accessible from all templates, namely hostname, fqdn
> and cluster-name.
> 
> Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
> ---
>  src/PVE/Notify.pm | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
> 
> diff --git a/src/PVE/Notify.pm b/src/PVE/Notify.pm
> index c514111..9f7a74c 100644
> --- a/src/PVE/Notify.pm
> +++ b/src/PVE/Notify.pm
> @@ -4,6 +4,7 @@ use strict;
>  use warnings;
>  
>  use PVE::Cluster qw(cfs_register_file cfs_read_file cfs_lock_file cfs_write_file);
> +use PVE::INotify;
>  use Proxmox::RS::Notify;
>  
>  cfs_register_file(
> @@ -130,4 +131,23 @@ sub check_may_use_target {
>      }
>  }
>  
> +sub common_template_data {
> +    my $hostname = PVE::INotify::nodename();
> +    my $fqdn = `hostname -f` || $hostname;
> +    chomp $fqdn;

A bit odd seeing the highly efficient hostname cached from inotify used
with getting the FQDN in a rather expensive (fork+exec) way.
Not so keen on the use of backticks, albeit it would not be a huge
problem.

I'd favor using PVE::Tools::get_fqdn which should work as well as calling
`hostname -f` but also be quite a bit cheaper due to avoiding fork+exec.
It'd be probably even fine to cache in a module-local variable, as this
is not something that changes often, but also probably not a must for now.

> +
> +    my $data = {
> +        hostname => $hostname,
> +        fqdn => $fqdn,
> +    };
> +
> +    my $cluster_info = PVE::Cluster::get_clinfo();
> +
> +    if (my $d = $cluster_info->{cluster}) {
> +        $data->{"cluster-name"} = $d->{name};
> +    }
> +
> +    return $data;
> +}
> +
>  1;



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2025-03-27 15:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-27 14:23 [pve-devel] [PATCH cluster/ha-manager/manager 0/6] preparation for #6143: notification template cleanup Lukas Wagner
2025-03-27 14:23 ` [pve-devel] [PATCH pve-cluster 1/1] notify: add common_template_data Lukas Wagner
2025-03-27 15:31   ` Thomas Lamprecht [this message]
2025-03-28  8:28     ` Lukas Wagner
2025-03-28  9:38       ` Thomas Lamprecht
2025-03-28 10:04         ` Lukas Wagner
2025-03-27 14:23 ` [pve-devel] [PATCH pve-manager 1/4] notification templates: vzdump: generate HTML table in template Lukas Wagner
2025-03-27 14:23 ` [pve-devel] [PATCH pve-manager 2/4] notifications: apt: clean up notification template Lukas Wagner
2025-03-27 14:23 ` [pve-devel] [PATCH pve-manager 3/4] notification: replication: add common properties to template data Lukas Wagner
2025-03-27 14:23 ` [pve-devel] [PATCH pve-manager 4/4] notifications: test: style fixup Lukas Wagner
2025-03-27 14:23 ` [pve-devel] [PATCH pve-ha-manager 1/1] notifications: overhaul fence notification Lukas Wagner
2025-03-28 10:21 ` [pve-devel] superseded: [PATCH cluster/ha-manager/manager 0/6] preparation for #6143: notification template cleanup Lukas Wagner

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=79bed8e2-741b-49f9-b6cf-cb0d740fe692@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=l.wagner@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal