From: Iztok Gregori <iztok.gregori@elettra.eu>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: [PVE-User] Network migration of a hyper-converged cluster
Date: Wed, 29 Jan 2025 11:27:39 +0100 [thread overview]
Message-ID: <83250231-ada6-4e81-a45d-492e12b64d5f@elettra.eu> (raw)
Hi to all!
I'm planning to migrate the network of a hyper-converged Proxmox cluster
to a different subnet and I'm searching for some advice on how to do
that without downtime and without the need to reinstall the nodes.
The migration will be performed one node at the time and the node will
be emptied from VMs (via live-migration) also the "noout" parameter will
be enabled to avoid unnecessary data movement. The "empty" nodes can be
restarted if needed.
For Ceph I was thinking to add the new network to "public_network" and
"cluster_network" (those 2 are the same), so Ceph will be ready to
accept "requests" from the IPs of the new network. After that, I'm less
sure of how to handle the configuration of monitors/managers. I was
thinking something like that:
- Destroy the monitor/manager daemon (if the node has one).
- Stop OSDs.
- Change Node IP.
- Start OSDs (or restart the node).
- Recreate the monitor/manager.
Am I missing something?
I have more doubts about how to migrate Proxmox network (corosync). I
think that I'll need to add a new "ring" network in corosync.conf with
the nodes new IPs, so once the node changes its IP address it will be
seen again "UP". At the end of the migration I'll remove the old "ring"
network. Is it feasible or it will not work?
Any other advice or experiences are welcome!
Cheers
Iztok
--
Iztok Gregori
ICT Systems and Services
Elettra - Sincrotrone Trieste S.C.p.A.
Telephone: +39 040 3758948
http://www.elettra.eu
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
reply other threads:[~2025-01-29 10:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=83250231-ada6-4e81-a45d-492e12b64d5f@elettra.eu \
--to=iztok.gregori@elettra.eu \
--cc=pve-user@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