From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pve-user-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 3D1F11FF2A7 for <inbox@lore.proxmox.com>; Mon, 1 Jul 2024 21:02:36 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 1C8CC3EF0; Mon, 1 Jul 2024 21:02:47 +0200 (CEST) Date: Mon, 01 Jul 2024 20:53:48 +0200 To: Proxmox VE user list <pve-user@lists.proxmox.com> In-Reply-To: <mailman.168.1719760115.331.pve-user@lists.proxmox.com> References: <mailman.168.1719760115.331.pve-user@lists.proxmox.com> MIME-Version: 1.0 Message-ID: <mailman.188.1719860565.331.pve-user@lists.proxmox.com> List-Id: Proxmox VE user list <pve-user.lists.proxmox.com> List-Post: <mailto:pve-user@lists.proxmox.com> From: Alwin Antreich via pve-user <pve-user@lists.proxmox.com> Precedence: list Cc: Alwin Antreich <alwin@antreich.com> X-Mailman-Version: 2.1.29 X-BeenThere: pve-user@lists.proxmox.com List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=subscribe> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-user/> Reply-To: Proxmox VE user list <pve-user@lists.proxmox.com> List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help> Subject: Re: [PVE-User] CEPH migration from cephadm or keep cephadm? Content-Type: multipart/mixed; boundary="===============0355361348682056101==" Errors-To: pve-user-bounces@lists.proxmox.com Sender: "pve-user" <pve-user-bounces@lists.proxmox.com> --===============0355361348682056101== Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <alwin@antreich.com> X-Original-To: pve-user@lists.proxmox.com Delivered-To: pve-user@lists.proxmox.com Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 2BFD7BB85F for <pve-user@lists.proxmox.com>; Mon, 1 Jul 2024 21:02:45 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0BF6D3F17 for <pve-user@lists.proxmox.com>; Mon, 1 Jul 2024 21:02:45 +0200 (CEST) Received: from mx.antreich.com (mx.antreich.com [173.249.42.230]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-user@lists.proxmox.com>; Mon, 1 Jul 2024 21:02:43 +0200 (CEST) Received: from mail2.antreich.com (unknown [172.16.9.25]) by mx.antreich.com (Postfix) with ESMTPS id 6B98A6E2E13; Mon, 1 Jul 2024 20:53:51 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=antreich.com; s=2018; t=1719860031; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=X8Y+8LVGKnFBq5bz2nvFg1eJO3zgCG/aIpQFAWgVYJ8=; b=G2ZUuVunzoJ2GGVD3F3t1rUcFcA9i7q3hRVJxUNPagTOCb2XP+udoIPXhljsxOu4CMYLOs +0iorxjTh4gTlgDbXtaEZmwa0sNUC9UTaQzxZBGQSSFnbETZ3XHzxPiX4rnHyIXfMgE70Z 0G7NRA3YMYkSof62gM8vunJv191fpx4g5W5PYXhbrATpE3bqkXIhR9UR2Xiqj+Bk3o4/LQ DSxU2t/cWfL98bfDg0ElS9FuTz2KL7sS1etH3K5pmbMLa3aKLBSjvSIYQsGwwnbJgtRZ2d 55eVi28QSowPMk/CoKhjX8cXmr6fXUA65VHzYdEmc4lFnIQ7sywOHCtdRVjasA== Date: Mon, 01 Jul 2024 20:53:48 +0200 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? In-Reply-To: <mailman.168.1719760115.331.pve-user@lists.proxmox.com> References: <mailman.168.1719760115.331.pve-user@lists.proxmox.com> Message-ID: <B0632604-F3F7-4926-8127-D0EDDF091B94@antreich.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 0.125 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record On June 30, 2024 5:08:31 PM GMT+02:00, Peter Eisch via pve-user <pve-user@l= ists=2Eproxmox=2Ecom> wrote: >_______________________________________________ >pve-user mailing list >pve-user@lists=2Eproxmox=2Ecom >https://lists=2Eproxmox=2Ecom/cgi-bin/mailman/listinfo/pve-user Hi Peter, it depends on what you would like to achieve=2E If all nodes will become P= VEs then it is easier to use the management and upgrade process of Proxmox= =2E As long as you stick to the same Ceph version then you should be able to m= igrate=2E OSDs may just start up, MONs are best re-created (easier)=2E As w= ell as the other services, like MGR/MDS=2E Reinstallation of the whole node is of course the other path=2E=20 Cheers, Alwin --===============0355361348682056101== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user --===============0355361348682056101==--