glusterfs.git/glusterfs.spec.in, branch v3.4.0beta4

rpm: move the mount/api xlator to the glusterfs-api sub-package

2013-06-26T13:35:24+00:00

The main glusterfs package included the xlator/api.so file which caused
a dependency on the glusterfs-api package:

  # rpm -i glusterfs-3.4.0-0.6.beta3.el6.x86_64.rpm
  error: Failed dependencies:
  libgfapi.so.0()(64bit) is needed by glusterfs-3.4.0-0.6.beta3.el6.x86_64

Moving the mount/api xlator to the glusterfs-api package will prevent
the automatic dependency generator to add the dependency to the main
package.

Change-Id: I333c6b61dfc239a7b0beca313aa5928f4e197937
BUG: 819130
Reported-by: Vijay Bellur 
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/5254
Reviewed-by: Kaleb KEITHLEY 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

build: sync glusterfs.spec.in with Fedora glusterfs.spec

2013-06-21T17:32:39+00:00

(This is the release-3.4 branch.)

 * remove G4S/UFO from community packaging. The Fedora/EPEL packaging
   will follow suit once the glusterfs-openstack-swift packaging
   materializes from the G4S team. Note that for the time being 'make dist'
   still creates a UFO tarball from the .../ufo directory for use by
   fedora packaging.
 * add glusterfs-api and glusterfs-api-devel sub-packages
 * add extras/systemd/glusterd.service. Use it (or extras/init.d/glusterd)
   instead of the Fedora versions.
 * restores ability to build glusterfs RPMs from the dist tarball with
   'rpmbuild {-ts,-tb,-ta} glusterfs-XXX.tar.gz'
 * reverse {--with,--without}_fusermount in sync with fedora .spec and
   master branch
 * other minor cleanups mostly to sync with fedora .spec and to build
   from the dist tarball. Any differences will be resolved in the fedora
   .spec in the next release (i.e. beta4 or GA).
 * this is nominally for "the impending merge of .../api from master" but
   should be independent of that change.

(still deciding whether to add the fedora glusterfsd.{init,service) files
here or remove them from fedora.)

BUG: 819130
Change-Id: I90c7355ca02239995b1df7646e3cd10ec227bcc5
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/5179
Reviewed-by: Niels de Vos 
Tested-by: Gluster Build System

rpm: automatically load the fuse module on EL5

2013-05-29T18:26:40+00:00

The fuse module needs to be loaded before /dev/fuse can be used. On
RHEL6 and Fedora the module is loaded on demand. RHEL5 needs to load the
module manually.

This change add a script under /etc/sysconfig/modules/ that loads the
fuse module on boot and packages it in the EL5 version of
glusterfs-fuse.

One of the features of GlusterFS is to not depend on additional fuse
userspace. The conditional requires on /usr/bin/fusermount is not
needed, this command is never called in the current version (even though
is it referenced in the sources).

BUG: 947830
Change-Id: I166327b8f2dff2c150368bdf5ea917af259186b2
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/5102
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Vijay Bellur

build: sync glusterfs.spec.in with Fedora glusterfs.spec

2013-04-26T15:17:02+00:00

BUG: 819130
Change-Id: I96aeb8fbe8b79bbc058ff9a45167d822abb576ed
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/4877
Tested-by: Gluster Build System 
Reviewed-by: Niels de Vos

object-storage: rebase Swift to 1.8.0 (grizzly)

2013-04-12T07:23:04+00:00

Merged (git cherry-pick) from master/HEAD to release-3.4

Change-Id: I24265c12a45eac4cec761748096118c9647440be
BUG: 948041
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/4780
Reviewed-by: Jeff Darcy 
Tested-by: Gluster Build System

build: add BuildRequires librdmacm-devel

2013-04-12T07:20:14+00:00

See http://review.gluster.org/149

Installed librdmacm-devel RPM on the build server.

cherry pick from http://review.gluster.org/#/c/4804/

BUG: 819130
Change-Id: I30e14ebf7646c19923940f86a72bf42497cac70c
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/4806
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy

glusterfs.spec.in: sync with fedora glusterfs.spec

2013-03-28T21:28:24+00:00

add --without ufo

cherry-pick from refs/changes/42/4742/1

Change-Id: If1b77003ded537f9664fa6ad677d48d118516c64
Signed-off-by: Kaleb S. KEITHLEY 
BUG: 819130
Reviewed-on: http://review.gluster.org/4743
Tested-by: Gluster Build System 
Tested-by: Luis Pabon 
Reviewed-by: Luis Pabon 
Reviewed-by: Anand Avati

glusterfs.spec.in: resync with Fedora glusterfs.spec

2013-03-27T01:28:54+00:00

cherry-pick from master, including commits:
 5d3b478e76f1015b11bfd7d48465ab12a4f0737e
 fd407a4f5cdb869dc52efe8fc9e1d284f60f5992
 6f6789884227b8260f140c39c063d77b0516af97
 84f5e4b354526fbb7f0665345816e81c81245c8f
 2398e1e0da61f4ec5f209c704e037b54b5c249e1

Resync with Fedora's glusterfs.spec

To build a set of RPMs:
 % ./autogen.sh
 % ./configure --enable-fusermount
 % make dist
 % cd extras/LinuxRPM && make glusterrpms

Updated rpm.t

BUG: 819130
Signed-off-by: Kaleb S. KEITHLEY 
Change-Id: Ib73be0fbb7ee16a5c41b4f7c7a3f66d0224bfe6c
Reviewed-on: http://review.gluster.org/4725
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

rpm: package /var/run/gluster so that statedumps can be created

2013-03-12T15:09:11+00:00

Creating statedumps fail when /var/run/gluster does not exist. This
directory should be part of the 'glusterfs' package that is installed on
storage servers and native clients.

Merged Niels's change from both $HEAD and release-3.3

BUG: 917554
Change-Id: I6ffc497c0bb6bc90c97a91a72bba9118853d4c8c
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/4659
Tested-by: Gluster Build System 
Reviewed-by: Niels de Vos

build: glusterfs-server should own known files under /var/lib/glusterd

2013-01-19T03:34:24+00:00

In continuation of Change-Id Ib1df8da7e8abdcd3edece45bd39fe238f28838f1
there are more files that should be owned by the glusterfs-server
package.

Note that starting glusterd, doing some peer-probes and creating volumes
will create additional run-time files under /var/lib/glusterd. The
filenames depend on the volumes that are created, and that prevents
packages from knowing (and owning) them in advance. It seems common
practice to leave files untouched under /var/lib/.

It would be okay to remove files generated by the package itself, but we
should not remove files generated by other packages, or files that have
been created by users manually. I do not see a way to detect files
generated by gluster* applications and remove only these. Keeping the
runtime files under /var/lib/glusterd (which do not have predictive
names) is safe and they should not require much space anyway.

BUG: 829734
Change-Id: I2b79682b014fcf62c2a73f076cf0b11b4ba87f4a
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/4361
Reviewed-by: Kaleb KEITHLEY 
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati