public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH manager] pvestatd: improve broadcast of node version-info
Date: Thu, 27 Feb 2025 15:34:27 +0100	[thread overview]
Message-ID: <82f15b5e-9c2b-4925-a3f1-bb5180486975@proxmox.com> (raw)
In-Reply-To: <20250116163055.2619572-1-a.lauterer@proxmox.com>

sent a v2 
https://lore.proxmox.com/pve-devel/20250227143356.1089350-1-a.lauterer@proxmox.com/T/#u

On  2025-01-16  17:30, Aaron Lauterer wrote:
> Until now, the pvestatd did broadcast the pve-manager version only once
> after startup of the service. But there are some situations, where the
> local pmxcfs (pve-cluster) restarts and loses that information.
> Basically everytime we restart the pmxcfs without restarting pvestatd
> too.
> 
> For example, on a cluster join, or if the pmxcfs has been restarted
> manually.
> 
> By additionally checking if the local kv-store of the pmxcfs has any
> version info for the node, we can decide if another broadcast is
> necessary.
> Therefore after the next run of pvestatd, we should have the full
> version info available again.
> 
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
> This patch is preparation to get reliable version infos as I am picking
> of the patch series of Folke to include more metrics into the RRD data
> and summary graphs. [0]
> This was a big blocker and now with the major version change coming up,
> we at least can assume the latest 8.x installed as part of the update to
> PVE 9.
> Therefore, we should get this in with PVE 8. Additional patches for PVE
> 8 will follow to make the transition smoother. But as mentioned, this
> here is one of the things that needs to work reliably, which is why I
> submit the patch already now.
> 
> [0] https://lore.proxmox.com/pve-devel/20231211144721.212071-1-f.gleumes@proxmox.com/
> 
>   PVE/Service/pvestatd.pm | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/PVE/Service/pvestatd.pm b/PVE/Service/pvestatd.pm
> index 7fa003fe..03c578e1 100755
> --- a/PVE/Service/pvestatd.pm
> +++ b/PVE/Service/pvestatd.pm
> @@ -527,7 +527,10 @@ sub update_sdn_status {
>   
>   my $broadcast_version_info_done = 0;
>   my sub broadcast_version_info : prototype() {
> -    if (!$broadcast_version_info_done) {
> +    if (
> +	!$broadcast_version_info_done
> +	|| !keys PVE::Cluster::get_node_kv('version-info', $nodename)->%*
> +    ) {
>   	PVE::Cluster::broadcast_node_kv(
>   	    'version-info',
>   	    encode_json(PVE::pvecfg::version_info()),



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


      parent reply	other threads:[~2025-02-27 14:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16 16:30 Aaron Lauterer
2025-01-16 16:35 ` Christian Ebner
2025-01-16 16:38   ` Aaron Lauterer
2025-01-16 16:50     ` Christian Ebner
2025-02-27 14:06       ` Aaron Lauterer
2025-01-17 12:18 ` Fiona Ebner
2025-02-26 16:02   ` Aaron Lauterer
2025-02-27  8:59     ` Fiona Ebner
2025-02-27 14:52       ` Fabian Grünbichler
2025-02-27 15:00         ` Fiona Ebner
2025-02-27 15:11           ` Fabian Grünbichler
2025-03-04  9:06             ` Thomas Lamprecht
2025-02-27 14:34 ` Aaron Lauterer [this message]

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=82f15b5e-9c2b-4925-a3f1-bb5180486975@proxmox.com \
    --to=a.lauterer@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal