Date: Sat, 16 Aug 2014 19:57:02 -0700 From: Jordan Hubbard <jkh@ixsystems.com> To: Harshavardhana <harsha@harshavardhana.net> Cc: freebsd-fs@freebsd.org Subject: Re: FreeBSD support being added to GlusterFS Message-ID: <2F416D06-0A98-4E66-902C-ED0690A4B1C0@ixsystems.com> In-Reply-To: <CAAeUqd3ycv=Bsz6UiZEKaPJXpGnf8Rts8j29O6R6q-WucXqYug@mail.gmail.com> References: <C647EDA1-EA93-4A66-B59D-3B5F959DC0E0@gluster.org> <6ADBB2BF-C7E8-4050-9278-2565A63D2EA8@gluster.org> <20140627070411.GI24440@ivaldir.etoilebsd.net> <0F20AEEC-6244-42BC-815C-1440BBBDE664@mail.turbofuzz.com> <20140629203746.GI34108@ivaldir.etoilebsd.net> <CAAeUqd0=CdwaVjZjUc4PKxD_gxpydVqCy4tebywi=iV3gkpz1Q@mail.gmail.com> <1A58F492-946F-46D4-A19E-2734F368CDAC@mail.turbofuzz.com> <CAAeUqd1m_FxPWCVft5tmeok8QFsEZWGM-5QV20=mq8MeU=7EbA@mail.gmail.com> <0ABAE2AC-BF1B-4125-ACA9-C6177D013E25@mail.turbofuzz.com> <CAAeUqd3ZoF7XUmLwvL7y_VorO1JfdtVk=RKcW2rVHKdoVOBRAw@mail.gmail.com> <20140706230910.GA8523@ivaldir.etoilebsd.net> <CAAeUqd3ycv=Bsz6UiZEKaPJXpGnf8Rts8j29O6R6q-WucXqYug@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks! Just to make sure I understand for our own ports repo in = FreeNAS-land: 1. You have updated the tarball but Baptiste is still maintaining the = port, correct? If Baptiste would like someone else to take it over, I can probably coax = one of our resident committers to do it as well. We frankly have not = been able to do any testing of glusterfs in FreeNAS yet since glusterd = just catches a signal 10 whenever any glusterfs operation is performed. = Since this is also really early BETA software, I figured the FreeBSD = port was still a bit green and I'd simply wait for it to get a bit more = mature. Now that you say you=92ve gotten a regression suite up and = running, I=92m guessing the time to really push on it in FreeNAS = 9.3-ALPHA is probably soon? 2. That said, it also sounds like updating the glusterfs port is going = to have to wait for your cmockery2 port to get accepted and committed to = the tree, since otherwise it won=92t build - is that a correct = assessment? Cheers, - Jordan On Aug 11, 2014, at 1:25 AM, Harshavardhana <harsha@harshavardhana.net> = wrote: > = http://download.gluster.org/pub/gluster/experimental/glusterfs-freebsd_201= 40811.tar.bz2 > - updated tar with >=20 > - libexecinfo part of glusterfs 'contrib' > - Gluster configuration changed from "/var/lib" to "/var/db" by > default for non-linux platforms. > - First attempt to get regression tests ported to FreeBSD > - Currently the build is dependent on 'cmockery2' for which i > submitted a new port request here - > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192420 (not merged > yet) >=20 > Let me know how the testing goes. >=20 > BTW as an off topic but related to GlusterFS regression tests - i have > been trying to get 'pidof' command really working on FreeBSD but seems > like its really un-usable and doesn't behave the same way as the > sysvinit `pidof` does. >=20 >=20 > On Sun, Jul 6, 2014 at 4:09 PM, Baptiste Daroussin <bapt@freebsd.org> = wrote: >> On Sun, Jul 06, 2014 at 12:13:15PM -0700, Harshavardhana wrote: >>>>=20 >>>> I can make the /usr/local/var/log/glusterfs directory and it gets = much further. That said, is there some special configure flags we = should be passing in our version of the port to properly stuff glusterfs = into /var instead? Your email tends to imply that we should be passing = =97localstatedir, which we can certainly do no problem, I=92m just = wondering if that=92s your long-term plan. Again, this is our port: = https://github.com/freenas/ports/tree/freenas/9-stable/sysutils/glusterfs >>>>=20 >>>> The fundamental issue with /usr/local is, again, that /usr/local is = read-only on FreeNAS. If there are configuration files that glusterfs = expects to be modifiable, they can=92t live anywhere in /usr/local, nor = of course can any temporary files or log files. We have made special = provisions for /etc and /var such that those can be modified, so we = basically just need to compile gluster as a =93system service=94 and put = it in the system directories (e.g. prefix is /, not /usr/local). >>>>=20 >>>=20 >>> Ah now i get it - "/usr/local" is not a requirement for "GlusterFS" = it >>> is a baggage of using "autotools" when during ./configure if you do >>> not specify --prefix - so for a standard installation under RPM it = is >>> usually the following flags are used >>>=20 >>> # ./configure --prefix=3D/usr --sysconfdir=3D/etc = --localstatedir=3D/var >>> --libdir=3D/usr/lib64 >>>=20 >>> Since FreeBSD doesn't need "/usr/lib64" you could just use for = packages >>>=20 >>> # ./configure --prefix=3D/usr --sysconfdir=3D/etc = --localstatedir=3D/var >>>=20 >>=20 >> Here is an updated version of my port >> http://people.freebsd.org/~bapt/glusterfs.diff >>=20 >> This time it passes poudriere (for those not aware of poudriere it is = for >> FreeBSD a bit like what mock is for fedora but on steroid :)) >>=20 >> What is new in there: dependency on bison that I missed the first = time, a >> dependency on libexecinfo (on non FreeBSD 10) and a build dependency = on git >> other build-aux/pkg-version is not happily catching the version >>=20 >> Tested on FreeBSD 10 >>=20 >> regards, >> Bapt >=20 >=20 >=20 > --=20 > Religious confuse piety with mere ritual, the virtuous confuse > regulation with outcomes
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2F416D06-0A98-4E66-902C-ED0690A4B1C0>