public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Daniel Kral" <d.kral@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Cc: pve-devel <pve-devel-bounces@lists.proxmox.com>,
	Thomas Skinner <thomas@atskinner.net>
Subject: Re: [pve-devel] [PATCH manager 1/2] add api path map for node HA endpoints
Date: Tue, 26 Aug 2025 11:38:35 +0200	[thread overview]
Message-ID: <DCC9C6P91WTQ.307NI9R7EOJRO@proxmox.com> (raw)
In-Reply-To: <20250825041128.132814-3-thomas@atskinner.net>

On Mon Aug 25, 2025 at 6:11 AM CEST, Thomas Skinner wrote:
> Signed-off-by: Thomas Skinner <thomas@atskinner.net>
> ---
>  PVE/API2/HAConfig.pm | 12 +++++++++++-
>  1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/PVE/API2/HAConfig.pm b/PVE/API2/HAConfig.pm
> index d29211fb..489cbf72 100644
> --- a/PVE/API2/HAConfig.pm
> +++ b/PVE/API2/HAConfig.pm
> @@ -12,6 +12,7 @@ use PVE::JSONSchema qw(get_standard_option);
>  use PVE::Exception qw(raise_param_exc);
>  use PVE::API2::HA::Resources;
>  use PVE::API2::HA::Groups;
> +use PVE::API2::HA::Nodes;
>  use PVE::API2::HA::Rules;
>  use PVE::API2::HA::Status;
>  
> @@ -37,6 +38,11 @@ __PACKAGE__->register_method({
>      path => 'status',
>  });
>  
> +__PACKAGE__->register_method({
> +    subclass => "PVE::API2::HA::Nodes",
> +    path => 'nodes',
> +});
> +

As stated in the ha-manager #2 patch, I'm inclined to register this at
/nodes/{node}/ha/... instead of /cluster/ha/nodes/{nodes}/..., because
then we wouldn't need to duplicate the nodelist in the HA endpoints in
the latter, because it is already provided at GET /nodes. We could still
provide information on GET /nodes/{node}/ha for each node, e.g. the LRM
state, mode, etc.

>  __PACKAGE__->register_method({
>      name => 'index',
>      path => '',
> @@ -63,7 +69,11 @@ __PACKAGE__->register_method({
>          my ($param) = @_;
>  
>          my $res = [
> -            { id => 'status' }, { id => 'resources' }, { id => 'groups' }, { id => 'rules' },
> +            { id => 'status' },
> +            { id => 'resources' },
> +            { id => 'groups' },
> +            { id => 'rules' },
> +            { id => 'nodes' },
>          ];
>  
>          return $res;


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


  reply	other threads:[~2025-08-26  9:39 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 for node maintenance mode 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 [this message]
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
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=DCC9C6P91WTQ.307NI9R7EOJRO@proxmox.com \
    --to=d.kral@proxmox.com \
    --cc=pve-devel-bounces@lists.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