public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Graeme Seaton <lists@graemes.com>
Subject: Re: [pve-devel] OpenZFS 2.0
Date: Wed, 2 Dec 2020 14:10:11 +0100	[thread overview]
Message-ID: <fa8b8f1d-12bf-0a13-c3aa-2ed7ef0b3035@proxmox.com> (raw)
In-Reply-To: <019e33dd-6722-f2b2-24a3-f41d59f1527b@graemes.com>

Hi,

On 02.12.20 13:45, Graeme Seaton wrote:
> Notice that OpenZFS 2.0 has been officially released at: https://github.com/openzfs/zfs/releases/tag/zfs-2.0.0

yes, we noticed that too :)

> Is integration into PVE on the roadmap? (I'm a sucker for new toys ;-) )
> 

Copying over my answer from a related forum thread[0]:

Yes, we plan to include it in Proxmox VE 6.4, which is due in the first half
of 2021, if I had to extrapolate from past releases. At least if no general
issues comes up and the upgrade path is straight forward.
But even though it's a big increase of version number, it's a rather sensible
sized release code-wise, so it should not pose bigger problems (knocks wood).

It'll trickle into the package repositories a bit earlier after passing through
testing here (2021/Q1), we'll post an update in the forum once available.

cheers,
Thomas

[0]: https://forum.proxmox.com/threads/openzfs-2-0.79948/#post-353631




      parent reply	other threads:[~2020-12-02 13:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 12:45 Graeme Seaton
2020-12-02 13:10 ` Moayad Almalat
2020-12-02 13:10 ` 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=fa8b8f1d-12bf-0a13-c3aa-2ed7ef0b3035@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=lists@graemes.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal