FreeBSD support being added to GlusterFS

[Jordan Hubbard]

On Jun 29, 2014, at 12:12 PM, Harshavardhana <harsha at harshavardhana.net> wrote:

> The patches are pending review and will be pushed hopefully this week!

Cool!

> - can i get these installed on a Virtualbox instance and test the
> failures?

Sure, you can always install http://download.freenas.org/nightlies/9.3/ALPHA/20140625/ and install it under VirtualBox - that has the glusterfs port in it as currently described by https://github.com/freenas/ports/tree/freenas/9-stable/sysutils/glusterfs (I love github!).   I tried updating that port to Baptiste’s latest version last night, but like I said, it croaked during the build process so I couldn’t get another 9.3 nightly done and ended up simply reverting the changes for now.

That 2nd URL will also show you the current state of the Makefile and patches we needed to get glusterfs compiling under FreeNAS, which may prove instructive as to why “our version” builds and the other does not.

Longer-term, once we get glusterd to not simply fall over with missing paths, if desired I can also create the glusterfs team an externally-facing VMWare VM containing the latest FreeNAS 9.3 build if they want to be able to test interoperability or otherwise beat on it to their heart’s content.  We do this for the Samba project as well, since there’s nothing like seeing one's code actually running in the target NAS environment to ensure it actually works, and it’s easy to install nightly builds on it if and as things evolve.

> Do not understand what is "poudriere" build? - is it like building
> inside a chrooted environment?

In essence, yes, though it also provides some other nice features that accelerate the process of building appliances based on freebsd packages.  See https://fossil.etoilebsd.net/poudriere/doc/trunk/doc/index.wiki for reference.

> The changes regarding "/var/lib" to "/var/db" are not complete with
> the diff, in-fact inside the code - "DEFAULT_WORKDIR
> /var/lib/glusterd" is hard-coded - and its only complete until all the
> references point to "/var/db/glusterd"
> 
> I will be making these changes this week. Is "/var/db" the directory
> we all agree upon for "glusterd" configuration files?

I believe so, yes.

Thanks!

- Jordan