From: "Patrick Mooney" <pmooney@pfmooney.com>
To: "illumos Developer" <developer@lists.illumos.org>
Subject: Compatibility file in OpenZFS for illumos
Date: Thu, 09 Nov 2023 20:55:17 -0600 [thread overview]
Message-ID: <c0e6c795-d68d-4c03-892c-07be0ecef135@app.fastmail.com> (raw)
OpenZFS supports a "compatibility" property when creating a zpool which constraints the set of features enabled on said pool. As part of that functionality, they ship a set of files detailing the features supported by different OSes and/or OpenZFS versions, making it relatively simple for a user to create a pool which should be supported by their target ZFS implementation(s).
See: https://openzfs.github.io/openzfs-docs/man/master/7/zpool-features.7.html#Compatibility_feature_sets
I propose that we (illumos) put together our own feature list file for inclusion in that compatibility listing. Without an explicit release cadence for illumos-gate, we could instead put together that listing periodically (perhaps annually?) provided we've integrated new pool-visible features.
Baring serious objections, I'm going to give this a swing starting with an 'illumos-2023' file reflecting the state of things from 1 January.
Cheers
--
Patrick Mooney
next reply other threads:[~2023-11-10 2:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 2:55 Patrick Mooney [this message]
2023-11-10 15:36 ` [developer] " Dan McDonald
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=c0e6c795-d68d-4c03-892c-07be0ecef135@app.fastmail.com \
--to=pmooney@pfmooney.com \
--cc=developer@lists.illumos.org \
/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;
as well as URLs for NNTP newsgroup(s).