From: Victor Hooi <victorhooi@yahoo.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
PVE development discussion <pve-devel@pve.proxmox.com>
Subject: Re: [pve-devel] Ceph Pacific testing?
Date: Mon, 14 Jun 2021 09:23:28 +1000 [thread overview]
Message-ID: <CAMnnoU+UxP=FmCWZBM4XuhoypKeEWgnmkDREcjMxvQK1Mw9HtQ@mail.gmail.com> (raw)
In-Reply-To: <ef4c5cb7-6f2f-26a4-32d5-173c4db8bb5f@proxmox.com>
Hi Thomas!
Do you know if there's been any update on Ceph Pacific in Proxmox? Are we
anywhere near having testing packages to try out? =)
Thanks,
Victor
On Sun, Apr 18, 2021 at 5:29 PM Thomas Lamprecht <t.lamprecht@proxmox.com>
wrote:
> Hi,
>
> On 18.04.21 00:48, Victor Hooi wrote:
> > Awesome! Really excited by this!
> >
> > Do we have any indication of when this year the PVE 7.0 testing will
> begin?
>
> No, nothing definitive yet, if I had to guess, I'd say that the test repo
> would get available in Q2 rather than Q3, though.
>
> > Also - will it still be based on a Ubuntu kernel? Or any chance we can
> get
> > a newer kernel from Debian? =)
>
> Debian 11 Bullseye will ship the 5.10 kernel, Ubuntu 21.04 will ship the
> 5.11 kernel.
>
> We will use the newer one from Ubuntu, and actually, that one is already
> available for testing in Proxmox VE 6 since almost a month[0].
>
> Note, while we did not see any issue anywhere, we still recommend to stay
> on 5.4, which
> will stay the default kernel for the remaining PVE 6.x lifetime.
>
> With above note in mind, you can install it by executing:
>
> apt update
> apt install pve-kernel-5.11
>
> cheers,
> Thomas
>
> [0]: https://forum.proxmox.com/threads/kernel-5-11.86225/
>
> >
> > Thanks,
> > Victor
> >
> > On Thu, Apr 15, 2021 at 8:44 PM Thomas Lamprecht <
> t.lamprecht@proxmox.com>
> > wrote:
> >
> >> Hi,
> >>
> >> On 14.04.21 22:05, Victor Hooi wrote:
> >>> Hi,
> >>>
> >>> Ceph Pacific was recently announced:
> >>>
> >>> https://ceph.io/releases/v16-2-0-pacific-released/
> >>>
> >>> Do you know if anybody has started testing this for Proxmox yet?
> >>>
> >>> Or are there alpha/beta packages we could run in a test lab?
> >>
> >> FYI: We plan to build and release this for upcoming PVE 7.0 this year,
> >> based on
> >> Debian bullseye.
> >>
> >> cheers,
> >> Thomas
> >>
> >>
> >
>
>
>
prev parent reply other threads:[~2021-06-13 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMnnoUL0iRSk_24b9jeTqFmEvJi+P6e+WzQv8ZwdKu6oMXXVgw.ref@mail.gmail.com>
2021-04-14 20:05 ` Victor Hooi
2021-04-15 10:44 ` Thomas Lamprecht
2021-04-17 22:48 ` Victor Hooi
2021-04-18 7:29 ` Thomas Lamprecht
2021-06-13 23:23 ` Victor Hooi [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='CAMnnoU+UxP=FmCWZBM4XuhoypKeEWgnmkDREcjMxvQK1Mw9HtQ@mail.gmail.com' \
--to=victorhooi@yahoo.com \
--cc=pve-devel@lists.proxmox.com \
--cc=pve-devel@pve.proxmox.com \
--cc=t.lamprecht@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