[Gluster-devel] New features and their location in packages

[Ravishankar N]

On 03/26/2015 02:45 AM, Niels de Vos wrote:
> With all the new features merged, we need to know on what side of the
> system the new xlators, libraries and scripts are used. There always are
> questions on reducing the installation size on client systems, so
> anything that is not strictly needed client-side, should not be in the
> client packages.
>
> For example, I would like to hear from all feature owners, which files,
> libraries, scripts, docs or other bits are required for clients to
> operate.
Hi Niels,
For AFR arbiter (BZ 1199985), the 'features/arbiter' xlator will be on 
the server side. The client bits that are needed to make it work will  
be a part of AFR code.
Thanks,
Ravi

>   For example, here is what tiering does:
>
>    - client-side: cluster/tiering xlator
>    - server-side: libgfdb (with sqlite dependency)
>
> By default, any library is included in the glusterfs-libs RPM. If the
> library is only useful on a system with glusterd installed, it should
> move to the glusterfs-server RPM.
>
> Clients include fuse and libgfapi, the common package for client-side
> bits (and shared client/server bits) is 'glusterfs'. There is no need
> for you to post patches for moving files around in the RPMs, that is
> something I can do in one go. Just let me know which files are needed
> where.
>
> Thanks!
> Niels
>
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20150331/b84ee8d2/attachment.html>