all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Skinner <thomas@atskinner.net>
To: d.rusovac@proxmox.com
Cc: pve-devel@lists.proxmox.com
Subject: Re: pve-devel Digest, Vol 190, Issue 194
Date: Thu, 26 Mar 2026 20:10:01 -0500	[thread overview]
Message-ID: <CALn9RMeusvxbJYWBtzQ1m2yGYH1gzR8UhqU5CaWNKmHBmMNzYA@mail.gmail.com> (raw)
In-Reply-To: <177436040579.1036.4395614451821464228@lists.proxmox.com>

> On Mon Jan 26, 2026 at 2:09 AM CET, Thomas Skinner wrote:
> > On Mon, Dec 22, 2025 at 8:09 AM Thomas Skinner <thomas@atskinner.net> wrote:
> >>
> >> On Sat, Oct 25, 2025 at 1:38 PM Thomas Skinner <thomas@atskinner.net> wrote:
> >> >
> >> > Continued work on node maintenance mode button in UI.
> >> >
> >> > Changes since V2:
> >> > - Adjust permissions from Sys.Console to Sys.Modify
> >> > - Fix typo in description
> >> >
> >> > docs:
> >> >
> >> > Thomas Skinner (1):
> >> >   add docs for maintenance mode buttons in UI
> >> >
> >> >  ha-manager.adoc | 22 ++++++++++++++++++++--
> >> >  1 file changed, 20 insertions(+), 2 deletions(-)
> >> >
> >> >
> >> > ha-manager:
> >> >
> >> > Thomas Skinner (1):
> >> >   add additional api field for lrm_mode in status check
> >> >
> >> >  src/PVE/API2/HA/Status.pm | 7 +++++++
> >> >  1 file changed, 7 insertions(+)
> >> >
> >> >
> >> > manager:
> >> >
> >> > Thomas Skinner (2):
> >> >   add api setter for node maintenance mode
> >> >   add UI for node maintenance enable/disable
> >> >
> >> >  PVE/API2/Nodes.pm             | 38 +++++++++++++++
> >> >  www/manager6/ha/StatusView.js | 92 +++++++++++++++++++++++++++++++++++
> >> >  2 files changed, 130 insertions(+)
> >> >
> >> >
> >> > --
> >> > 2.47.3
> >> >
> >>
> >> Hello! Any updates on getting this patch series accepted?
> >
> > Hello! Checking in again to see if this patch series can be applied.
> >
>
> Hello Thomas, thank you for sending this patch series!
>
> We plan to extend the concept of node maintenance to non-HA resources in
> the near future. This will involve a dedicated endpoint and
> corresponding UI support.
>
> To avoid "programming us into a corner" or causing code churn, we would
> like to evaluate some approaches first, before committing anything.
> We'll then retake a look at your changes here and try to build on top of
> them. I hope that's okay with you.
>
> Kind regards,
> Dominik
>
> [snip]

No worries at all! Thanks for considering the patch. Once there is
something figured out, I'll be happy to update the patch accordingly
or the PVE team is welcome to spin off the submitted patch as they
please. Non-HA resources being considered in maintenance is definitely
an important aspect to work into the product.



           reply	other threads:[~2026-03-27  1:34 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <177436040579.1036.4395614451821464228@lists.proxmox.com>]

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=CALn9RMeusvxbJYWBtzQ1m2yGYH1gzR8UhqU5CaWNKmHBmMNzYA@mail.gmail.com \
    --to=thomas@atskinner.net \
    --cc=d.rusovac@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