On Mon, Jul 29, 2013 at 12:18 AM, Anand Avati <anand.avati@xxxxxxxxx> wrote: > > Another model can be: > > 0. glusterfs-libs.rpm - libglusterfs.so libgfrpc.so libgfxdr.so > 1. glusterfs (depends on glusterfs-libs) - glusterfsd binary, glusterfs > symlink, all common xlators > 2. glusterfs-rdma (depends on glusterfs) - rdma shared library > 3. glusterfs-geo-replication (depends on glusterfs) - geo-rep related > objects > 4. glusterfs-fuse (depends on glusterfs) - fuse xlator, mount.glusterfs > 5. glusterfs-server (depends on glusterfs) - server side xlators, config > files > 6. glusterfs-api (depends on glusterfs-libs) - libgfapi.so and api.so > 7. glusterfs-resource-agents (depends on glusterfs) > 8. glusterfs-devel (depends on glusterfs-libs) - header files for > libglusterfs > 9. glusterfs-api-devel (depends on glusterfs-api) - header files for gfapi > > This way qemu will only pick up libgfapi.so libglusterfs.so libgfrpc.so and > libgfxdr.so (the bare minimum to "just execute") for the binary to load at > run time. Those who want to store vm images natively on gluster must also do > a 'yum install glusterfs' to make gfapi 'useful'. This way Fedora qemu users > who do not plan to use gluster will not get any of the xlator cruft. +1 Regards, Bharata.
