public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH docs, manager 0/7] add and expand on cluster recommendations
Date: Fri, 27 Jun 2025 15:45:43 +0200	[thread overview]
Message-ID: <8bdab510-4e7c-47d9-b1b9-921f327de737@proxmox.com> (raw)
In-Reply-To: <20250429135749.1335521-1-a.lauterer@proxmox.com>

sent a v2 
https://lore.proxmox.com/pve-devel/20250627134455.2065020-1-a.lauterer@proxmox.com/T/#u

On  2025-04-29  15:57, Aaron Lauterer wrote:
> by expanding on it in the docs and the UI.
> 
> the doc patches have some cleanup and new anchor patches
> the second ui patch is to fix an external link that I noticed and is
> just a drive-by patch.
> 
> docs: Aaron Lauterer (5):
>    pvecm: drop notes about old version incompatibilities
>    pvecm: add anchor for cluster requirements
>    pvecm: add anchor for corosync exernal vote support
>    pvecm: extend cluster Requirements
>    ha-manager: expand requirements
> 
>   ha-manager.adoc |  7 ++++++-
>   pvecm.adoc      | 34 +++++++++++++++++++---------------
>   2 files changed, 25 insertions(+), 16 deletions(-)
> 
> manager: Aaron Lauterer (2):
>    ui: cluster create: add recommendations for cluster networks
>    ui: guest import: make sure an external link has target _blank
> 
>   www/manager6/dc/ClusterEdit.js     | 15 ++++++++++++++-
>   www/manager6/window/GuestImport.js |  2 +-
>   2 files changed, 15 insertions(+), 2 deletions(-)
> 



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


      parent reply	other threads:[~2025-06-27 13:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29 13:57 Aaron Lauterer
2025-04-29 13:57 ` [pve-devel] [PATCH docs 1/7] pvecm: drop notes about old version incompatibilities Aaron Lauterer
2025-05-07 15:22   ` Kevin Schneider
2025-05-12 12:01     ` Thomas Lamprecht
2025-04-29 13:57 ` [pve-devel] [PATCH docs 2/7] pvecm: add anchor for cluster requirements Aaron Lauterer
2025-04-29 13:57 ` [pve-devel] [PATCH docs 3/7] pvecm: add anchor for corosync exernal vote support Aaron Lauterer
2025-04-29 13:57 ` [pve-devel] [PATCH docs 4/7] pvecm: extend cluster Requirements Aaron Lauterer
2025-05-07 15:22   ` Kevin Schneider
2025-05-08 11:54     ` Robin Christ
2025-06-27 12:47       ` Aaron Lauterer
2025-04-29 13:57 ` [pve-devel] [PATCH docs 5/7] ha-manager: expand requirements Aaron Lauterer
2025-04-29 13:57 ` [pve-devel] [PATCH manager 6/7] ui: cluster create: add recommendations for cluster networks Aaron Lauterer
2025-04-29 13:57 ` [pve-devel] [PATCH manager 7/7] ui: guest import: make sure an external link has target _blank Aaron Lauterer
2025-06-27 13:45 ` Aaron Lauterer [this message]

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=8bdab510-4e7c-47d9-b1b9-921f327de737@proxmox.com \
    --to=a.lauterer@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