From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Aaron Lauterer <a.lauterer@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs v2] pveceph: document the change of ceph networks
Date: Tue, 13 Jan 2026 09:45:01 +0100 [thread overview]
Message-ID: <176829389808.1701861.783385891310196376.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260102165754.650450-1-a.lauterer@proxmox.com>
On Fri, 02 Jan 2026 17:57:54 +0100, Aaron Lauterer wrote:
> ceph networks (public, cluster) can be changed on the fly in a running
> cluster. But the procedure, especially for the ceph public network is
> a bit more involved. By documenting it, we will hopefully reduce the
> number of issues our users run into when they try to attempt a network
> change on their own.
>
>
> [...]
Applied, thanks!
[1/1] pveceph: document the change of ceph networks
commit: 72ff2edabfd9e733c5f45c4e2c0e1e8037556f95
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2026-01-13 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 16:57 [pve-devel] " Aaron Lauterer
2026-01-13 8:22 ` Nicolas Frey
2026-01-13 8:45 ` Thomas Lamprecht [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=176829389808.1701861.783385891310196376.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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 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.