>> >> >> On Wed, Dec 5, 2018 at 9:21 PM Josh Paetzel <[email protected] >> <mailto:[email protected]>> wrote: >> There was a proposal on this mailing list a week or so ago that sparked some >> good discussion regarding setting feature flags at pool creation. We >> discussed this proposal on the last OpenZFS call and while we all agreed it >> was a good idea, we felt the UI could use a little workshopping. >> >> Thanks for leading this discussion, Josh! >> >> >> This proposal is simply a starting point for a discussion. >> >> The proposal is to add an optional flag at zpool create time. -o features= >> >> which can be set to one of the following 4 settings: >> >> all: The default and the current behavior of zpool create. This setting >> enables all features supported by the in use OpenZFS version. >> >> compat: Enable async_destroy, empty_bpobj, filesystem_limits, lz4_compress, >> spacemap_histogram, extensible_dataset, bookmarks, enabled_txg, and >> hole_birth. This set of features is supported by FreeBSD/FreeNAS 9.3 (July >> of 2014), ZoL 0.6.4 ( 0.6.5.6 was used in Ubuntu 16.04 LTS), and Illumos in >> the early to mid 2014 era. >> >> I think the term "portable" is more specific than "compat[ible]", so "-o >> features=portable" is probably a better name. Thanks to whoever suggested >> that at the meeting Tuesday. > > +1 > >> I think that the definition of "-o features=portable" needs to change over >> time, as features become more widely available. Do you have thoughts on how >> specifically we should do that? > > One thought would be: As a delivery vehicle drops out of support we can > remove it from the list. So say we have -o features=portable include Ubuntu > 16.04 LTS. When support for Ubuntu 16.04 LTS expires we remove it from the > portable list. Now, that directly contradicts the first pass at this. For > instance FreeBSD (and FreeNAS) 9.3-R have long been out of support by the > "vendor" > > Another thought would be "do it by date" . Which is to say, "Here are the > Tier 1 platforms. By using the portable flag you get feature flags that any > Tier 1 platform supported 3 years ago from when what you are using now was > released."
maybe prepare special list of versions on wiki, where specify: features=portable1 where: portable1=Ubuntu16,Debian9,FreeBSD10 portable2=Ubuntu17,Debisn10,FereBSD11 etc we can use: zpool upgrade -o feature=portable2 <pool name> to be sure we are still in sync between platforms. but still open question - how to identify illumos? can we create some tag on illumos tree for this compatibility list to be in sync with others platforms ? -Igor > > Both of those are not very good ways to express, "systems that people might > reasonably be using and might want to migrate pools between" > > -- > > Thanks, > > Josh Paetzel > > > openzfs <https://openzfs.topicbox.com/latest> / openzfs-developer / see > discussions <https://openzfs.topicbox.com/groups/developer> + participants > <https://openzfs.topicbox.com/groups/developer/members> + delivery options > <https://openzfs.topicbox.com/groups/developer/subscription>Permalink > <https://openzfs.topicbox.com/groups/developer/T562a2f6ecf883736-Mb86c3e2623b86d5eb4146234> ------------------------------------------ openzfs: openzfs-developer Permalink: https://openzfs.topicbox.com/groups/developer/T562a2f6ecf883736-M628c654257b69ea394e284fc Delivery options: https://openzfs.topicbox.com/groups/developer/subscription
