CEPH + FreeBSD

[Greg Troxel]

Jordan Hubbard <jordanhubbard at icloud.com> writes:

> One is glusterfs, for which I’m not even really clear on the status of
> the ports for.  I don’t see any glusterfs port in the master branch of
> https://github.com/freebsd/freebsd-ports (or
> https://github.com/freebsd/freebsd-ports/tree/branches/2015Q3 for that
> matter).
>
> [snip]
>
> I’m not really sure about the provenance since we were simply
> evaluating glusterfs for awhile and may have pulled in interim
> versions from those sources, but obviously it would be best to have an
> official maintainer and someone in the FreeBSD project actually
> curating a glusterfs port so that all users of FreeBSD can use it.  It
> would also be fairly key to your own efforts, assuming you decide to
> pursue glusterfs as a foundation technology for pNFS.

Emmanual Dreyfus has been working on glusterfs for NetBSD, and it seems
to work quite well.  So most of the BSD-shared porrtability issues are
worked out.  gluster needs the low level FUSE API.  On NetBSD, we have
puffs in the kernel which is FUSE-like, and librefuse to impelment FUSE
on puffs (all BSD licensed).  Then there is a low-level API daemon
perfuse.  gluster and perfuse are in pkgsrc.

So if FreeBSD has the low-level FUSE API, it will probably mostly work.
However, gluster was a tough user of FUSE, and shook out a lot of
obscure edge cases.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 180 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20150914/3c3beddb/attachment.bin>