DevHeads.net

building nfs-ganesha for ceph

Hi Niels and Kaleb,

I'm wondering how we could best build nfs-ganesha's ceph FSALs in CBS.

Right now, since we'll likely support multiple versions of nfs-ganesha
simultaneously for different versions of Ceph, I'm leaning towards
using a custom "dist tag" like thing in the Release field so we don't
collide with what Kaleb's doing at
<a href="http://cbs.centos.org/koji/packageinfo?packageID=98" title="http://cbs.centos.org/koji/packageinfo?packageID=98">http://cbs.centos.org/koji/packageinfo?packageID=98</a>

Eventually it would be nice to have a unified nfs-ganesha build shared
between Ceph and Gluster. If we built it in storage7-common-candidate,
we would have to tag gluster and ceph into that, which sounds kinda
messy, because you only get to choose one version of each. It'd be
more manageable to have a separate set of tags and targets just for
nfs-ganesha versions. Like:

storage7-nfs-ganesha-26-el7
storage7-nfs-ganesha-27-el7
... etc

But that still leaves the problem of shipping a nfs-ganesha-gluster
sub-package that will not have its runtime deps fulfilled in
<a href="http://mirror.centos.org/centos/7/storage/x86_64/ceph-nautilus/" title="http://mirror.centos.org/centos/7/storage/x86_64/ceph-nautilus/">http://mirror.centos.org/centos/7/storage/x86_64/ceph-nautilus/</a> . Vice
versa, we'd have a nfs-ganesha-ceph sub-package that lacks runtime
deps in <a href="http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/" title="http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/">http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/</a>

What do you think? Just have separate nfs-ganesha builds for now?

- Ken