From: Alwin Antreich via pve-user <pve-user@lists.proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: Alwin Antreich <alwin@antreich.com>
Subject: Re: [PVE-User] CEPH migration from cephadm or keep cephadm?
Date: Mon, 01 Jul 2024 20:53:48 +0200 [thread overview]
Message-ID: <mailman.188.1719860565.331.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <mailman.168.1719760115.331.pve-user@lists.proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 3885 bytes --]
From: Alwin Antreich <alwin@antreich.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] CEPH migration from cephadm or keep cephadm?
Date: Mon, 01 Jul 2024 20:53:48 +0200
Message-ID: <B0632604-F3F7-4926-8127-D0EDDF091B94@antreich.com>
On June 30, 2024 5:08:31 PM GMT+02:00, Peter Eisch via pve-user <pve-user@lists.proxmox.com> wrote:
>_______________________________________________
>pve-user mailing list
>pve-user@lists.proxmox.com
>https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Hi Peter,
it depends on what you would like to achieve. If all nodes will become PVEs then it is easier to use the management and upgrade process of Proxmox.
As long as you stick to the same Ceph version then you should be able to migrate. OSDs may just start up, MONs are best re-created (easier). As well as the other services, like MGR/MDS.
Reinstallation of the whole node is of course the other path.
Cheers,
Alwin
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2024-07-01 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 15:08 Peter Eisch via pve-user
2024-06-30 15:40 ` Gilberto Ferreira
2024-06-30 18:44 ` Peter Eisch via pve-user
2024-07-01 18:53 ` Alwin Antreich via pve-user [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=mailman.188.1719860565.331.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=alwin@antreich.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