On Fri, Nov 22, 2013 at 12:36:41PM -0500, Bob Doolittle wrote:
On 11/22/2013 11:45 AM, Dan Kenigsberg wrote:
On Fri, Nov 22, 2013 at 05:51:48PM +0200, Itamar Heim wrote:
doesn't vdsm require vdsm-gluster which requires them? vdsm requires vdsm-gluster only in gluster, gluster+virt clusters. Hence if gluster server side functionality is being exercised, we would need to use EPEL packages.
For a virt only cluster, only the client side packages are needed and RHEL 6.5 has these packages. vijay - didn't we add gluster-cli for libgfapi support in core vdsm? glusterVolume uses the cli to only to tell if it's using tcp or rdma. This vdsm dependency is currently a soft one (not declared in the spec), and would only affect users which attempt to user true glusterfs storage domains without installing gluster-cli.
This is not what I see. I see that vdsm.x86_64 has a dependency on glusterfs-cli:
# rpm -qa --whatrequires glusterfs-cli vdsm-4.12.1-4.el6.x86_64
You are correct. My statement about vdsm's dependency is valid only for the not-yet-released rhev-3.3.0 (and thus, is not really apropriate for this venue).
Hence the problem, since the new version of glusterfs does not deliver this package.
I still think that your problem stems from mixing and matching epel-gluster repositories with rhs ones. It would be easier to deploy oVirt+epel-gluster and rhev+rhs. Dan.