From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexandre DERUMIER <aderumier@odiso.com>
Subject: Re: [pve-devel] Ceph 15.2.5 update?
Date: Tue, 13 Oct 2020 14:45:09 +0200 [thread overview]
Message-ID: <b1f56f15-549c-51b2-9c39-d7f6f52ba61c@proxmox.com> (raw)
In-Reply-To: <521737835.3272203.1601723722503.JavaMail.zimbra@odiso.com>
On 03.10.20 13:15, Alexandre DERUMIER wrote:
>>>
>>> Hmm - will that actually work?
>>>
>>> My understanding was that for Proxmox you had to use the Proxmox-specific
>>> Ceph packages - just like there's a Proxmox-specific kernel etc.
>
> Proxmox don't have any extra patch on ceph package, so you can use package from ceph official repo.
>
That's not true, and I would not recommend using another repo, ceph itself is
really not good at doing Debian packages, so especially dependency stuff is
often quite wrong to incompatible with PVE.
https://git.proxmox.com/?p=ceph.git;a=tree;f=patches;h=d30ebbccd31cedfae76dd1426298e97874d8a8f1;hb=HEAD
> (Proxmox have his own repo, to be able to test ceph minor versions before releases, to avoid bug,.....)
>
That's an additional reason, but mainly we do it to have full control
over packaging.
Anyway, 15.2.5 is out on the test repository since yesterday.
prev parent reply other threads:[~2020-10-13 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMnnoUJ41C8L2TyCch0_KXGkKm57Fee8_D2Zy1XqiODKCuuTbg.ref@mail.gmail.com>
2020-10-02 3:43 ` Victor Hooi
[not found] ` <4e732c70-86a1-2d61-3efd-47f5e3a470a6@coppint.com>
2020-10-02 12:22 ` Victor Hooi
2020-10-03 11:15 ` Alexandre DERUMIER
2020-10-13 12: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=b1f56f15-549c-51b2-9c39-d7f6f52ba61c@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=aderumier@odiso.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox