From: Thomas Skinner <thomas@atskinner.net>
To: pve-devel@lists.proxmox.com
Cc: Thomas Skinner <thomas@atskinner.net>
Subject: [pve-devel] [PATCH SERIES docs/ha-manager/manager v2] close #6144: add ui button + api for node maintenance mode
Date: Sat, 20 Sep 2025 13:20:46 -0500 [thread overview]
Message-ID: <20250920182050.1657928-1-thomas@atskinner.net> (raw)
Continued work on node maintenance mode button in UI.
Changes since V1:
- Code refactoring/reformatting
- Clarity in docs
- Remove redundant GET API for maintenance status
- Change button UI to dropdown menu with icons
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.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-09-20 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-20 18:20 Thomas Skinner [this message]
2025-09-20 18:20 ` [pve-devel] [PATCH ha-manager v2 1/1] add additional api field for lrm_mode in status check Thomas Skinner
2025-09-20 18:20 ` [pve-devel] [PATCH manager v2 1/2] add api setter for node maintenance mode Thomas Skinner
2025-09-20 18:20 ` [pve-devel] [PATCH docs v2 1/1] add docs for maintenance mode buttons in UI Thomas Skinner
2025-09-20 18:20 ` [pve-devel] [PATCH manager v2 2/2] add UI for node maintenance enable/disable 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=20250920182050.1657928-1-thomas@atskinner.net \
--to=thomas@atskinner.net \
--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.