From: Peter Eisch via pve-user <pve-user@lists.proxmox.com>
To: "Proxmox VE user list" <pve-user@lists.proxmox.com>
Cc: Peter Eisch <peter@boku.net>
Subject: Re: [PVE-User] CEPH migration from cephadm or keep cephadm?
Date: Sun, 30 Jun 2024 18:44:03 +0000 [thread overview]
Message-ID: <mailman.169.1719773078.331.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <CAOKSTBsRMB5fQ8iU9VXLwYjQ38yN1mvPP6mCg-WSAguAptSjEA@mail.gmail.com>
[-- Attachment #1: Type: message/rfc822, Size: 5886 bytes --]
From: "Peter Eisch" <peter@boku.net>
To: "Proxmox VE user list" <pve-user@lists.proxmox.com>
Subject: Re[2]: [PVE-User] CEPH migration from cephadm or keep cephadm?
Date: Sun, 30 Jun 2024 18:44:03 +0000
Message-ID: <b2162682b42137edb315f307645a10f4@mail.boku.net>
It largely works. At some point this issue crept in:
root@node3:/# ceph-volume inventory
stderr: Unknown device "/dev/pve/data_tmeta": No such device
stderr: Unknown device "/dev/pve/data_tdata": No such device
stderr: Unknown device "/dev/pve-data/tpool": No such device
stderr: Unknown device "/dev/pve/data": No such device
--> KeyError: 'TYPE'
root@node3:/#
which seems to be tied to lvmthin. This thread https://www.spinics.net/lists/ceph-users/msg79647.html (https://www.spinics.net/lists/ceph-users/msg79647.html) had solution to this but not a PVE issue.
Thanks for the confirmation.
On Sun, Jun 30, 2024 at 10:41 AM, Gilberto Ferreira wrote:
Hi there
If it's works, keep it just like that.
Em dom., 30 de jun. de 2024 às 12:08, Peter Eisch via pve-user escreveu:
---------- Forwarded message ----------
From: Peter Eisch
To: pve-user@lists.proxmox.com (mailto:pve-user@lists.proxmox.com)
Cc:
Bcc:
Date: Sun, 30 Jun 2024 15:08:31 +0000
Subject: CEPH migration from cephadm or keep cephadm?
Hi,
I have a CEPH cluster where I’ve been doing hyperconverged with Linux KVM. I have had no problem migrating the VMs to PVE running on compute-only nodes. No instances remain on the storage nodes.
Back to converged with:
- CEPH 18.2.2
- cephadm orchestration
- 6 hosts with 16 OSDs each
- 4 hosts rocky linux
- 1 host PVE 8.2.2, deployed OSDs with cephadm
- 1 host out of the cluster, pending options
- 4 hosts running PVE/RBD
Is there a way to convert a cephadm CEPH cluster to PVE’s CEPH? Is it better to keep cephadm?
Thank you for your thoughts,
peter
---------- Forwarded message ----------
From: Peter Eisch via pve-user
To: pve-user@lists.proxmox.com (mailto:pve-user@lists.proxmox.com)
Cc: Peter Eisch
Bcc:
Date: Sun, 30 Jun 2024 15:08:31 +0000
Subject: [PVE-User] CEPH migration from cephadm or keep cephadm?
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com (mailto:pve-user@lists.proxmox.com)
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user (https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user)
[-- 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
next prev parent reply other threads:[~2024-06-30 18:44 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 [this message]
2024-07-01 18:53 ` Alwin Antreich via pve-user
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.169.1719773078.331.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=peter@boku.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