Date: Sat, 28 Jun 2014 00:34:56 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Jordan Hubbard <jkh@turbofuzz.com> Cc: freebsd-fs@freebsd.org Subject: Re: FreeBSD support being added to GlusterFS Message-ID: <20140627223456.GD34108@ivaldir.etoilebsd.net> In-Reply-To: <AB0CB58A-A93E-4DDA-8060-A2B183BBB6FD@turbofuzz.com> References: <C647EDA1-EA93-4A66-B59D-3B5F959DC0E0@gluster.org> <6ADBB2BF-C7E8-4050-9278-2565A63D2EA8@gluster.org> <20140627070411.GI24440@ivaldir.etoilebsd.net> <AB0CB58A-A93E-4DDA-8060-A2B183BBB6FD@turbofuzz.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--3Gf/FFewwPeBMqCJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 27, 2014 at 02:27:35PM -0700, Jordan Hubbard wrote: >=20 > On Jun 27, 2014, at 12:04 AM, Baptiste Daroussin <bapt@FreeBSD.org> wrote: >=20 > > For you information here is my version: > > http://people.freebsd.org/~bapt/glusterfs.diff > >=20 > > It is just missing the license bits > >=20 > > if everyone here agrees I'll commit :) >=20 > Seems reasonable. Question from my own "questions to be asked about glus= terfs" pile: Paths. I notice that glusterd requires quite a few path not = in the standard hierarchy for /usr/local (or any value of ${prefix}) that w= ill cause it to simply fall over upon first invocation. To wit: >=20 > /var/lib/glusterd (nothing in FreeBSD uses /var/lib at all - /var/db, /va= r/run and /var/tmp are more canonical locations, depending on what you [the= service] are trying to do). >=20 > In fact, ${prefix}/var seems to be generally avoided by most things in po= rts. /usr/local/var/log is highly atypical, for example. >=20 > This also creates problems for us in FreeNAS since our root filesystem is= read-only by default, and we simply make parts of /var (the root /var) r/w= to accommodate things wanting to write into /var/log, /var/tmp/, /var/run = and so on. I would hope that the port could also be configured to run as a= system component, or at least obey a more predictable ${prefix} hierarchy = so that we could map things suitably r/w into the location(s) that glusterf= s needs to scribble on at runtime. >=20 > I was going to write all of this up in a more exhaustive email but I got = side-tracked by other projects. :) >=20 > - Jordan >=20 >=20 >=20 Here is a new version which uses /var/db, /var/log and /var/run This version also works with pkg_install and handle the /var/db/glusterd/groups/virt file as a config file so it will not overwrite= user one on reinstallation. I haven't added the license as I do not understand the license from the COP= YING files I see GPLv2 and LGPLv3 but from the website I see GPLv3, can someone enlighten me? I'm still looking for a better maintainer then me :) I mean I can make sure= the port/package is clean, I can also help on the fuse part if needed, but I ha= ve no use case so far on glusterfs beside highly supporting it on FreeBSD and bei= ng excited by the features it provides :) Maybe someone at FreeNAS it willing to take maintainership of this port in = the ports tree? Jordan does this new port fits FreeNAS requirements? regards, Bapt --3Gf/FFewwPeBMqCJ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlOt8ZAACgkQ8kTtMUmk6EwrHgCfZ4Ytw1GDQ1ZpjT1lIfEYJ+P+ 2VcAoKl8muHSjMegyqU2U7Tx6ehQEMi/ =w/O7 -----END PGP SIGNATURE----- --3Gf/FFewwPeBMqCJ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140627223456.GD34108>