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>,
	Thomas Skinner <thomas@atskinner.net>,
	Daniel Kral <d.kral@proxmox.com>
Subject: Re: [pve-devel] [PATCH ha-manager 2/2] add api getter/setter for node maintenance mode
Date: Wed, 27 Aug 2025 09:31:48 +0200	[thread overview]
Message-ID: <9be0c0ba-b50c-4b8a-9832-440328d6d55c@proxmox.com> (raw)
In-Reply-To: <CALn9RMdGbTp1H1cc_3LHhke-ui30J9Vqf9ro3DXYsKt5L04hnw@mail.gmail.com>

On 26/08/2025 18:02, Thomas Skinner wrote:
>> The more I think about it, I'm somewhat inclined to register the whole
>> subclass under /nodes/{node}/ha/... instead of /cluster/ha/nodes/... to
>> not duplicate the information of a nodelist, which is provided by
>> pve-cluster and there would be something wrong with the HA Manager
>> anyway if those are out-of-sync and all the HA-related information can
>> then live in a node-specific "ha" subdirectory.
>>
>> Then this API handler wouldn't be needed anymore at all.
> If this is how Proxmox would like it, that makes it much easier IMO. I
> wasn't sure which one to include it under, so I put it under the
> cluster path since a cluster must be created to even have the HA
> featureset. I'm good with either, I just need to know so that I know
> what to update for a v2 series.

We might be already all on the same page, so just to be sure and a
bit more context to avoid making this to HA specific:

Reporting the current (maintenance) status should go into either (or
both of) the /cluster/ha/status and/or the /cluster/resources API
endpoint.

As there are some light-weight plans to provide maintenance mode
for non-ha services, I'd indeed place that outside of a ha specific
path now already, might be even fine to use a dedicated
/nodes/{node}/maintenance API endpoint. For now the description should
state that it's only affecting HA, the non-HA parts are probably not
very complicated work, but got quite a few edge cases and design
decisions that are better done in a separate series building on top
of such API infrastructure you add here.


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


  reply	other threads:[~2025-08-27  7:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25  4:11 [pve-devel] [PATCH SERIES docs/ha-manager/manager] close #6144: add ui button + api " Thomas Skinner
2025-08-25  4:11 ` [pve-devel] [PATCH ha-manager 1/2] add additional api field for lrm_mode in status check Thomas Skinner
2025-08-25  4:11 ` [pve-devel] [PATCH manager 1/2] add api path map for node HA endpoints Thomas Skinner
2025-08-26  9:38   ` Daniel Kral
2025-08-26 10:26     ` Thomas Lamprecht
2025-08-26 11:34       ` Daniel Kral
2025-08-25  4:11 ` [pve-devel] [PATCH docs 1/1] add docs for maintenance mode buttons in UI Thomas Skinner
2025-08-26  9:44   ` Daniel Kral
2025-08-26 16:05     ` Thomas Skinner
2025-08-27  7:50       ` Daniel Kral
2025-08-25  4:11 ` [pve-devel] [PATCH ha-manager 2/2] add api getter/setter for node maintenance mode Thomas Skinner
2025-08-26  9:38   ` Daniel Kral
2025-08-26 16:00     ` Thomas Skinner
2025-08-27  7:31       ` Thomas Lamprecht [this message]
2025-08-27  8:25       ` Daniel Kral
2025-08-27  9:20         ` Thomas Lamprecht
2025-08-29 20:13         ` Thomas Skinner
2025-09-01  8:52           ` Daniel Kral
2025-08-29 20:17     ` Thomas Skinner
2025-08-25  4:11 ` [pve-devel] [PATCH manager 2/2] add UI for node maintenance enable/disable Thomas Skinner
2025-08-26 10:00   ` Daniel Kral
2025-08-26 17:34     ` Thomas Skinner

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=9be0c0ba-b50c-4b8a-9832-440328d6d55c@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=d.kral@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=thomas@atskinner.net \
    /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