I am a bit lost here.. so pardon me if I am misquoting something.
But I really wanted to know where does /usr/sbin/gluster sits, i mean
which RPM ?
Currently VDSM needs /usr/sbin/gluster since thats needed by gluster cli
plugin of VDSM.
This gluster plugin gets used to query the transport type as part of
GLUSTERFS_DOMAIN storage domain usecase.
Currently, this is what i see...
rpm -qf /usr/sbin/gluster
glusterfs-server-3.4.0beta1-1.fc17.x86_64
which means for somebody to use gluster vdsm plugin, one needs to
install glusterfs-server rpm.
But from VDSM spec file...
%if 0%{?with_gluster}
%package gluster
Summary: Gluster Plugin for VDSM
BuildArch: noarch
Requires: %{name} = %{version}-%{release}
Requires: glusterfs >= 3.4.0
Requires: glusterfs-server
Requires: glusterfs-fuse
Requires: glusterfs-rdma
Requires: python-magic
which means, that if the hypervisor host is not a gluster node,
vdsm-gluster RPM is optional
and if User doesn't install it.. he won't get glusterfs-server, and
hence no /usr/sbin/gluster
and because of this, we run into
https://bugzilla.redhat.com/show_bug.cgi?id=988299
Based on my debug, it seems like the absence of gluster binary is the
root cause here, tho' I can confirm
once the BZ reported gives back more info.
VDSM (which is eq. to hypervisor host) in this case is a hyp. only host,
hence vdsm-gluster is not a necessity
but it can be a gluster client (as part of User using GLUSTERFS_DOMAIN
storage domain), for which the hyp. only host
still needs /usr/sbin/gluster binary.
To clarify further... vdsm/storage/gluster/cli.py is not part of
vdsm-gluster rpm, its part of vdsm package.. and this was done long back
to ensure VDSM acting as gluster client doesn't necessarily need to
install vdsm-gluster rpm. But since /usr/sbin/gluster is part of
glusterfs-server, the problem is resurfaced.
I wanted to understand for the above scenario... where VDSM is just a
gluster client.. what RPM (post the re-structuring) will be needed to be
installed on the VDSM hyp. only host ? This also means post RPM
re-structuring we need to change vdsm.spec.in too
thanx,
deepak
