public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Dominik Rusovac" <d.rusovac@proxmox.com>
To: "Dominik Csapak" <d.csapak@proxmox.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH manager v2] ui: ha: add disarm/re-arm button
Date: Thu, 16 Apr 2026 07:58:01 +0200	[thread overview]
Message-ID: <DHUCK8PJBEB5.1IDYLD7TPDDZN@proxmox.com> (raw)
In-Reply-To: <ee90ff79-cc2b-46c8-9cd9-f0a9867b705a@proxmox.com>

On Wed Apr 15, 2026 at 4:18 PM CEST, Dominik Csapak wrote:
>
>
> On 4/15/26 3:30 PM, Dominik Rusovac wrote:
>> thx for the comments! I will send a v3
>> 
>> On Wed Apr 15, 2026 at 2:32 PM CEST, Dominik Csapak wrote:
>>> what i miss with using these is some feedback when i activated them.
>>>
>>> This is probably more due to the backend decision, but
>>> when clicking arm/disarm, there is nothing happening in the gui at
>>> first, no spinning icon, no change in state..
>> 
>> regarding feedback after activating either of them: one can see the
>> Status changing in the Status panel, which exactly traces what's going
>> on for every node, in particular it reveals the armed-state in the
>> Status of fencing
>> 
>> if that's not enough feedback, I'd look into other possible solutions in
>> more detail
>
> on my test machine, it multiple seconds from clicking ok to
> the status actually changing, so this might be confusing, especially
> if the cluster/connection is not the fastest and the updates
> take longer to arrive.
>

ok, I see your point. I will try to come up with a solution

>> 
>>>
>>> I think there are a few possible solutions on this, but
>>> i'm not super deep in the ha stack, so sorry in advance if
>>> some can't work:
>>> * use a worker that waits for the change of the ha state, e.g.
>>>     via polling. this could directly be shown in the gui
>>> * mark the requested state immediately somewhere and return
>>>     it with the overall ha state, so we  see in the gui what is happening
>>> * 'fake' the progress until we see a status change
>>>     (i don't really like this, since it's prone to errors when e.g.
>>>      one admin disarms, the other arms again, but the gui does not
>>>      get an updated state in the meantime)
>>>

[snip]




  reply	other threads:[~2026-04-16  5:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15  6:41 Dominik Rusovac
2026-04-15  7:34 ` Daniel Kral
2026-04-15 12:32 ` Dominik Csapak
2026-04-15 13:32   ` Dominik Rusovac
2026-04-15 14:18     ` Dominik Csapak
2026-04-16  5:58       ` Dominik Rusovac [this message]
2026-04-16  7:33     ` Daniel Kral
2026-04-16  9:20       ` Thomas Lamprecht
2026-04-16  9:59         ` Daniel Kral
2026-04-16 11:21 ` Dominik Rusovac

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=DHUCK8PJBEB5.1IDYLD7TPDDZN@proxmox.com \
    --to=d.rusovac@proxmox.com \
    --cc=d.csapak@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