From owner-freebsd-fs@FreeBSD.ORG Fri Jun 27 22:35:03 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 439C9DF5 for ; Fri, 27 Jun 2014 22:35:03 +0000 (UTC) Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA08A24BC for ; Fri, 27 Jun 2014 22:35:02 +0000 (UTC) Received: by mail-we0-f178.google.com with SMTP id x48so5722825wes.9 for ; Fri, 27 Jun 2014 15:34:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=x3VuX/2HmcIpzNV2FhkAS/KN4y2dI4fkT9gPj81ufQg=; b=UwpggeJKEbMOrJrVqVBqnpylcKRRaAfkQqd081xSEKWAj17ex0xksh9yCQdV0J69v+ fxxOzKrb1UXW0Uk5F+DdfpLsDKe+Nyvkp0iS8rUltBenoo/PI7jlzSUy6jBjGTdKUCo0 qKa8pC0CsmEWcznPkr8J3U5tgOrfQK8zJhGpJe2bz6WKtarPvU7AV1PJw57jUdyLxAd1 CLplWIDmizIzP/peRQtKlYBpo/DZIULT/efIBvLXELK4JEuffcl5+PshtEnw/I9eLfgD A7g9fMftX6qI0ueEnR+Qs1xHzwhsVfJ00wMPWlq0XxPHb0MxQ9DdvjbqU16C+WYbFE5i 4iPg== X-Received: by 10.194.237.135 with SMTP id vc7mr29399183wjc.86.1403908499690; Fri, 27 Jun 2014 15:34:59 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id d3sm1233618wiy.13.2014.06.27.15.34.58 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Jun 2014 15:34:58 -0700 (PDT) Sender: Baptiste Daroussin Date: Sat, 28 Jun 2014 00:34:56 +0200 From: Baptiste Daroussin To: Jordan Hubbard Subject: Re: FreeBSD support being added to GlusterFS Message-ID: <20140627223456.GD34108@ivaldir.etoilebsd.net> References: <6ADBB2BF-C7E8-4050-9278-2565A63D2EA8@gluster.org> <20140627070411.GI24440@ivaldir.etoilebsd.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3Gf/FFewwPeBMqCJ" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2014 22:35:03 -0000 --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 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--