Re: [developer] OpenZFS feature flag at zpool create proposal

A little late to the party, but: Given the goals are to give an easy way to create a pool that is compatible with a desired range of other systems (and tools like GRUB) in a way that is both interoperable between the different distributions / platforms, easy to automate and simple to remember..

Re: [developer] OpenZFS feature flag at zpool create proposal

So something like this: (Ignoring the accuracy of the version numbers and ZFS features listed) | ZFS Version Introduction | ZFS FEATURE DESCRIPTION | BSD | Linux | macOS | Illumos | Comp. Ver. edonr | 11.1 ||

Re: [developer] OpenZFS feature flag at zpool create proposal

On Sun, Dec 9, 2018 at 5:46 PM wrote: > I would say that having the default be 'portable' (which itself may just > be an alias to portable-2018 much like compress=on is now LZ4), makes the > most sense. If a user wants to use a feature that is not included in that, > 'zpool upgrade -o features=al

Re: [developer] OpenZFS feature flag at zpool create proposal

I would say that having the default be 'portable' (which itself may just be an alias to portable-2018 much like compress=on is now LZ4), makes the most sense. If a user wants to use a feature that is not included in that, 'zpool upgrade -o features=all' or specifically enabling individual featur

Re: [developer] OpenZFS feature flag at zpool create proposal

On Fri, Dec 7, 2018, at 2:48 PM, Richard Elling wrote: > > People don't read man pages, so they won't read about this option or > any of the other options.> For those people who do read man pages, we can > simply document the > appropriate flags> and their shortcut aliases. > > But... people

Re: [developer] OpenZFS feature flag at zpool create proposal

On Fri, Dec 7, 2018, at 11:50 AM, Matthew Ahrens wrote: > > > On Thu, Dec 6, 2018 at 11:17 AM Matthew Ahrens > wrote:>> >> >> On Thu, Dec 6, 2018 at 10:06 AM Josh Paetzel wrote:>>> __ >>> >>> >>> >>> On Thu, Dec 6, 2018, at 11:40 AM, Matthew Ahrens wrote: On Wed, Dec 5, 20

Re: [developer] OpenZFS feature flag at zpool create proposal

implementation > gathers this info into one place but it can probably just be one giant > table that we add an entry to each year. We can retroactively create > entries starting from 2013 or 2014 (feature flags were introduced May 2012). > > --matt > > >> >> &g

Re: [developer] OpenZFS feature flag at zpool create proposal

--matt > > > > > From: Matthew Ahrens <mailto:mahr...@delphix.com> > Reply: openzfs-developer > <mailto:developer@lists.open-zfs.org> > Date: December 7, 2018 at 12:14:17 PM > To: openzfs-developer > <mailto:developer@lists.open-zfs.org> &g

Re: [developer] OpenZFS feature flag at zpool create proposal

2012). --matt > > > > From: Matthew Ahrens > Reply: openzfs-developer > > Date: December 7, 2018 at 12:14:17 PM > To: openzfs-developer > > Subject: Re: [developer] OpenZFS feature flag at zpool create proposal > > > > On Thu, Dec 6, 2018 at 11

Re: [developer] OpenZFS feature flag at zpool create proposal

On Thu, Dec 6, 2018 at 11:17 AM Matthew Ahrens wrote: > Add new options to "zpool create", "zpool upgrade", and "zpool set": > - zpool create -o features=portable-20XX (yearly values) > - zpool create -o features=portable > - zpool upgrade -o features=portable-20XX > - zpool upgrade -o feature

Re: [developer] OpenZFS feature flag at zpool create proposal

, plus ‘portable’ (though a number of values might be equivalent) today. From: Matthew Ahrens Reply: openzfs-developer Date: December 7, 2018 at 12:14:17 PM To: openzfs-developer Subject: Re: [developer] OpenZFS feature flag at zpool create proposal On Thu, Dec 6, 2018 at 11:17 AM

Re: [developer] OpenZFS feature flag at zpool create proposal

Matt, thanks for update. can we print feature=portable by: zpool get feature-portable ? probably we need pool property for it , because we need to know feature for upgrade. -Igor >> >> >> On Wed, Dec 5, 2018 at 9:21 PM Josh Paetzel > > wrote: >> There was a proposal on

Re: [developer] OpenZFS feature flag at zpool create proposal

On Thu, Dec 6, 2018 at 11:17 AM Matthew Ahrens wrote: > > > On Thu, Dec 6, 2018 at 10:06 AM Josh Paetzel wrote: > >> >> >> >> On Thu, Dec 6, 2018, at 11:40 AM, Matthew Ahrens wrote: >> >> >> >> On Wed, Dec 5, 2018 at 9:21 PM Josh Paetzel wrote: >> >> There was a proposal on this mailing list a

Re: [developer] OpenZFS feature flag at zpool create proposal

> On Dec 7, 2018, at 7:23 AM, a...@omniosce.org wrote: > >> On Thursday, December 06, 2018, at 7:21 PM, Joshua M. Clulow wrote: >> I think for illumos we would say something like: features are reasonably >> expected to be available for "portable" use in all distributions when >> they've been i

Re: [developer] OpenZFS feature flag at zpool create proposal

On Thursday, December 06, 2018, at 7:21 PM, Joshua M. Clulow wrote: > I think for illumos we would say something like: features are reasonably expected to be available for "portable" use in all distributions when they've been in the upstream illumos-gate repository for a certain length of time; e.g

Re: [developer] OpenZFS feature flag at zpool create proposal

let me play devil's advocate here: On Thu, Dec 6, 2018 at 6:41 PM Matthew Ahrens wrote: > > [...] > > 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. > > I think t

Re: [developer] OpenZFS feature flag at zpool create proposal

On 06/12/2018 17:40, Matthew Ahrens wrote: On Wed, Dec 5, 2018 at 9:21 PM Josh Paetzel mailto:j...@tcbug.org>> 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 th

Re: [developer] OpenZFS feature flag at zpool create proposal

On Thu, Dec 6, 2018 at 11:20 AM Josh Paetzel wrote: > > > > On Thu, Dec 6, 2018, at 12:23 AM, Rich via openzfs-developer wrote: > > On Thu, Dec 6, 2018 at 12:19 AM Josh Paetzel wrote: > > > > > > There was a proposal on this mailing list a week or so ago that sparked > > > some good discussion r

Re: [developer] OpenZFS feature flag at zpool create proposal

On Thu, Dec 6, 2018, at 1:17 PM, Matthew Ahrens wrote: >> >> 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 p

Re: [developer] OpenZFS feature flag at zpool create proposal

On Thu, 6 Dec 2018 at 10:27, Igor Kozhukhov wrote: > 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 ? I don't think a tag will be particularly helpful. In your example you list "Ubuntu

Re: [developer] OpenZFS feature flag at zpool create proposal

On Thu, Dec 6, 2018 at 10:06 AM Josh Paetzel wrote: > > > > On Thu, Dec 6, 2018, at 11:40 AM, Matthew Ahrens wrote: > > > > On Wed, Dec 5, 2018 at 9:21 PM Josh Paetzel wrote: > > There was a proposal on this mailing list a week or so ago that sparked > some good discussion regarding setting feat

Re: [developer] OpenZFS feature flag at zpool create proposal

>> >> >> On Wed, Dec 5, 2018 at 9:21 PM Josh Paetzel > > 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

Re: [developer] OpenZFS feature flag at zpool create proposal

On Thu, Dec 6, 2018, at 11:40 AM, Matthew Ahrens wrote: > > > On Wed, Dec 5, 2018 at 9:21 PM Josh Paetzel 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

Re: [developer] OpenZFS feature flag at zpool create proposal

On Wed, Dec 5, 2018 at 9:21 PM Josh Paetzel 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

Re: [developer] OpenZFS feature flag at zpool create proposal

On Thu, Dec 6, 2018, at 12:23 AM, Rich via openzfs-developer wrote: > On Thu, Dec 6, 2018 at 12:19 AM Josh Paetzel 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 > > discusse

Re: [developer] OpenZFS feature flag at zpool create proposal

On Dec 5, 2018, at 9:19 PM, Josh Paetzel wrote: > > The proposal is to add an optional flag at zpool create time. -o features= My proposal was to have a compatibility option, and have a set of features that each of the players can agree to. Once a quarter, or whatever. The complication is ho

Re: [developer] OpenZFS feature flag at zpool create proposal

On Thu, Dec 6, 2018 at 12:19 AM Josh Paetzel 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

[developer] OpenZFS feature flag at zpool create proposal

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. This pr