Re: CFT for vendor openzfs - week 4 reminder + memdisk images

On Wed, Jul 29, 2020 at 20:16 Chris <bsd-lists_at_bsdforge.com> wrote:

> On Tue, 28 Jul 2020 21:16:28 -0700 Matthew Macy mmacy_at_freebsd.org said
>
> > On Tue, Jul 28, 2020 at 21:06 Chris <bsd-lists_at_bsdforge.com> wrote:
> >
> > > On Tue, 28 Jul 2020 20:50:33 -0700 Matthew Macy mmacy_at_freebsd.org said
> > >
> > > > On Tue, Jul 28, 2020 at 20:43 Chris <bsd-lists_at_bsdforge.com> wrote:
> > > >
> > > > > On Tue, 28 Jul 2020 20:08:33 -0700 Matthew Macy mmacy_at_freebsd.org
> said
> > > > >
> > > > > > On Tue, Jul 28, 2020 at 8:03 PM Chris <bsd-lists_at_bsdforge.com>
> > > wrote:
> > > > > > >
> > > > > > > On Tue, 28 Jul 2020 19:10:21 -0700 Matthew Macy
> mmacy_at_freebsd.org
> > > said
> > > > > > >
> > > > > > > > On Wednesday, July 8th I issued the initial call for testing
> for
> > > the
> > > > > > > > update to HEAD to vendored openzfs. We'd like to give users
> > > roughly a
> > > > > > > > month to test before merging.  The tentative merge date is
> August
> > > > > > > > 17th.
> > > > > > > >
> > > > > > > > Again, I hope it's not terribly controversial to point out
> that
> > > > > > > > it really rests with users of non amd64 platforms to test to
> > > avoid
> > > > > any
> > > > > > > > unpleasant surprises the next time they update their trees
> > > following
> > > > > > > > the merge.
> > > > > > > >
> > > > > > > > amd64, i386, and aarch64 memdisk images can be found at:
> > > > > > > >
> > > > > > >
> > > > >
> > > > >
> > >
> > >
> https://people.freebsd.org/~freqlabs/freebsd-openzfs-3d833bea-f10f94aa-2020072900/
> > > > > > >
> > > > > > > Is this in an attempt to replace the opensolaris version used
> now?
> > > > > >
> > > > > > The word "attempt" is a misnomer. If you search the mail archives
> > > this
> > > > > > has been the PoR for some time.
> > > > > Sure. OK. I caught this thread. But must have missed the
> announcement
> > > > > of the intent to replace the opensolaris version with openzfs.
> > > > > Do you recall which mailing list that was made to?
> > > > >
> > > > > Thank you for your quick reply, Matthew.
> > > > >
> > > >
> > > > Apart from the 3 previous CFT mails, the initial intent was
> discussed in
> > > > December 2018. Getting FreeBSD support integrated in to openzfs took
> a
> > > lot
> > > > more incremental PRs than I anticipated.
> > > >
> > > >
> > >
> > >
> https://lists.freebsd.org/pipermail/freebsd-current/2018-December/072422.html
> > >
> > > Thank you very much, Mathew. Sorry for any bother.
> > >
> >
> >
> > No bother or not much at least. It’s just been a long haul and I’d like
> > to
> > wrap this up.
> No doubt.
> FTR I'm not looking to impede you. :-)
> My only concern would be that I'd need to remaster the art of ZFS. I've
> got 1500 installs to maintain, and any changes tend to alarm me. :-)
> I see we're a bit behind the others, if this status report is current:
>
> https://docs.google.com/spreadsheets/d/1CFapSYxA5QRFYy5k6ge3FutU7zbAWbaeGN2nKVXgxCI/edit#gid=0
> Will your impending commit move us closer? Is there anything others
> like myself can do to help?


Close to 90% of the sources files in openzfs are shared between Linux and
FreeBSD. So the features will, give or take a line item, be the same. For
non developers the main thing they can do to help out is to run it in their
own environments to identify any changes in behavior or regressions. If
you’re doing 1500 installs it’s in your best interest to make this as
smooth a transition as possible. However, it’s not something you’re going
to face until you move to 13. The openzfs port is available to those who
want to run it on 12.

-M

>
>
> Thanks again, Matthew.
>
> --Chris
> >
> > -M
> >
> > >
>
>
>