2013-06-17 21:44:10 +04:00
%global _hardened_build 1
2013-01-30 20:29:54 +04:00
%global _for_fedora_koji_builds 0
2009-02-18 15:06:07 +03:00
2013-06-17 21:44:10 +04:00
# uncomment and add '%' to use the prereltag for pre-releases
2013-12-10 16:26:46 +04:00
# %%global prereltag qa3
2013-06-17 21:44:10 +04:00
2014-02-28 09:40:51 +04:00
##-----------------------------------------------------------------------------
## All argument definitions should be placed here and keep them sorted
##
2018-08-10 02:32:22 +03:00
# asan
# if you wish to compile an rpm with address sanitizer...
# rpmbuild -ta @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz --with asan
%{?_with_asan:%global _with_asan --enable-asan}
%if ( 0%{?rhel} && 0%{?rhel} < 7 )
%global _with_asan %{nil}
%endif
2018-01-18 23:24:00 +03:00
# bd
# if you wish to compile an rpm without the BD map support...
# rpmbuild -ta @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz --without bd
%{?_without_bd:%global _without_bd --disable-bd-xlator}
2017-02-28 09:37:00 +03:00
2018-10-26 16:28:59 +03:00
%if ( 0%{?rhel} && 0%{?rhel} > 7 )
%global _without_bd --without-bd
%endif
2018-01-18 23:24:00 +03:00
# cmocka
2015-02-18 16:47:01 +03:00
# if you wish to compile an rpm with cmocka unit testing...
# rpmbuild -ta @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz --with cmocka
%{?_with_cmocka:%global _with_cmocka --enable-cmocka}
2018-01-18 23:24:00 +03:00
# debug
# if you wish to compile an rpm with debugging...
# rpmbuild -ta @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz --with debug
%{?_with_debug:%global _with_debug --enable-debug}
2010-09-22 08:23:45 +04:00
2018-01-18 23:24:00 +03:00
# epoll
2010-08-16 11:26:33 +04:00
# if you wish to compile an rpm without epoll...
2009-07-01 08:13:09 +04:00
# rpmbuild -ta @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz --without epoll
2011-11-10 06:27:25 +04:00
%{?_without_epoll:%global _without_epoll --disable-epoll}
2009-02-18 15:06:07 +03:00
2018-01-18 23:24:00 +03:00
# fusermount
2013-04-04 00:38:00 +04:00
# if you wish to compile an rpm without fusermount...
# rpmbuild -ta @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz --without fusermount
%{?_without_fusermount:%global _without_fusermount --disable-fusermount}
2011-11-10 06:27:25 +04:00
2018-01-18 23:24:00 +03:00
# geo-rep
2011-04-15 09:08:47 +04:00
# if you wish to compile an rpm without geo-replication support, compile like this...
2011-09-20 11:36:11 +04:00
# rpmbuild -ta @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz --without georeplication
2014-03-07 22:01:05 +04:00
%{?_without_georeplication:%global _without_georeplication --disable-georeplication}
2018-01-18 23:24:00 +03:00
# gnfs
2017-03-27 23:09:56 +03:00
# if you wish to compile an rpm with the legacy gNFS server xlator
# rpmbuild -ta @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz --with gnfs
%{?_with_gnfs:%global _with_gnfs --enable-gnfs}
2018-01-18 23:24:00 +03:00
# ipv6default
# if you wish to compile an rpm with IPv6 default...
# rpmbuild -ta @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz --with ipv6default
%{?_with_ipv6default:%global _with_ipv6default --with-ipv6-default}
# libtirpc
# if you wish to compile an rpm without TIRPC (i.e. use legacy glibc rpc)
# rpmbuild -ta @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz --without libtirpc
%{?_without_libtirpc:%global _without_libtirpc --without-libtirpc}
2018-01-24 13:41:39 +03:00
# Do not use libtirpc on EL6, it does not have xdr_uint64_t() and xdr_uint32_t
# Do not use libtirpc on EL7, it does not have xdr_sizeof()
%if ( 0%{?rhel} && 0%{?rhel} <= 7 )
%global _without_libtirpc --without-libtirpc
%endif
2018-01-18 23:24:00 +03:00
# ocf
2012-11-06 13:13:07 +04:00
# if you wish to compile an rpm without the OCF resource agents...
# rpmbuild -ta @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz --without ocf
%{?_without_ocf:%global _without_ocf --without-ocf}
2018-01-18 23:24:00 +03:00
# rdma
# if you wish to compile an rpm without rdma support, compile like this...
# rpmbuild -ta @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz --without rdma
%{?_without_rdma:%global _without_rdma --disable-ibverbs}
2019-03-08 18:17:14 +03:00
# No RDMA Support on 32-bit ARM
%ifarch armv7hl
2018-01-18 23:24:00 +03:00
%global _without_rdma --disable-ibverbs
%endif
2018-01-31 18:38:34 +03:00
# server
# if you wish to build rpms without server components, compile like this
# rpmbuild -ta @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz --without server
%{?_without_server:%global _without_server --without-server}
# disable server components forcefully as rhel <= 6
%if ( 0%{?rhel} && 0%{?rhel} <= 6 )
%global _without_server --without-server
%endif
2018-01-18 23:24:00 +03:00
# syslog
log: enhance syslog logging using CEE format
This patch enables to use syslog as log target in addition to the
default. The logs are sent in CEE format (http://cee.mitre.org/).
This logging can be disabled using compile time option by
./configure --disable-syslog
(or)
rpmbuild glusterfs.tar.gz --without syslog
The framework provides two api
void gf_openlog (const char *ident, int option, int facility);
void gf_syslog (int error_code, int facility_priority, char *format, ...);
consumers need to call gf_openlog() prior to gf_syslog() like the way
traditional syslog function calls. error_code is mandatory when using
gf_syslog(). For example,
gf_openlog (NULL, -1, -1);
gf_syslog (GF_ERR_DEV, LOG_ERR, "error reading configuration file");
Using syslog, admin is free to configure logger to
* reduce repeated log messages
* forward logs to remote logger
* execute a command on certain log pattern
* alert people for certain log pattern by email, snmp etc
* and many more
Change-Id: Ibacbcbbc547192893fc4a46b387496b622e4811f
BUG: 928648
Signed-off-by: Bala.FA <barumuga@redhat.com>
Reviewed-on: http://review.gluster.org/4915
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
2013-04-30 16:09:30 +04:00
# if you wish to build rpms without syslog logging, compile like this
2014-04-25 18:14:14 +04:00
# rpmbuild -ta @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz --without syslog
log: enhance syslog logging using CEE format
This patch enables to use syslog as log target in addition to the
default. The logs are sent in CEE format (http://cee.mitre.org/).
This logging can be disabled using compile time option by
./configure --disable-syslog
(or)
rpmbuild glusterfs.tar.gz --without syslog
The framework provides two api
void gf_openlog (const char *ident, int option, int facility);
void gf_syslog (int error_code, int facility_priority, char *format, ...);
consumers need to call gf_openlog() prior to gf_syslog() like the way
traditional syslog function calls. error_code is mandatory when using
gf_syslog(). For example,
gf_openlog (NULL, -1, -1);
gf_syslog (GF_ERR_DEV, LOG_ERR, "error reading configuration file");
Using syslog, admin is free to configure logger to
* reduce repeated log messages
* forward logs to remote logger
* execute a command on certain log pattern
* alert people for certain log pattern by email, snmp etc
* and many more
Change-Id: Ibacbcbbc547192893fc4a46b387496b622e4811f
BUG: 928648
Signed-off-by: Bala.FA <barumuga@redhat.com>
Reviewed-on: http://review.gluster.org/4915
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
2013-04-30 16:09:30 +04:00
%{?_without_syslog:%global _without_syslog --disable-syslog}
2013-10-18 09:36:59 +04:00
# disable syslog forcefully as rhel <= 6 doesn't have rsyslog or rsyslog-mmcount
packaging: rpm scriptlet cleanup, handle -p /sbin/ldconfig
The RPM documention indicates that during an rpm install or erase, the
script(lets): %post, %preun, and %postun (and %pre, %build, %install,
etc.) are copied to a temp file, and then the temp file is run as a
(/bin/sh or bash) script.
Unfortunately the documentation is not clear about how rpmbuild and/or
rpm determine where the end of any scriptlet is when it is copied to
the file.
Most things in the glusterfs.spec work correctly as is. These are the
%preun, %post, and %postun scriptlets that are "closed" by a following
%preun, %post, and %postun, or poetentially another scriptlet, e.g.
%file.
The ones that don't work correctly (only one actually) are those where
there is a comment in the spec file before it is closed by another
scriptlet. Further complicating things is that the type of scriptlet
affects what rpm does and what `rpm -qp --scripts ...` shows.
The specific one that didn't work was the "%postun libs" scriptlet. It
is followed by a comment before being "closed" by the %files section (or
scriptlet). It can be written two ways: "%postun libs\n/sbin/ldconfig"
or "%postun libs -p /sbin/ldconfig" Either way it's written, `rpm -qp
--scripts glusterfs-libs...` will include the comment lines between the
%postun libs line and the following %files line.
But the way rpm executes these depends on how they're written. If
written as "%postun libs\n/sbin/ldconfig" rpm will simply run
/sbin/ldconfig with no command line options, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig" ], [ ]);
But when written as "%postun libs -p /sbin/ldconfig", it will copy
the comment lines to a temp file, and pass the temp file name and "1"
as (command line) parameters, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig", "/tmp/tmpXXXXXX", "1" ],
[ ]);
Which results in ldconfig exiting with an error. (Remember, both ways show
the comment in `rpm -qp --scripts ...`)
(Note though, that the similar "%postun api -p /sbin/ldconfig" is run
correctly, because it is "closed" by the following "%postun server"
scriptlet.)
Finally, through trial and error, it appears that rpm can be tricked with
a hack, and "closure" of the scriptlet forcedlike this:
%postun libs -p /sbin/ldconfig
%if ( 0%{?_undocumented_hack_closes_scriptlets} )
%postun
%endif
in which case ldconfig appears to run correctly. Note also that here too
the comment will be included in the output of `rpm -qp --scripts ...`
But that's very ugly hack.
Change-Id: I587a490ddcdf47d01605479bc8ef8b0e439108fb
BUG: 1315024
Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
Reviewed-on: http://review.gluster.org/13613
Smoke: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
2016-03-06 00:06:18 +03:00
# Fedora deprecated syslog, see
2014-05-01 16:23:52 +04:00
# https://fedoraproject.org/wiki/Changes/NoDefaultSyslog
# (And what about RHEL7?)
%if ( 0%{?fedora} && 0%{?fedora} >= 20 ) || ( 0%{?rhel} && 0%{?rhel} <= 6 )
2013-08-09 15:51:56 +04:00
%global _without_syslog --disable-syslog
%endif
2018-11-13 14:53:17 +03:00
# tsan
# if you wish to compile an rpm with thread sanitizer...
# rpmbuild -ta @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz --with tsan
%{?_with_tsan:%global _with_tsan --enable-tsan}
%if ( 0%{?rhel} && 0%{?rhel} < 7 )
%global _with_tsan %{nil}
%endif
2018-01-18 23:24:00 +03:00
# valgrind
# if you wish to compile an rpm to run all processes under valgrind...
# rpmbuild -ta @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz --with valgrind
%{?_with_valgrind:%global _with_valgrind --enable-valgrind}
2014-02-28 09:40:51 +04:00
##-----------------------------------------------------------------------------
packaging: rpm scriptlet cleanup, handle -p /sbin/ldconfig
The RPM documention indicates that during an rpm install or erase, the
script(lets): %post, %preun, and %postun (and %pre, %build, %install,
etc.) are copied to a temp file, and then the temp file is run as a
(/bin/sh or bash) script.
Unfortunately the documentation is not clear about how rpmbuild and/or
rpm determine where the end of any scriptlet is when it is copied to
the file.
Most things in the glusterfs.spec work correctly as is. These are the
%preun, %post, and %postun scriptlets that are "closed" by a following
%preun, %post, and %postun, or poetentially another scriptlet, e.g.
%file.
The ones that don't work correctly (only one actually) are those where
there is a comment in the spec file before it is closed by another
scriptlet. Further complicating things is that the type of scriptlet
affects what rpm does and what `rpm -qp --scripts ...` shows.
The specific one that didn't work was the "%postun libs" scriptlet. It
is followed by a comment before being "closed" by the %files section (or
scriptlet). It can be written two ways: "%postun libs\n/sbin/ldconfig"
or "%postun libs -p /sbin/ldconfig" Either way it's written, `rpm -qp
--scripts glusterfs-libs...` will include the comment lines between the
%postun libs line and the following %files line.
But the way rpm executes these depends on how they're written. If
written as "%postun libs\n/sbin/ldconfig" rpm will simply run
/sbin/ldconfig with no command line options, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig" ], [ ]);
But when written as "%postun libs -p /sbin/ldconfig", it will copy
the comment lines to a temp file, and pass the temp file name and "1"
as (command line) parameters, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig", "/tmp/tmpXXXXXX", "1" ],
[ ]);
Which results in ldconfig exiting with an error. (Remember, both ways show
the comment in `rpm -qp --scripts ...`)
(Note though, that the similar "%postun api -p /sbin/ldconfig" is run
correctly, because it is "closed" by the following "%postun server"
scriptlet.)
Finally, through trial and error, it appears that rpm can be tricked with
a hack, and "closure" of the scriptlet forcedlike this:
%postun libs -p /sbin/ldconfig
%if ( 0%{?_undocumented_hack_closes_scriptlets} )
%postun
%endif
in which case ldconfig appears to run correctly. Note also that here too
the comment will be included in the output of `rpm -qp --scripts ...`
But that's very ugly hack.
Change-Id: I587a490ddcdf47d01605479bc8ef8b0e439108fb
BUG: 1315024
Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
Reviewed-on: http://review.gluster.org/13613
Smoke: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
2016-03-06 00:06:18 +03:00
## All %%global definitions should be placed here and keep them sorted
2014-02-28 09:40:51 +04:00
##
2018-10-05 20:28:03 +03:00
%if ( 0%{?fedora} ) || ( 0%{?rhel} && 0%{?rhel} > 6 )
2014-02-28 09:40:51 +04:00
%global _with_systemd true
2013-01-30 20:29:54 +04:00
%endif
2015-08-21 22:39:53 +03:00
%if ( 0%{?fedora} ) || ( 0%{?rhel} && 0%{?rhel} >= 7 )
%global _with_firewalld --enable-firewalld
%endif
2015-01-16 15:48:49 +03:00
%if 0%{?_tmpfilesdir:1}
2015-12-25 16:11:54 +03:00
%global _with_tmpfilesdir --with-tmpfilesdir=%{_tmpfilesdir}
2015-01-16 15:48:49 +03:00
%else
2015-12-25 16:11:54 +03:00
%global _with_tmpfilesdir --without-tmpfilesdir
2015-01-16 15:48:49 +03:00
%endif
2018-01-31 18:38:34 +03:00
# without server should also disable some server-only components
%if 0%{?_without_server:1}
%global _without_events --disable-events
%global _without_georeplication --disable-georeplication
%global _with_gnfs %{nil}
2018-07-29 13:28:43 +03:00
%global _without_ocf --without-ocf
2018-01-31 18:38:34 +03:00
%endif
2018-10-05 20:28:03 +03:00
%if ( 0%{?fedora} ) || ( 0%{?rhel} && 0%{?rhel} > 7 )
core: python3
see https://review.gluster.org/#/c/19788/,
https://review.gluster.org/#/c/19871/,
https://review.gluster.org/#/c/19952/,
https://review.gluster.org/#/c/20104/,
https://review.gluster.org/#/c/20162/,
https://review.gluster.org/#/c/20185/,
https://review.gluster.org/#/c/20207/,
https://review.gluster.org/#/c/20227/,
https://review.gluster.org/#/c/20307/,
https://review.gluster.org/#/c/20320/,
https://review.gluster.org/#/c/20332/,
https://review.gluster.org/#/c/20364/,
https://review.gluster.org/#/c/20441/, and
https://review.gluster.org/#/c/20484
shebangs changed from /usr/bin/python2 to /usr/bin/python3.
(Reminder, various distribution packaging guidelines require use
of explicit python version and don't allow '#!/usr/bin/env python',
regardless of how handy that idiom may be.)
glusterfs.spec(.in) package python{2,3}-gluster and python2 or
python3 dependencies as appropriate.
configure(.ac):
+ test for and use python2 or python3 as appropriate. If build
machine has python2 and python3, use python3. Override by
setting PYTHON=/usr/bin/python2 when running configure.
+ PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
better match to the original python sysconfig.get_python_inc().
All those other extraneous flags breaks the build.
+ Only change the shebangs once. Changing them over and over
again, e.g., during a `make glusterrpms` in extras/LinuxRPM
just sends make (is it really make that's looping?) into an
infinite loop. If you figure out why, let me know.
+ Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
Everything else has 2.7 or 3.x
+ logic from https://review.gluster.org/c/glusterfs/+/21050, which
needs to be removed/merged after that patch is merged.
Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
mysterious RHEL > 7.
Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
updates: #411
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
2018-08-29 18:09:27 +03:00
%global _usepython3 1
%global _pythonver 3
%else
%global _usepython3 0
%global _pythonver 2
%endif
2013-09-30 11:05:14 +04:00
# From https://fedoraproject.org/wiki/Packaging:Python#Macros
2017-03-27 23:09:56 +03:00
%if ( 0%{?rhel} && 0%{?rhel} <= 6 )
2017-01-18 20:51:19 +03:00
%{!?python2_sitelib: %global python2_sitelib %(python2 -c " f r o m d i s t u t i l s . s y s c o n f i g i m p o r t g e t _ p y t h o n _ l i b ; p r i n t ( g e t _ p y t h o n _ l i b ( ) ) " )}
%{!?python2_sitearch: %global python2_sitearch %(python2 -c " f r o m d i s t u t i l s . s y s c o n f i g i m p o r t g e t _ p y t h o n _ l i b ; p r i n t ( g e t _ p y t h o n _ l i b ( 1 ) ) " )}
2017-08-23 18:37:40 +03:00
%global _rundir %{_localstatedir} /run
2013-09-30 11:05:14 +04:00
%endif
2014-02-28 09:40:51 +04:00
%if ( 0%{?_with_systemd:1} )
2017-10-04 21:22:05 +03:00
%global service_start() /bin/systemctl --quiet start %1.service || : \
%{nil}
%global service_stop() /bin/systemctl --quiet stop %1.service || :\
%{nil}
%global service_install() install -D -p -m 0644 %1.service %{buildroot} %2 \
%{nil}
2014-02-28 09:40:51 +04:00
# can't seem to make a generic macro that works
2017-10-04 21:22:05 +03:00
%global glusterd_svcfile %{_unitdir} /glusterd.service
%global glusterfsd_svcfile %{_unitdir} /glusterfsd.service
2019-01-30 11:54:14 +03:00
%global glusterta_svcfile %{_unitdir} /gluster-ta-volume.service
2017-10-04 21:22:05 +03:00
%global glustereventsd_svcfile %{_unitdir} /glustereventsd.service
%global glusterfssharedstorage_svcfile %{_unitdir} /glusterfssharedstorage.service
2014-02-28 09:40:51 +04:00
%else
2017-10-04 21:22:05 +03:00
%global systemd_post() /sbin/chkconfig --add %1 >/dev/null 2>&1 || : \
%{nil}
%global systemd_preun() /sbin/chkconfig --del %1 >/dev/null 2>&1 || : \
%{nil}
%global systemd_postun_with_restart() /sbin/service %1 condrestart >/dev/null 2>&1 || : \
%{nil}
%global service_start() /sbin/service %1 start >/dev/null 2>&1 || : \
%{nil}
%global service_stop() /sbin/service %1 stop >/dev/null 2>&1 || : \
%{nil}
%global service_install() install -D -p -m 0755 %1.init %{buildroot} %2 \
%{nil}
2014-02-28 09:40:51 +04:00
# can't seem to make a generic macro that works
2017-10-04 21:22:05 +03:00
%global glusterd_svcfile %{_sysconfdir} /init.d/glusterd
%global glusterfsd_svcfile %{_sysconfdir} /init.d/glusterfsd
%global glustereventsd_svcfile %{_sysconfdir} /init.d/glustereventsd
2014-02-28 09:40:51 +04:00
%endif
%{!?_pkgdocdir: %global _pkgdocdir %{_docdir} /%{name} -%{version} }
# We do not want to generate useless provides and requires for xlator
# .so files to be set for glusterfs packages.
# Filter all generated:
#
# TODO: RHEL5 does not have a convenient solution
%if ( 0%{?rhel} == 6 )
2015-12-25 16:11:54 +03:00
# filter_setup exists in RHEL6 only
%filter_provides_in %{_libdir} /glusterfs/%{version} /
%global __filter_from_req %{?__filter_from_req} | grep -v -P '^(?!lib).*\.so.*$'
%filter_setup
2014-02-28 09:40:51 +04:00
%else
2015-12-25 16:11:54 +03:00
# modern rpm and current Fedora do not generate requires when the
# provides are filtered
%global __provides_exclude_from ^%{_libdir} /glusterfs/%{version} /.*$
2014-02-28 09:40:51 +04:00
%endif
##-----------------------------------------------------------------------------
2016-04-12 18:35:38 +03:00
## All package definitions should be placed here in alphabetical order
2014-02-28 09:40:51 +04:00
##
2014-09-25 09:58:21 +04:00
Summary : Distributed File System
2013-06-17 21:44:10 +04:00
%if ( 0%{_for_fedora_koji_builds} )
2013-01-30 20:29:54 +04:00
Name : glusterfs
2016-04-12 18:35:38 +03:00
Version : 3.8.0
2013-12-10 16:26:46 +04:00
Release : 0.1%{?prereltag:.%{prereltag} }%{?dist}
2013-01-30 20:29:54 +04:00
%else
Name : @PACKAGE_NAME@
Version : @PACKAGE_VERSION@
2014-02-27 11:09:43 +04:00
Release : 0.@PACKAGE_RELEASE@%{?dist}
2013-01-30 20:29:54 +04:00
%endif
2013-06-17 21:44:10 +04:00
License : GPLv2 or LGPLv3+
2017-09-01 16:09:06 +03:00
URL : http://docs.gluster.org/
2013-06-17 21:44:10 +04:00
%if ( 0%{_for_fedora_koji_builds} )
2014-04-25 18:14:14 +04:00
Source0 : http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-%{version} %{?prereltag} .tar.gz
2013-01-30 20:29:54 +04:00
Source1 : glusterd.sysconfig
Source2 : glusterfsd.sysconfig
2014-02-28 09:40:51 +04:00
Source7 : glusterfsd.service
Source8 : glusterfsd.init
2013-06-17 21:44:10 +04:00
%else
Source0 : @PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz
%endif
2013-01-30 20:29:54 +04:00
BuildRoot : %(mktemp -ud %{_tmppath} /%{name} -%{version} -%{release} -XXXXXX)
2017-04-26 15:11:56 +03:00
Requires(pre) : shadow-utils
2013-06-17 21:44:10 +04:00
%if ( 0%{?_with_systemd:1} )
2016-11-30 17:08:03 +03:00
BuildRequires : systemd
2013-01-30 20:29:54 +04:00
%endif
2009-04-16 17:15:48 +04:00
2016-01-08 18:43:15 +03:00
Requires : %{name} -libs%{?_isa} = %{version} -%{release}
2016-11-30 17:08:03 +03:00
%if ( 0%{?_with_systemd:1} )
%{?systemd_requires}
%endif
2018-08-10 02:32:22 +03:00
%if 0%{?_with_asan:1} && !( 0%{?rhel} && 0%{?rhel} < 7 )
BuildRequires : libasan
%endif
2018-11-13 14:53:17 +03:00
%if 0%{?_with_tsan:1} && !( 0%{?rhel} && 0%{?rhel} < 7 )
BuildRequires : libtsan
%endif
2013-01-30 20:29:54 +04:00
BuildRequires : bison flex
2016-05-23 12:06:38 +03:00
BuildRequires : gcc make libtool
2013-01-30 20:29:54 +04:00
BuildRequires : ncurses-devel readline-devel
BuildRequires : libxml2-devel openssl-devel
2015-02-10 21:13:35 +03:00
BuildRequires : libaio-devel libacl-devel
core: python3
see https://review.gluster.org/#/c/19788/,
https://review.gluster.org/#/c/19871/,
https://review.gluster.org/#/c/19952/,
https://review.gluster.org/#/c/20104/,
https://review.gluster.org/#/c/20162/,
https://review.gluster.org/#/c/20185/,
https://review.gluster.org/#/c/20207/,
https://review.gluster.org/#/c/20227/,
https://review.gluster.org/#/c/20307/,
https://review.gluster.org/#/c/20320/,
https://review.gluster.org/#/c/20332/,
https://review.gluster.org/#/c/20364/,
https://review.gluster.org/#/c/20441/, and
https://review.gluster.org/#/c/20484
shebangs changed from /usr/bin/python2 to /usr/bin/python3.
(Reminder, various distribution packaging guidelines require use
of explicit python version and don't allow '#!/usr/bin/env python',
regardless of how handy that idiom may be.)
glusterfs.spec(.in) package python{2,3}-gluster and python2 or
python3 dependencies as appropriate.
configure(.ac):
+ test for and use python2 or python3 as appropriate. If build
machine has python2 and python3, use python3. Override by
setting PYTHON=/usr/bin/python2 when running configure.
+ PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
better match to the original python sysconfig.get_python_inc().
All those other extraneous flags breaks the build.
+ Only change the shebangs once. Changing them over and over
again, e.g., during a `make glusterrpms` in extras/LinuxRPM
just sends make (is it really make that's looping?) into an
infinite loop. If you figure out why, let me know.
+ Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
Everything else has 2.7 or 3.x
+ logic from https://review.gluster.org/c/glusterfs/+/21050, which
needs to be removed/merged after that patch is merged.
Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
mysterious RHEL > 7.
Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
updates: #411
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
2018-08-29 18:09:27 +03:00
BuildRequires : python%{_pythonver}-devel
%if ( 0%{?rhel} && 0%{?rhel} < 8 )
2013-01-30 20:29:54 +04:00
BuildRequires : python-ctypes
2016-09-22 15:22:50 +03:00
%endif
2018-01-24 13:41:39 +03:00
%if ( 0%{?_with_ipv6default:1} ) || ( 0%{!?_without_libtirpc:1} )
2018-01-18 23:24:00 +03:00
BuildRequires : libtirpc-devel
%endif
2018-10-26 16:28:59 +03:00
%if ( 0%{?fedora} && 0%{?fedora} > 27 ) || ( 0%{?rhel} && 0%{?rhel} > 7 )
2018-01-18 23:24:00 +03:00
BuildRequires : rpcgen
2017-04-29 02:44:29 +03:00
%endif
2015-01-06 12:42:59 +03:00
BuildRequires : userspace-rcu-devel >= 0.7
2016-05-23 12:06:38 +03:00
%if ( 0%{?rhel} && 0%{?rhel} <= 6 )
BuildRequires : automake
%endif
2015-04-03 19:14:13 +03:00
BuildRequires : libuuid-devel
2015-03-03 02:27:34 +03:00
%if ( 0%{?_with_cmocka:1} )
BuildRequires : libcmocka-devel >= 1.0.1
2015-02-18 16:47:01 +03:00
%endif
2014-02-06 15:46:20 +04:00
%if ( 0%{!?_without_georeplication:1} )
BuildRequires : libattr-devel
%endif
2009-02-18 15:06:07 +03:00
2015-08-21 22:39:53 +03:00
%if (0%{?_with_firewalld:1})
2017-04-20 16:46:46 +03:00
BuildRequires : firewalld
2015-08-21 22:39:53 +03:00
%endif
2013-12-10 16:26:46 +04:00
Obsoletes : hekafs
2011-11-10 06:27:25 +04:00
Obsoletes : %{name} -common < %{version} -%{release}
Obsoletes : %{name} -core < %{version} -%{release}
2013-12-10 16:26:46 +04:00
Obsoletes : %{name} -ufo
2017-02-01 15:50:17 +03:00
Obsoletes : %{name} -ganesha
2019-02-11 08:37:49 +03:00
%if ( 0%{!?_with_gnfs:1} )
Obsoletes : %{name} -gnfs
%endif
2011-11-10 06:27:25 +04:00
Provides : %{name} -common = %{version} -%{release}
Provides : %{name} -core = %{version} -%{release}
2009-02-18 15:06:07 +03:00
2011-11-10 06:27:25 +04:00
%description
2014-09-05 08:12:18 +04:00
GlusterFS is a distributed file-system capable of scaling to several
2013-01-30 20:29:54 +04:00
petabytes. It aggregates various storage bricks over Infiniband RDMA
2009-04-16 17:15:48 +04:00
or TCP/IP interconnect into one large parallel network file
2013-01-30 20:29:54 +04:00
system. GlusterFS is one of the most sophisticated file systems in
2009-04-16 17:15:48 +04:00
terms of features and extensibility. It borrows a powerful concept
called Translators from GNU Hurd kernel. Much of the code in GlusterFS
2013-01-30 20:29:54 +04:00
is in user space and easily manageable.
2009-04-16 17:15:48 +04:00
2013-01-30 20:29:54 +04:00
This package includes the glusterfs binary, the glusterfsd daemon and the
2015-05-05 11:28:15 +03:00
libglusterfs and glusterfs translator modules common to both GlusterFS server
and client framework.
2009-04-16 17:15:48 +04:00
2014-02-28 09:40:51 +04:00
%package api
2015-02-25 17:07:22 +03:00
Summary : GlusterFS api library
2016-01-08 18:43:15 +03:00
Requires : %{name} %{?_isa} = %{version} -%{release}
Requires : %{name} -client-xlators%{?_isa} = %{version} -%{release}
2013-07-30 22:00:46 +04:00
2014-02-28 09:40:51 +04:00
%description api
2014-09-05 08:12:18 +04:00
GlusterFS is a distributed file-system capable of scaling to several
2013-07-30 22:00:46 +04:00
petabytes. It aggregates various storage bricks over Infiniband RDMA
or TCP/IP interconnect into one large parallel network file
system. GlusterFS is one of the most sophisticated file systems in
terms of features and extensibility. It borrows a powerful concept
called Translators from GNU Hurd kernel. Much of the code in GlusterFS
is in user space and easily manageable.
2014-02-28 09:40:51 +04:00
This package provides the glusterfs libgfapi library.
%package api-devel
Summary : Development Libraries
2016-01-08 18:43:15 +03:00
Requires : %{name} %{?_isa} = %{version} -%{release}
Requires : %{name} -devel%{?_isa} = %{version} -%{release}
2015-05-05 15:47:38 +03:00
Requires : libacl-devel
2014-02-28 09:40:51 +04:00
%description api-devel
2014-09-05 08:12:18 +04:00
GlusterFS is a distributed file-system capable of scaling to several
2014-02-28 09:40:51 +04:00
petabytes. It aggregates various storage bricks over Infiniband RDMA
or TCP/IP interconnect into one large parallel network file
system. GlusterFS is one of the most sophisticated file systems in
terms of features and extensibility. It borrows a powerful concept
called Translators from GNU Hurd kernel. Much of the code in GlusterFS
is in user space and easily manageable.
This package provides the api include files.
2013-07-30 22:00:46 +04:00
2018-01-31 18:38:34 +03:00
%if ( 0%{!?_without_server:1} )
2013-08-07 17:11:48 +04:00
%package cli
Summary : GlusterFS CLI
2016-01-08 18:43:15 +03:00
Requires : %{name} -libs%{?_isa} = %{version} -%{release}
2013-08-07 17:11:48 +04:00
%description cli
2014-09-05 08:12:18 +04:00
GlusterFS is a distributed file-system capable of scaling to several
2013-08-07 17:11:48 +04:00
petabytes. It aggregates various storage bricks over Infiniband RDMA
or TCP/IP interconnect into one large parallel network file
system. GlusterFS is one of the most sophisticated file systems in
terms of features and extensibility. It borrows a powerful concept
called Translators from GNU Hurd kernel. Much of the code in GlusterFS
is in user space and easily manageable.
This package provides the GlusterFS CLI application and its man page
2018-01-31 18:38:34 +03:00
%endif
2013-08-07 17:11:48 +04:00
2018-09-10 16:02:33 +03:00
%package cloudsync-plugins
Summary : Cloudsync Plugins
BuildRequires : libcurl-devel
%description cloudsync-plugins
GlusterFS is a distributed file-system capable of scaling to several
petabytes. It aggregates various storage bricks over Infiniband RDMA
or TCP/IP interconnect into one large parallel network file
system. GlusterFS is one of the most sophisticated file systems in
terms of features and extensibility. It borrows a powerful concept
called Translators from GNU Hurd kernel. Much of the code in GlusterFS
is in user space and easily manageable.
This package provides cloudsync plugins for archival feature.
2014-02-28 09:40:51 +04:00
%package devel
Summary : Development Libraries
2016-01-08 18:43:15 +03:00
Requires : %{name} %{?_isa} = %{version} -%{release}
2014-02-28 09:40:51 +04:00
# Needed for the Glupy examples to work
2016-01-08 18:43:15 +03:00
Requires : %{name} -extra-xlators%{?_isa} = %{version} -%{release}
2011-11-10 06:27:25 +04:00
2014-02-28 09:40:51 +04:00
%description devel
2014-09-05 08:12:18 +04:00
GlusterFS is a distributed file-system capable of scaling to several
2013-01-30 20:29:54 +04:00
petabytes. It aggregates various storage bricks over Infiniband RDMA
2009-04-16 17:15:48 +04:00
or TCP/IP interconnect into one large parallel network file
2013-01-30 20:29:54 +04:00
system. GlusterFS is one of the most sophisticated file systems in
2009-04-16 17:15:48 +04:00
terms of features and extensibility. It borrows a powerful concept
called Translators from GNU Hurd kernel. Much of the code in GlusterFS
2013-01-30 20:29:54 +04:00
is in user space and easily manageable.
2009-04-16 17:15:48 +04:00
2014-02-28 09:40:51 +04:00
This package provides the development libraries and include files.
2009-04-16 17:15:48 +04:00
2014-02-28 09:40:51 +04:00
%package extra-xlators
Summary : Extra Gluster filesystem Translators
2015-05-03 16:07:56 +03:00
# We need python-gluster rpm for gluster module's __init__.py in Python
# site-packages area
core: python3
see https://review.gluster.org/#/c/19788/,
https://review.gluster.org/#/c/19871/,
https://review.gluster.org/#/c/19952/,
https://review.gluster.org/#/c/20104/,
https://review.gluster.org/#/c/20162/,
https://review.gluster.org/#/c/20185/,
https://review.gluster.org/#/c/20207/,
https://review.gluster.org/#/c/20227/,
https://review.gluster.org/#/c/20307/,
https://review.gluster.org/#/c/20320/,
https://review.gluster.org/#/c/20332/,
https://review.gluster.org/#/c/20364/,
https://review.gluster.org/#/c/20441/, and
https://review.gluster.org/#/c/20484
shebangs changed from /usr/bin/python2 to /usr/bin/python3.
(Reminder, various distribution packaging guidelines require use
of explicit python version and don't allow '#!/usr/bin/env python',
regardless of how handy that idiom may be.)
glusterfs.spec(.in) package python{2,3}-gluster and python2 or
python3 dependencies as appropriate.
configure(.ac):
+ test for and use python2 or python3 as appropriate. If build
machine has python2 and python3, use python3. Override by
setting PYTHON=/usr/bin/python2 when running configure.
+ PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
better match to the original python sysconfig.get_python_inc().
All those other extraneous flags breaks the build.
+ Only change the shebangs once. Changing them over and over
again, e.g., during a `make glusterrpms` in extras/LinuxRPM
just sends make (is it really make that's looping?) into an
infinite loop. If you figure out why, let me know.
+ Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
Everything else has 2.7 or 3.x
+ logic from https://review.gluster.org/c/glusterfs/+/21050, which
needs to be removed/merged after that patch is merged.
Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
mysterious RHEL > 7.
Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
updates: #411
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
2018-08-29 18:09:27 +03:00
Requires : python%{_pythonver}-gluster = %{version} -%{release}
Requires : python%{_pythonver}
2011-04-15 09:08:47 +04:00
2014-02-28 09:40:51 +04:00
%description extra-xlators
2014-09-05 08:12:18 +04:00
GlusterFS is a distributed file-system capable of scaling to several
2014-02-28 09:40:51 +04:00
petabytes. It aggregates various storage bricks over Infiniband RDMA
2011-04-15 09:08:47 +04:00
or TCP/IP interconnect into one large parallel network file
2014-02-28 09:40:51 +04:00
system. GlusterFS is one of the most sophisticated file systems in
2011-04-15 09:08:47 +04:00
terms of features and extensibility. It borrows a powerful concept
called Translators from GNU Hurd kernel. Much of the code in GlusterFS
2014-02-28 09:40:51 +04:00
is in user space and easily manageable.
2011-04-15 09:08:47 +04:00
2014-02-28 09:40:51 +04:00
This package provides extra filesystem Translators, such as Glupy,
for GlusterFS.
2011-04-15 09:08:47 +04:00
2010-08-16 11:26:33 +04:00
%package fuse
2013-01-30 20:29:54 +04:00
Summary : Fuse client
BuildRequires : fuse-devel
2015-03-26 19:11:55 +03:00
Requires : attr
2016-08-17 10:38:41 +03:00
Requires : psmisc
2011-11-10 06:27:25 +04:00
2016-01-08 18:43:15 +03:00
Requires : %{name} %{?_isa} = %{version} -%{release}
Requires : %{name} -client-xlators%{?_isa} = %{version} -%{release}
2011-11-10 06:27:25 +04:00
Obsoletes : %{name} -client < %{version} -%{release}
Provides : %{name} -client = %{version} -%{release}
2009-02-18 15:06:07 +03:00
2010-08-16 11:26:33 +04:00
%description fuse
2014-09-05 08:12:18 +04:00
GlusterFS is a distributed file-system capable of scaling to several
2013-01-30 20:29:54 +04:00
petabytes. It aggregates various storage bricks over Infiniband RDMA
2009-02-18 15:06:07 +03:00
or TCP/IP interconnect into one large parallel network file
2013-01-30 20:29:54 +04:00
system. GlusterFS is one of the most sophisticated file systems in
2009-02-18 15:06:07 +03:00
terms of features and extensibility. It borrows a powerful concept
called Translators from GNU Hurd kernel. Much of the code in GlusterFS
2013-01-30 20:29:54 +04:00
is in user space and easily manageable.
2009-02-18 15:06:07 +03:00
2015-05-05 11:28:15 +03:00
This package provides support to FUSE based clients and inlcudes the
glusterfs(d) binary.
2009-02-18 15:06:07 +03:00
2014-02-28 09:40:51 +04:00
%if ( 0%{!?_without_georeplication:1} )
%package geo-replication
Summary : GlusterFS Geo-replication
2016-01-08 18:43:15 +03:00
Requires : %{name} %{?_isa} = %{version} -%{release}
Requires : %{name} -server%{?_isa} = %{version} -%{release}
core: python3
see https://review.gluster.org/#/c/19788/,
https://review.gluster.org/#/c/19871/,
https://review.gluster.org/#/c/19952/,
https://review.gluster.org/#/c/20104/,
https://review.gluster.org/#/c/20162/,
https://review.gluster.org/#/c/20185/,
https://review.gluster.org/#/c/20207/,
https://review.gluster.org/#/c/20227/,
https://review.gluster.org/#/c/20307/,
https://review.gluster.org/#/c/20320/,
https://review.gluster.org/#/c/20332/,
https://review.gluster.org/#/c/20364/,
https://review.gluster.org/#/c/20441/, and
https://review.gluster.org/#/c/20484
shebangs changed from /usr/bin/python2 to /usr/bin/python3.
(Reminder, various distribution packaging guidelines require use
of explicit python version and don't allow '#!/usr/bin/env python',
regardless of how handy that idiom may be.)
glusterfs.spec(.in) package python{2,3}-gluster and python2 or
python3 dependencies as appropriate.
configure(.ac):
+ test for and use python2 or python3 as appropriate. If build
machine has python2 and python3, use python3. Override by
setting PYTHON=/usr/bin/python2 when running configure.
+ PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
better match to the original python sysconfig.get_python_inc().
All those other extraneous flags breaks the build.
+ Only change the shebangs once. Changing them over and over
again, e.g., during a `make glusterrpms` in extras/LinuxRPM
just sends make (is it really make that's looping?) into an
infinite loop. If you figure out why, let me know.
+ Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
Everything else has 2.7 or 3.x
+ logic from https://review.gluster.org/c/glusterfs/+/21050, which
needs to be removed/merged after that patch is merged.
Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
mysterious RHEL > 7.
Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
updates: #411
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
2018-08-29 18:09:27 +03:00
Requires : python%{_pythonver}
Requires : python%{_pythonver}-prettytable
Requires : python%{_pythonver}-gluster = %{version} -%{release}
2015-06-12 14:49:55 +03:00
Requires : rsync
2018-02-12 11:11:04 +03:00
Requires : util-linux
2011-11-10 06:27:25 +04:00
2014-02-28 09:40:51 +04:00
%description geo-replication
2014-09-05 08:12:18 +04:00
GlusterFS is a distributed file-system capable of scaling to several
2014-02-28 09:40:51 +04:00
peta-bytes. It aggregates various storage bricks over Infiniband RDMA
2011-11-10 06:27:25 +04:00
or TCP/IP interconnect into one large parallel network file
2014-02-28 09:40:51 +04:00
system. GlusterFS is one of the most sophisticated file system in
2011-11-10 06:27:25 +04:00
terms of features and extensibility. It borrows a powerful concept
called Translators from GNU Hurd kernel. Much of the code in GlusterFS
2014-02-28 09:40:51 +04:00
is in userspace and easily manageable.
2011-11-10 06:27:25 +04:00
2014-02-28 09:40:51 +04:00
This package provides support to geo-replication.
%endif
2011-11-10 06:27:25 +04:00
2017-03-27 23:09:56 +03:00
%if ( 0%{?_with_gnfs:1} )
%package gnfs
Summary : GlusterFS gNFS server
Requires : %{name} %{?_isa} = %{version} -%{release}
Requires : %{name} -client-xlators%{?_isa} = %{version} -%{release}
Requires : nfs-utils
%description gnfs
GlusterFS is a distributed file-system capable of scaling to several
petabytes. It aggregates various storage bricks over Infiniband RDMA
or TCP/IP interconnect into one large parallel network file
system. GlusterFS is one of the most sophisticated file systems in
terms of features and extensibility. It borrows a powerful concept
called Translators from GNU Hurd kernel. Much of the code in GlusterFS
is in user space and easily manageable.
This package provides the glusterfs legacy gNFS server xlator
%endif
2014-02-28 09:40:51 +04:00
%package libs
Summary : GlusterFS common libraries
2013-06-17 21:44:10 +04:00
2014-02-28 09:40:51 +04:00
%description libs
2014-09-05 08:12:18 +04:00
GlusterFS is a distributed file-system capable of scaling to several
2013-06-17 21:44:10 +04:00
petabytes. It aggregates various storage bricks over Infiniband RDMA
or TCP/IP interconnect into one large parallel network file
system. GlusterFS is one of the most sophisticated file systems in
terms of features and extensibility. It borrows a powerful concept
called Translators from GNU Hurd kernel. Much of the code in GlusterFS
is in user space and easily manageable.
2014-02-28 09:40:51 +04:00
This package provides the base GlusterFS libraries
2013-06-17 21:44:10 +04:00
core: python3
see https://review.gluster.org/#/c/19788/,
https://review.gluster.org/#/c/19871/,
https://review.gluster.org/#/c/19952/,
https://review.gluster.org/#/c/20104/,
https://review.gluster.org/#/c/20162/,
https://review.gluster.org/#/c/20185/,
https://review.gluster.org/#/c/20207/,
https://review.gluster.org/#/c/20227/,
https://review.gluster.org/#/c/20307/,
https://review.gluster.org/#/c/20320/,
https://review.gluster.org/#/c/20332/,
https://review.gluster.org/#/c/20364/,
https://review.gluster.org/#/c/20441/, and
https://review.gluster.org/#/c/20484
shebangs changed from /usr/bin/python2 to /usr/bin/python3.
(Reminder, various distribution packaging guidelines require use
of explicit python version and don't allow '#!/usr/bin/env python',
regardless of how handy that idiom may be.)
glusterfs.spec(.in) package python{2,3}-gluster and python2 or
python3 dependencies as appropriate.
configure(.ac):
+ test for and use python2 or python3 as appropriate. If build
machine has python2 and python3, use python3. Override by
setting PYTHON=/usr/bin/python2 when running configure.
+ PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
better match to the original python sysconfig.get_python_inc().
All those other extraneous flags breaks the build.
+ Only change the shebangs once. Changing them over and over
again, e.g., during a `make glusterrpms` in extras/LinuxRPM
just sends make (is it really make that's looping?) into an
infinite loop. If you figure out why, let me know.
+ Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
Everything else has 2.7 or 3.x
+ logic from https://review.gluster.org/c/glusterfs/+/21050, which
needs to be removed/merged after that patch is merged.
Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
mysterious RHEL > 7.
Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
updates: #411
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
2018-08-29 18:09:27 +03:00
%package -n python%{_pythonver}-gluster
2017-01-18 20:51:19 +03:00
Summary : GlusterFS python library
core: python3
see https://review.gluster.org/#/c/19788/,
https://review.gluster.org/#/c/19871/,
https://review.gluster.org/#/c/19952/,
https://review.gluster.org/#/c/20104/,
https://review.gluster.org/#/c/20162/,
https://review.gluster.org/#/c/20185/,
https://review.gluster.org/#/c/20207/,
https://review.gluster.org/#/c/20227/,
https://review.gluster.org/#/c/20307/,
https://review.gluster.org/#/c/20320/,
https://review.gluster.org/#/c/20332/,
https://review.gluster.org/#/c/20364/,
https://review.gluster.org/#/c/20441/, and
https://review.gluster.org/#/c/20484
shebangs changed from /usr/bin/python2 to /usr/bin/python3.
(Reminder, various distribution packaging guidelines require use
of explicit python version and don't allow '#!/usr/bin/env python',
regardless of how handy that idiom may be.)
glusterfs.spec(.in) package python{2,3}-gluster and python2 or
python3 dependencies as appropriate.
configure(.ac):
+ test for and use python2 or python3 as appropriate. If build
machine has python2 and python3, use python3. Override by
setting PYTHON=/usr/bin/python2 when running configure.
+ PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
better match to the original python sysconfig.get_python_inc().
All those other extraneous flags breaks the build.
+ Only change the shebangs once. Changing them over and over
again, e.g., during a `make glusterrpms` in extras/LinuxRPM
just sends make (is it really make that's looping?) into an
infinite loop. If you figure out why, let me know.
+ Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
Everything else has 2.7 or 3.x
+ logic from https://review.gluster.org/c/glusterfs/+/21050, which
needs to be removed/merged after that patch is merged.
Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
mysterious RHEL > 7.
Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
updates: #411
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
2018-08-29 18:09:27 +03:00
Requires : python%{_pythonver}
%if ( ! %{_usepython3} )
%{?python_provide:%python_provide python-gluster}
2017-02-16 22:32:36 +03:00
Provides : python-gluster = %{version} -%{release}
Obsoletes : python-gluster < 3.10
core: python3
see https://review.gluster.org/#/c/19788/,
https://review.gluster.org/#/c/19871/,
https://review.gluster.org/#/c/19952/,
https://review.gluster.org/#/c/20104/,
https://review.gluster.org/#/c/20162/,
https://review.gluster.org/#/c/20185/,
https://review.gluster.org/#/c/20207/,
https://review.gluster.org/#/c/20227/,
https://review.gluster.org/#/c/20307/,
https://review.gluster.org/#/c/20320/,
https://review.gluster.org/#/c/20332/,
https://review.gluster.org/#/c/20364/,
https://review.gluster.org/#/c/20441/, and
https://review.gluster.org/#/c/20484
shebangs changed from /usr/bin/python2 to /usr/bin/python3.
(Reminder, various distribution packaging guidelines require use
of explicit python version and don't allow '#!/usr/bin/env python',
regardless of how handy that idiom may be.)
glusterfs.spec(.in) package python{2,3}-gluster and python2 or
python3 dependencies as appropriate.
configure(.ac):
+ test for and use python2 or python3 as appropriate. If build
machine has python2 and python3, use python3. Override by
setting PYTHON=/usr/bin/python2 when running configure.
+ PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
better match to the original python sysconfig.get_python_inc().
All those other extraneous flags breaks the build.
+ Only change the shebangs once. Changing them over and over
again, e.g., during a `make glusterrpms` in extras/LinuxRPM
just sends make (is it really make that's looping?) into an
infinite loop. If you figure out why, let me know.
+ Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
Everything else has 2.7 or 3.x
+ logic from https://review.gluster.org/c/glusterfs/+/21050, which
needs to be removed/merged after that patch is merged.
Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
mysterious RHEL > 7.
Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
updates: #411
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
2018-08-29 18:09:27 +03:00
%endif
2017-01-18 20:51:19 +03:00
core: python3
see https://review.gluster.org/#/c/19788/,
https://review.gluster.org/#/c/19871/,
https://review.gluster.org/#/c/19952/,
https://review.gluster.org/#/c/20104/,
https://review.gluster.org/#/c/20162/,
https://review.gluster.org/#/c/20185/,
https://review.gluster.org/#/c/20207/,
https://review.gluster.org/#/c/20227/,
https://review.gluster.org/#/c/20307/,
https://review.gluster.org/#/c/20320/,
https://review.gluster.org/#/c/20332/,
https://review.gluster.org/#/c/20364/,
https://review.gluster.org/#/c/20441/, and
https://review.gluster.org/#/c/20484
shebangs changed from /usr/bin/python2 to /usr/bin/python3.
(Reminder, various distribution packaging guidelines require use
of explicit python version and don't allow '#!/usr/bin/env python',
regardless of how handy that idiom may be.)
glusterfs.spec(.in) package python{2,3}-gluster and python2 or
python3 dependencies as appropriate.
configure(.ac):
+ test for and use python2 or python3 as appropriate. If build
machine has python2 and python3, use python3. Override by
setting PYTHON=/usr/bin/python2 when running configure.
+ PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
better match to the original python sysconfig.get_python_inc().
All those other extraneous flags breaks the build.
+ Only change the shebangs once. Changing them over and over
again, e.g., during a `make glusterrpms` in extras/LinuxRPM
just sends make (is it really make that's looping?) into an
infinite loop. If you figure out why, let me know.
+ Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
Everything else has 2.7 or 3.x
+ logic from https://review.gluster.org/c/glusterfs/+/21050, which
needs to be removed/merged after that patch is merged.
Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
mysterious RHEL > 7.
Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
updates: #411
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
2018-08-29 18:09:27 +03:00
%description -n python%{_pythonver}-gluster
GlusterFS is a distributed file-system capable of scaling to several
petabytes. It aggregates various storage bricks over Infiniband RDMA
or TCP/IP interconnect into one large parallel network file
system. GlusterFS is one of the most sophisticated file systems in
terms of features and extensibility. It borrows a powerful concept
called Translators from GNU Hurd kernel. Much of the code in GlusterFS
is in user space and easily manageable.
This package contains the python modules of GlusterFS and own gluster
namespace.
2015-04-15 09:59:16 +03:00
2014-02-28 09:40:51 +04:00
%if ( 0%{!?_without_rdma:1} )
%package rdma
Summary : GlusterFS rdma support for ib-verbs
2017-08-22 17:21:48 +03:00
%if ( 0%{?fedora} && 0%{?fedora} > 26 )
BuildRequires : rdma-core-devel
%else
2014-02-28 09:40:51 +04:00
BuildRequires : libibverbs-devel
2015-03-27 21:13:05 +03:00
BuildRequires : librdmacm-devel >= 1.0.15
2017-08-22 17:21:48 +03:00
%endif
2016-01-08 18:43:15 +03:00
Requires : %{name} %{?_isa} = %{version} -%{release}
2014-03-22 00:13:16 +04:00
2014-02-28 09:40:51 +04:00
%description rdma
2014-09-05 08:12:18 +04:00
GlusterFS is a distributed file-system capable of scaling to several
2014-03-22 00:13:16 +04:00
petabytes. It aggregates various storage bricks over Infiniband RDMA
or TCP/IP interconnect into one large parallel network file
system. GlusterFS is one of the most sophisticated file systems in
terms of features and extensibility. It borrows a powerful concept
called Translators from GNU Hurd kernel. Much of the code in GlusterFS
is in user space and easily manageable.
2014-02-28 09:40:51 +04:00
This package provides support to ib-verbs library.
%endif
%package regression-tests
Summary : Development Tools
2016-01-08 18:43:15 +03:00
Requires : %{name} %{?_isa} = %{version} -%{release}
Requires : %{name} -fuse%{?_isa} = %{version} -%{release}
Requires : %{name} -server%{?_isa} = %{version} -%{release}
2014-06-25 02:00:59 +04:00
## thin provisioning support
Requires : lvm2 >= 2.02.89
Requires : perl(App::Prove) perl(Test::Harness) gcc util-linux-ng
core: python3
see https://review.gluster.org/#/c/19788/,
https://review.gluster.org/#/c/19871/,
https://review.gluster.org/#/c/19952/,
https://review.gluster.org/#/c/20104/,
https://review.gluster.org/#/c/20162/,
https://review.gluster.org/#/c/20185/,
https://review.gluster.org/#/c/20207/,
https://review.gluster.org/#/c/20227/,
https://review.gluster.org/#/c/20307/,
https://review.gluster.org/#/c/20320/,
https://review.gluster.org/#/c/20332/,
https://review.gluster.org/#/c/20364/,
https://review.gluster.org/#/c/20441/, and
https://review.gluster.org/#/c/20484
shebangs changed from /usr/bin/python2 to /usr/bin/python3.
(Reminder, various distribution packaging guidelines require use
of explicit python version and don't allow '#!/usr/bin/env python',
regardless of how handy that idiom may be.)
glusterfs.spec(.in) package python{2,3}-gluster and python2 or
python3 dependencies as appropriate.
configure(.ac):
+ test for and use python2 or python3 as appropriate. If build
machine has python2 and python3, use python3. Override by
setting PYTHON=/usr/bin/python2 when running configure.
+ PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
better match to the original python sysconfig.get_python_inc().
All those other extraneous flags breaks the build.
+ Only change the shebangs once. Changing them over and over
again, e.g., during a `make glusterrpms` in extras/LinuxRPM
just sends make (is it really make that's looping?) into an
infinite loop. If you figure out why, let me know.
+ Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
Everything else has 2.7 or 3.x
+ logic from https://review.gluster.org/c/glusterfs/+/21050, which
needs to be removed/merged after that patch is merged.
Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
mysterious RHEL > 7.
Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
updates: #411
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
2018-08-29 18:09:27 +03:00
Requires : python%{_pythonver}
Requires : attr dbench file git libacl-devel net-tools
2017-04-13 19:26:29 +03:00
Requires : nfs-utils xfsprogs yajl psmisc bc
2014-02-28 09:40:51 +04:00
%description regression-tests
The Gluster Test Framework, is a suite of scripts used for
regression testing of Gluster.
2014-03-22 00:13:16 +04:00
2013-06-17 21:44:10 +04:00
%if ( 0%{!?_without_ocf:1} )
2012-11-06 13:13:07 +04:00
%package resource-agents
Summary : OCF Resource Agents for GlusterFS
License : GPLv3+
2013-04-23 20:57:40 +04:00
BuildArch : noarch
2012-11-06 13:13:07 +04:00
# this Group handling comes from the Fedora resource-agents package
# for glusterd
2016-05-09 12:56:37 +03:00
Requires : %{name} -server = %{version} -%{release}
2012-11-06 13:13:07 +04:00
# depending on the distribution, we need pacemaker or resource-agents
Requires : %{_prefix} /lib/ocf/resource.d
%description resource-agents
2014-09-05 08:12:18 +04:00
GlusterFS is a distributed file-system capable of scaling to several
2012-11-06 13:13:07 +04:00
petabytes. It aggregates various storage bricks over Infiniband RDMA
or TCP/IP interconnect into one large parallel network file
system. GlusterFS is one of the most sophisticated file systems in
terms of features and extensibility. It borrows a powerful concept
called Translators from GNU Hurd kernel. Much of the code in GlusterFS
is in user space and easily manageable.
This package provides the resource agents which plug glusterd into
Open Cluster Framework (OCF) compliant cluster resource managers,
like Pacemaker.
%endif
2018-01-31 18:38:34 +03:00
%if ( 0%{!?_without_server:1} )
2014-02-28 09:40:51 +04:00
%package server
Summary : Clustered file-system server
2016-01-08 18:43:15 +03:00
Requires : %{name} %{?_isa} = %{version} -%{release}
Requires : %{name} -cli%{?_isa} = %{version} -%{release}
Requires : %{name} -libs%{?_isa} = %{version} -%{release}
2015-05-05 11:28:15 +03:00
# some daemons (like quota) use a fuse-mount, glusterfsd is part of -fuse
2016-01-08 18:43:15 +03:00
Requires : %{name} -fuse%{?_isa} = %{version} -%{release}
2015-05-05 11:28:15 +03:00
# self-heal daemon, rebalance, nfs-server etc. are actually clients
2016-01-08 18:43:15 +03:00
Requires : %{name} -api%{?_isa} = %{version} -%{release}
Requires : %{name} -client-xlators%{?_isa} = %{version} -%{release}
2017-03-21 00:24:37 +03:00
# lvm2 for snapshot, and nfs-utils and rpcbind/portmap for gnfs server
2014-06-25 02:00:59 +04:00
Requires : lvm2
2015-05-05 11:28:15 +03:00
%if ( 0%{?_with_systemd:1} )
2016-11-30 17:08:03 +03:00
%{?systemd_requires}
2015-05-05 11:28:15 +03:00
%else
Requires(post) : /sbin/chkconfig
Requires(preun) : /sbin/service
Requires(preun) : /sbin/chkconfig
Requires(postun) : /sbin/service
%endif
2017-01-06 19:16:38 +03:00
%if (0%{?_with_firewalld:1})
# we install firewalld rules, so we need to have the directory owned
2017-04-20 16:46:46 +03:00
%if ( 0%{!?rhel} )
# not on RHEL because firewalld-filesystem appeared in 7.3
# when EL7 rpm gets weak dependencies we can add a Suggests:
2017-01-06 19:16:38 +03:00
Requires : firewalld-filesystem
%endif
2017-04-20 16:46:46 +03:00
%endif
2014-02-28 09:40:51 +04:00
%if ( 0%{?fedora} ) || ( 0%{?rhel} && 0%{?rhel} >= 6 )
Requires : rpcbind
%else
Requires : portmap
%endif
2015-04-21 21:15:07 +03:00
%if ( 0%{?rhel} && 0%{?rhel} <= 6 )
Requires : python-argparse
%endif
core: python3
see https://review.gluster.org/#/c/19788/,
https://review.gluster.org/#/c/19871/,
https://review.gluster.org/#/c/19952/,
https://review.gluster.org/#/c/20104/,
https://review.gluster.org/#/c/20162/,
https://review.gluster.org/#/c/20185/,
https://review.gluster.org/#/c/20207/,
https://review.gluster.org/#/c/20227/,
https://review.gluster.org/#/c/20307/,
https://review.gluster.org/#/c/20320/,
https://review.gluster.org/#/c/20332/,
https://review.gluster.org/#/c/20364/,
https://review.gluster.org/#/c/20441/, and
https://review.gluster.org/#/c/20484
shebangs changed from /usr/bin/python2 to /usr/bin/python3.
(Reminder, various distribution packaging guidelines require use
of explicit python version and don't allow '#!/usr/bin/env python',
regardless of how handy that idiom may be.)
glusterfs.spec(.in) package python{2,3}-gluster and python2 or
python3 dependencies as appropriate.
configure(.ac):
+ test for and use python2 or python3 as appropriate. If build
machine has python2 and python3, use python3. Override by
setting PYTHON=/usr/bin/python2 when running configure.
+ PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
better match to the original python sysconfig.get_python_inc().
All those other extraneous flags breaks the build.
+ Only change the shebangs once. Changing them over and over
again, e.g., during a `make glusterrpms` in extras/LinuxRPM
just sends make (is it really make that's looping?) into an
infinite loop. If you figure out why, let me know.
+ Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
Everything else has 2.7 or 3.x
+ logic from https://review.gluster.org/c/glusterfs/+/21050, which
needs to be removed/merged after that patch is merged.
Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
mysterious RHEL > 7.
Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
updates: #411
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
2018-08-29 18:09:27 +03:00
%if ( 0%{?fedora} && 0%{?fedora} > 27 ) || ( 0%{?rhel} && 0%{?rhel} > 7 )
Requires : python%{_pythonver}-pyxattr
2017-12-25 16:40:16 +03:00
%else
2015-04-21 21:15:07 +03:00
Requires : pyxattr
2017-12-25 16:40:16 +03:00
%endif
2017-02-28 09:37:00 +03:00
%if (0%{?_with_valgrind:1})
Requires : valgrind
%endif
2013-06-17 21:44:10 +04:00
2014-02-28 09:40:51 +04:00
%description server
2014-09-05 08:12:18 +04:00
GlusterFS is a distributed file-system capable of scaling to several
2013-06-17 21:44:10 +04:00
petabytes. It aggregates various storage bricks over Infiniband RDMA
or TCP/IP interconnect into one large parallel network file
system. GlusterFS is one of the most sophisticated file systems in
terms of features and extensibility. It borrows a powerful concept
called Translators from GNU Hurd kernel. Much of the code in GlusterFS
is in user space and easily manageable.
2014-02-28 09:40:51 +04:00
This package provides the glusterfs server daemon.
2018-01-31 18:38:34 +03:00
%endif
2013-08-21 11:50:41 +04:00
2019-01-30 11:54:14 +03:00
%package thin-arbiter
Summary : GlusterFS thin-arbiter module
Requires : %{name} %{?_isa} = %{version} -%{release}
Requires : %{name} -server%{?_isa} = %{version} -%{release}
%description thin-arbiter
This package provides a tie-breaker functionality to GlusterFS
replicate volume. It includes translators required to provide the
functionality, and also few other scripts required for getting the setup done.
This package provides the glusterfs thin-arbiter translator.
2015-05-05 11:28:15 +03:00
%package client-xlators
Summary : GlusterFS client-side translators
%description client-xlators
GlusterFS is a distributed file-system capable of scaling to several
petabytes. It aggregates various storage bricks over Infiniband RDMA
or TCP/IP interconnect into one large parallel network file
system. GlusterFS is one of the most sophisticated file systems in
terms of features and extensibility. It borrows a powerful concept
called Translators from GNU Hurd kernel. Much of the code in GlusterFS
is in user space and easily manageable.
This package provides the translators needed on any GlusterFS client.
eventsapi: Gluster Eventing Feature implementation
[Depends on http://review.gluster.org/14627]
Design is available in `glusterfs-specs`, A change from the design
is support of webhook instead of Websockets as discussed in the design
http://review.gluster.org/13115
Since Websocket support depends on REST APIs, I will add Websocket support
once REST APIs patch gets merged
Usage:
Run following command to start/stop Eventsapi server in all Peers,
which will collect the notifications from any Gluster daemon and emits
to configured client.
gluster-eventsapi start|stop|restart|reload
Status of running services can be checked using,
gluster-eventsapi status
Events listener is a HTTP(S) server which listens to events emited by
the Gluster. Create a HTTP Server to listen on POST and register that
URL using,
gluster-eventsapi webhook-add <URL> [--bearer-token <TOKEN>]
For example, if HTTP Server running in `http://192.168.122.188:9000`
then add that URL using,
gluster-eventsapi webhook-add http://192.168.122.188:9000
If it expects a Token then specify it using `--bearer-token` or `-t`
We can also test Webhook if all peer nodes can send message or not
using,
gluster-eventsapi webhook-test <URL> [--bearer-token <TOKEN>]
Configurations can be viewed/updated using,
gluster-eventsapi config-get [--name]
gluster-eventsapi config-set <NAME> <VALUE>
gluster-eventsapi config-reset <NAME|all>
If any one peer node was down during config-set/reset or webhook
modifications, Run sync command from good node when a peer node comes
back. Automatic update is not yet implemented.
gluster-eventsapi sync
Basic Events Client(HTTP Server) is included with the code, Start
running the client with required port and start listening to the
events.
/usr/share/glusterfs/scripts/eventsdash.py --port 8080
Default port is 9000, if no port is specified, once it started running
then configure gluster-eventsapi to send events to that client.
Eventsapi Client can be outside of the Cluster, it can be run event on
Windows. But only requirement is the client URL should be accessible
by all peer nodes.(Or ngrok(https://ngrok.com) like tools can be used)
Events implemented with this patch,
- Volume Create
- Volume Start
- Volume Stop
- Volume Delete
- Peer Attach
- Peer Detach
It is easy to add/support more events, since it touches Gluster cmd
code and to avoid merge conflicts I will add support for more events
once this patch merges.
BUG: 1334044
Change-Id: I316827ac9dd1443454df7deffe4f54835f7f6a08
Signed-off-by: Aravinda VK <avishwan@redhat.com>
Reviewed-on: http://review.gluster.org/14248
Smoke: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
2016-05-05 16:04:41 +03:00
%if ( 0%{!?_without_events:1} )
%package events
Summary : GlusterFS Events
Requires : %{name} -server%{?_isa} = %{version} -%{release}
core: python3
see https://review.gluster.org/#/c/19788/,
https://review.gluster.org/#/c/19871/,
https://review.gluster.org/#/c/19952/,
https://review.gluster.org/#/c/20104/,
https://review.gluster.org/#/c/20162/,
https://review.gluster.org/#/c/20185/,
https://review.gluster.org/#/c/20207/,
https://review.gluster.org/#/c/20227/,
https://review.gluster.org/#/c/20307/,
https://review.gluster.org/#/c/20320/,
https://review.gluster.org/#/c/20332/,
https://review.gluster.org/#/c/20364/,
https://review.gluster.org/#/c/20441/, and
https://review.gluster.org/#/c/20484
shebangs changed from /usr/bin/python2 to /usr/bin/python3.
(Reminder, various distribution packaging guidelines require use
of explicit python version and don't allow '#!/usr/bin/env python',
regardless of how handy that idiom may be.)
glusterfs.spec(.in) package python{2,3}-gluster and python2 or
python3 dependencies as appropriate.
configure(.ac):
+ test for and use python2 or python3 as appropriate. If build
machine has python2 and python3, use python3. Override by
setting PYTHON=/usr/bin/python2 when running configure.
+ PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
better match to the original python sysconfig.get_python_inc().
All those other extraneous flags breaks the build.
+ Only change the shebangs once. Changing them over and over
again, e.g., during a `make glusterrpms` in extras/LinuxRPM
just sends make (is it really make that's looping?) into an
infinite loop. If you figure out why, let me know.
+ Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
Everything else has 2.7 or 3.x
+ logic from https://review.gluster.org/c/glusterfs/+/21050, which
needs to be removed/merged after that patch is merged.
Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
mysterious RHEL > 7.
Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
updates: #411
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
2018-08-29 18:09:27 +03:00
Requires : python%{_pythonver} python%{_pythonver}-prettytable
Requires : python%{_pythonver}-gluster = %{version} -%{release}
%if ( 0%{?rhel} && 0%{?rhel} < 8 )
2017-12-28 11:34:50 +03:00
Requires : python-requests
2017-02-07 17:17:47 +03:00
%else
core: python3
see https://review.gluster.org/#/c/19788/,
https://review.gluster.org/#/c/19871/,
https://review.gluster.org/#/c/19952/,
https://review.gluster.org/#/c/20104/,
https://review.gluster.org/#/c/20162/,
https://review.gluster.org/#/c/20185/,
https://review.gluster.org/#/c/20207/,
https://review.gluster.org/#/c/20227/,
https://review.gluster.org/#/c/20307/,
https://review.gluster.org/#/c/20320/,
https://review.gluster.org/#/c/20332/,
https://review.gluster.org/#/c/20364/,
https://review.gluster.org/#/c/20441/, and
https://review.gluster.org/#/c/20484
shebangs changed from /usr/bin/python2 to /usr/bin/python3.
(Reminder, various distribution packaging guidelines require use
of explicit python version and don't allow '#!/usr/bin/env python',
regardless of how handy that idiom may be.)
glusterfs.spec(.in) package python{2,3}-gluster and python2 or
python3 dependencies as appropriate.
configure(.ac):
+ test for and use python2 or python3 as appropriate. If build
machine has python2 and python3, use python3. Override by
setting PYTHON=/usr/bin/python2 when running configure.
+ PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
better match to the original python sysconfig.get_python_inc().
All those other extraneous flags breaks the build.
+ Only change the shebangs once. Changing them over and over
again, e.g., during a `make glusterrpms` in extras/LinuxRPM
just sends make (is it really make that's looping?) into an
infinite loop. If you figure out why, let me know.
+ Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
Everything else has 2.7 or 3.x
+ logic from https://review.gluster.org/c/glusterfs/+/21050, which
needs to be removed/merged after that patch is merged.
Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
mysterious RHEL > 7.
Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
updates: #411
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
2018-08-29 18:09:27 +03:00
Requires : python%{_pythonver}-requests
2017-02-07 17:17:47 +03:00
%endif
%if ( 0%{?rhel} && 0%{?rhel} < 7 )
eventsapi: Gluster Eventing Feature implementation
[Depends on http://review.gluster.org/14627]
Design is available in `glusterfs-specs`, A change from the design
is support of webhook instead of Websockets as discussed in the design
http://review.gluster.org/13115
Since Websocket support depends on REST APIs, I will add Websocket support
once REST APIs patch gets merged
Usage:
Run following command to start/stop Eventsapi server in all Peers,
which will collect the notifications from any Gluster daemon and emits
to configured client.
gluster-eventsapi start|stop|restart|reload
Status of running services can be checked using,
gluster-eventsapi status
Events listener is a HTTP(S) server which listens to events emited by
the Gluster. Create a HTTP Server to listen on POST and register that
URL using,
gluster-eventsapi webhook-add <URL> [--bearer-token <TOKEN>]
For example, if HTTP Server running in `http://192.168.122.188:9000`
then add that URL using,
gluster-eventsapi webhook-add http://192.168.122.188:9000
If it expects a Token then specify it using `--bearer-token` or `-t`
We can also test Webhook if all peer nodes can send message or not
using,
gluster-eventsapi webhook-test <URL> [--bearer-token <TOKEN>]
Configurations can be viewed/updated using,
gluster-eventsapi config-get [--name]
gluster-eventsapi config-set <NAME> <VALUE>
gluster-eventsapi config-reset <NAME|all>
If any one peer node was down during config-set/reset or webhook
modifications, Run sync command from good node when a peer node comes
back. Automatic update is not yet implemented.
gluster-eventsapi sync
Basic Events Client(HTTP Server) is included with the code, Start
running the client with required port and start listening to the
events.
/usr/share/glusterfs/scripts/eventsdash.py --port 8080
Default port is 9000, if no port is specified, once it started running
then configure gluster-eventsapi to send events to that client.
Eventsapi Client can be outside of the Cluster, it can be run event on
Windows. But only requirement is the client URL should be accessible
by all peer nodes.(Or ngrok(https://ngrok.com) like tools can be used)
Events implemented with this patch,
- Volume Create
- Volume Start
- Volume Stop
- Volume Delete
- Peer Attach
- Peer Detach
It is easy to add/support more events, since it touches Gluster cmd
code and to avoid merge conflicts I will add support for more events
once this patch merges.
BUG: 1334044
Change-Id: I316827ac9dd1443454df7deffe4f54835f7f6a08
Signed-off-by: Aravinda VK <avishwan@redhat.com>
Reviewed-on: http://review.gluster.org/14248
Smoke: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
2016-05-05 16:04:41 +03:00
Requires : python-argparse
%endif
2016-09-13 11:51:29 +03:00
%if ( 0%{?_with_systemd:1} )
2016-11-30 17:08:03 +03:00
%{?systemd_requires}
2016-09-13 11:51:29 +03:00
%endif
eventsapi: Gluster Eventing Feature implementation
[Depends on http://review.gluster.org/14627]
Design is available in `glusterfs-specs`, A change from the design
is support of webhook instead of Websockets as discussed in the design
http://review.gluster.org/13115
Since Websocket support depends on REST APIs, I will add Websocket support
once REST APIs patch gets merged
Usage:
Run following command to start/stop Eventsapi server in all Peers,
which will collect the notifications from any Gluster daemon and emits
to configured client.
gluster-eventsapi start|stop|restart|reload
Status of running services can be checked using,
gluster-eventsapi status
Events listener is a HTTP(S) server which listens to events emited by
the Gluster. Create a HTTP Server to listen on POST and register that
URL using,
gluster-eventsapi webhook-add <URL> [--bearer-token <TOKEN>]
For example, if HTTP Server running in `http://192.168.122.188:9000`
then add that URL using,
gluster-eventsapi webhook-add http://192.168.122.188:9000
If it expects a Token then specify it using `--bearer-token` or `-t`
We can also test Webhook if all peer nodes can send message or not
using,
gluster-eventsapi webhook-test <URL> [--bearer-token <TOKEN>]
Configurations can be viewed/updated using,
gluster-eventsapi config-get [--name]
gluster-eventsapi config-set <NAME> <VALUE>
gluster-eventsapi config-reset <NAME|all>
If any one peer node was down during config-set/reset or webhook
modifications, Run sync command from good node when a peer node comes
back. Automatic update is not yet implemented.
gluster-eventsapi sync
Basic Events Client(HTTP Server) is included with the code, Start
running the client with required port and start listening to the
events.
/usr/share/glusterfs/scripts/eventsdash.py --port 8080
Default port is 9000, if no port is specified, once it started running
then configure gluster-eventsapi to send events to that client.
Eventsapi Client can be outside of the Cluster, it can be run event on
Windows. But only requirement is the client URL should be accessible
by all peer nodes.(Or ngrok(https://ngrok.com) like tools can be used)
Events implemented with this patch,
- Volume Create
- Volume Start
- Volume Stop
- Volume Delete
- Peer Attach
- Peer Detach
It is easy to add/support more events, since it touches Gluster cmd
code and to avoid merge conflicts I will add support for more events
once this patch merges.
BUG: 1334044
Change-Id: I316827ac9dd1443454df7deffe4f54835f7f6a08
Signed-off-by: Aravinda VK <avishwan@redhat.com>
Reviewed-on: http://review.gluster.org/14248
Smoke: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
2016-05-05 16:04:41 +03:00
%description events
GlusterFS Events
%endif
2009-02-18 15:06:07 +03:00
%prep
2013-06-17 21:44:10 +04:00
%setup -q -n %{name} -%{version} %{?prereltag}
2018-09-24 21:12:45 +03:00
%if ( ! %{_usepython3} )
echo " f i x i n g p y t h o n s h e b a n g s . . . "
for f in api events extras geo-replication libglusterfs tools xlators; do
find $f -type f -exec sed -i 's|/usr/bin/python3|/usr/bin/python2|' {} \;
done
%endif
2009-02-18 15:06:07 +03:00
%build
2015-11-05 17:27:51 +03:00
2016-05-23 12:06:38 +03:00
# RHEL6 and earlier need to manually replace config.guess and config.sub
%if ( 0%{?rhel} && 0%{?rhel} <= 6 )
./autogen.sh
%endif
%configure \
2018-08-10 02:32:22 +03:00
%{?_with_asan} \
2015-05-17 16:26:03 +03:00
%{?_with_cmocka} \
2015-05-31 22:50:21 +03:00
%{?_with_debug} \
2017-03-27 23:09:56 +03:00
%{?_with_firewalld} \
%{?_with_gnfs} \
2015-01-16 15:48:49 +03:00
%{?_with_tmpfilesdir} \
2018-11-13 14:53:17 +03:00
%{?_with_tsan} \
2017-03-27 23:09:56 +03:00
%{?_with_valgrind} \
2013-09-11 15:44:10 +04:00
%{?_without_epoll} \
2017-03-27 23:09:56 +03:00
%{?_without_events} \
2013-09-11 15:44:10 +04:00
%{?_without_fusermount} \
%{?_without_georeplication} \
%{?_without_ocf} \
2015-05-17 16:26:03 +03:00
%{?_without_rdma} \
2018-01-31 18:38:34 +03:00
%{?_without_server} \
2015-05-17 16:26:03 +03:00
%{?_without_syslog} \
2018-01-18 23:24:00 +03:00
%{?_with_ipv6default} \
%{?_without_libtirpc}
2009-04-16 17:15:48 +04:00
2013-06-27 18:44:44 +04:00
# fix hardening and remove rpath in shlibs
%if ( 0%{?fedora} && 0%{?fedora} > 17 ) || ( 0%{?rhel} && 0%{?rhel} > 6 )
2013-12-10 16:26:46 +04:00
sed -i 's| \\\$compiler_flags |&\\\$LDFLAGS |' libtool
2013-06-27 18:44:44 +04:00
%endif
2013-12-10 16:26:46 +04:00
sed -i 's|^hardcode_libdir_flag_spec=.*|hardcode_libdir_flag_spec=""|' libtool
sed -i 's|^runpath_var=LD_RUN_PATH|runpath_var=DIE_RPATH_DIE|' libtool
2011-11-10 06:27:25 +04:00
2013-12-10 16:26:46 +04:00
make %{?_smp_mflags}
2009-02-18 15:06:07 +03:00
2014-04-24 00:18:57 +04:00
%check
make check
2009-02-18 15:06:07 +03:00
%install
2013-12-10 16:26:46 +04:00
rm -rf %{buildroot}
make install DESTDIR=%{buildroot}
2019-02-25 14:32:21 +03:00
%if ( 0%{!?_without_server:1} )
2013-06-17 21:44:10 +04:00
%if ( 0%{_for_fedora_koji_builds} )
2013-12-10 16:26:46 +04:00
install -D -p -m 0644 %{SOURCE1} \
2013-01-30 20:29:54 +04:00
%{buildroot} %{_sysconfdir} /sysconfig/glusterd
2013-12-10 16:26:46 +04:00
install -D -p -m 0644 %{SOURCE2} \
2013-01-30 20:29:54 +04:00
%{buildroot} %{_sysconfdir} /sysconfig/glusterfsd
%else
2013-12-10 16:26:46 +04:00
install -D -p -m 0644 extras/glusterd-sysconfig \
2013-01-30 20:29:54 +04:00
%{buildroot} %{_sysconfdir} /sysconfig/glusterd
%endif
2018-01-31 18:38:34 +03:00
%endif
2009-04-16 17:15:48 +04:00
2013-12-10 16:26:46 +04:00
mkdir -p %{buildroot} %{_localstatedir} /log/glusterd
mkdir -p %{buildroot} %{_localstatedir} /log/glusterfs
mkdir -p %{buildroot} %{_localstatedir} /log/glusterfsd
2017-08-10 20:13:39 +03:00
mkdir -p %{buildroot} %{_rundir} /gluster
2011-09-20 11:36:11 +04:00
2011-11-10 06:27:25 +04:00
# Remove unwanted files from all the shared libraries
find %{buildroot} %{_libdir} -name '*.a' -delete
find %{buildroot} %{_libdir} -name '*.la' -delete
2009-02-18 15:06:07 +03:00
2013-12-10 16:26:46 +04:00
# Remove installed docs, the ones we want are included by %%doc, in
# /usr/share/doc/glusterfs or /usr/share/doc/glusterfs-x.y.z depending
# on the distribution
%if ( 0%{?fedora} && 0%{?fedora} > 19 ) || ( 0%{?rhel} && 0%{?rhel} > 6 )
rm -rf %{buildroot} %{_pkgdocdir} /*
%else
rm -rf %{buildroot} %{_defaultdocdir} /%{name}
mkdir -p %{buildroot} %{_pkgdocdir}
%endif
2013-06-27 18:44:44 +04:00
head -50 ChangeLog > ChangeLog.head && mv ChangeLog.head ChangeLog
cat << EOM >> ChangeLog
More commit messages for this ChangeLog can be found at
https://forge.gluster.org/glusterfs-core/glusterfs/commits/v%{version} %{?prereltag}
EOM
2011-02-22 11:29:07 +03:00
2013-01-30 20:29:54 +04:00
# Remove benchmarking and other unpackaged files
2014-04-25 18:14:14 +04:00
# make install always puts these in %%{_defaultdocdir}/%%{name} so don't
# use %%{_pkgdocdir}; that will be wrong on later Fedora distributions
rm -rf %{buildroot} %{_defaultdocdir} /%{name} /benchmarking
rm -f %{buildroot} %{_defaultdocdir} /%{name} /glusterfs-mode.el
rm -f %{buildroot} %{_defaultdocdir} /%{name} /glusterfs.vim
2011-02-22 11:29:07 +03:00
2018-01-31 18:38:34 +03:00
%if ( 0%{!?_without_server:1} )
2011-11-10 06:27:25 +04:00
# Create working directory
2013-12-10 16:26:46 +04:00
mkdir -p %{buildroot} %{_sharedstatedir} /glusterd
2011-02-22 11:29:07 +03:00
2011-11-10 06:27:25 +04:00
# Update configuration file to /var/lib working directory
sed -i 's|option working-directory /etc/glusterd|option working-directory %{_sharedstatedir}/glusterd|g' \
%{buildroot} %{_sysconfdir} /glusterfs/glusterd.vol
2018-01-31 18:38:34 +03:00
%endif
2011-05-30 08:45:19 +04:00
2013-07-30 22:00:46 +04:00
# Install glusterfsd .service or init.d file
2019-02-25 14:32:21 +03:00
%if ( 0%{!?_without_server:1} )
2013-07-30 22:00:46 +04:00
%if ( 0%{_for_fedora_koji_builds} )
2017-10-04 21:22:05 +03:00
%service_install glusterfsd %{glusterfsd_svcfile}
2013-07-30 22:00:46 +04:00
%endif
2019-02-25 14:32:21 +03:00
%endif
2013-07-30 22:00:46 +04:00
2013-12-10 16:26:46 +04:00
install -D -p -m 0644 extras/glusterfs-logrotate \
2013-01-30 20:29:54 +04:00
%{buildroot} %{_sysconfdir} /logrotate.d/glusterfs
2012-12-10 17:41:10 +04:00
2013-06-17 21:44:10 +04:00
%if ( 0%{!?_without_georeplication:1} )
2013-01-30 20:29:54 +04:00
# geo-rep ghosts
2013-12-10 16:26:46 +04:00
mkdir -p %{buildroot} %{_sharedstatedir} /glusterd/geo-replication
2013-07-10 16:02:41 +04:00
touch %{buildroot} %{_sharedstatedir} /glusterd/geo-replication/gsyncd_template.conf
2013-12-10 16:26:46 +04:00
install -D -p -m 0644 extras/glusterfs-georep-logrotate \
2013-09-19 12:54:35 +04:00
%{buildroot} %{_sysconfdir} /logrotate.d/glusterfs-georep
2013-01-30 20:29:54 +04:00
%endif
2018-01-31 18:38:34 +03:00
%if ( 0%{!?_without_server:1} )
2013-01-30 20:29:54 +04:00
# the rest of the ghosts
2012-07-16 20:11:17 +04:00
touch %{buildroot} %{_sharedstatedir} /glusterd/glusterd.info
2013-01-02 19:37:04 +04:00
touch %{buildroot} %{_sharedstatedir} /glusterd/options
2016-04-12 18:35:38 +03:00
subdirs=(add-brick create copy-file delete gsync-create remove-brick reset set start stop)
for dir in ${subdirs[@]}; do
mkdir -p %{buildroot} %{_sharedstatedir} /glusterd/hooks/1/" $ d i r " /{pre,post}
done
2013-12-10 16:26:46 +04:00
mkdir -p %{buildroot} %{_sharedstatedir} /glusterd/glustershd
mkdir -p %{buildroot} %{_sharedstatedir} /glusterd/peers
mkdir -p %{buildroot} %{_sharedstatedir} /glusterd/vols
mkdir -p %{buildroot} %{_sharedstatedir} /glusterd/nfs/run
2016-04-12 18:35:38 +03:00
mkdir -p %{buildroot} %{_sharedstatedir} /glusterd/bitd
mkdir -p %{buildroot} %{_sharedstatedir} /glusterd/quotad
mkdir -p %{buildroot} %{_sharedstatedir} /glusterd/scrub
mkdir -p %{buildroot} %{_sharedstatedir} /glusterd/snaps
mkdir -p %{buildroot} %{_sharedstatedir} /glusterd/ss_brick
2013-01-30 20:29:54 +04:00
touch %{buildroot} %{_sharedstatedir} /glusterd/nfs/nfs-server.vol
touch %{buildroot} %{_sharedstatedir} /glusterd/nfs/run/nfs.pid
2018-01-31 18:38:34 +03:00
%endif
2013-01-30 20:29:54 +04:00
2013-09-16 06:56:25 +04:00
find ./tests ./run-tests.sh -type f | cpio -pd %{buildroot} %{_prefix} /share/glusterfs
2014-06-04 13:31:14 +04:00
## Install bash completion for cli
2018-01-31 18:38:34 +03:00
%if ( 0%{!?_without_server:1} )
2014-06-04 13:31:14 +04:00
install -p -m 0744 -D extras/command-completion/gluster.bash \
%{buildroot} %{_sysconfdir} /bash_completion.d/gluster
2018-01-31 18:38:34 +03:00
%endif
2014-06-04 13:31:14 +04:00
2011-11-10 06:27:25 +04:00
%clean
2013-12-10 16:26:46 +04:00
rm -rf %{buildroot}
2009-04-16 17:15:48 +04:00
2014-02-28 09:40:51 +04:00
##-----------------------------------------------------------------------------
packaging: rpm scriptlet cleanup, handle -p /sbin/ldconfig
The RPM documention indicates that during an rpm install or erase, the
script(lets): %post, %preun, and %postun (and %pre, %build, %install,
etc.) are copied to a temp file, and then the temp file is run as a
(/bin/sh or bash) script.
Unfortunately the documentation is not clear about how rpmbuild and/or
rpm determine where the end of any scriptlet is when it is copied to
the file.
Most things in the glusterfs.spec work correctly as is. These are the
%preun, %post, and %postun scriptlets that are "closed" by a following
%preun, %post, and %postun, or poetentially another scriptlet, e.g.
%file.
The ones that don't work correctly (only one actually) are those where
there is a comment in the spec file before it is closed by another
scriptlet. Further complicating things is that the type of scriptlet
affects what rpm does and what `rpm -qp --scripts ...` shows.
The specific one that didn't work was the "%postun libs" scriptlet. It
is followed by a comment before being "closed" by the %files section (or
scriptlet). It can be written two ways: "%postun libs\n/sbin/ldconfig"
or "%postun libs -p /sbin/ldconfig" Either way it's written, `rpm -qp
--scripts glusterfs-libs...` will include the comment lines between the
%postun libs line and the following %files line.
But the way rpm executes these depends on how they're written. If
written as "%postun libs\n/sbin/ldconfig" rpm will simply run
/sbin/ldconfig with no command line options, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig" ], [ ]);
But when written as "%postun libs -p /sbin/ldconfig", it will copy
the comment lines to a temp file, and pass the temp file name and "1"
as (command line) parameters, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig", "/tmp/tmpXXXXXX", "1" ],
[ ]);
Which results in ldconfig exiting with an error. (Remember, both ways show
the comment in `rpm -qp --scripts ...`)
(Note though, that the similar "%postun api -p /sbin/ldconfig" is run
correctly, because it is "closed" by the following "%postun server"
scriptlet.)
Finally, through trial and error, it appears that rpm can be tricked with
a hack, and "closure" of the scriptlet forcedlike this:
%postun libs -p /sbin/ldconfig
%if ( 0%{?_undocumented_hack_closes_scriptlets} )
%postun
%endif
in which case ldconfig appears to run correctly. Note also that here too
the comment will be included in the output of `rpm -qp --scripts ...`
But that's very ugly hack.
Change-Id: I587a490ddcdf47d01605479bc8ef8b0e439108fb
BUG: 1315024
Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
Reviewed-on: http://review.gluster.org/13613
Smoke: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
2016-03-06 00:06:18 +03:00
## All %%post should be placed here and keep them sorted
2014-02-28 09:40:51 +04:00
##
2011-11-10 06:27:25 +04:00
%post
packaging: rpm scriptlet cleanup, handle -p /sbin/ldconfig
The RPM documention indicates that during an rpm install or erase, the
script(lets): %post, %preun, and %postun (and %pre, %build, %install,
etc.) are copied to a temp file, and then the temp file is run as a
(/bin/sh or bash) script.
Unfortunately the documentation is not clear about how rpmbuild and/or
rpm determine where the end of any scriptlet is when it is copied to
the file.
Most things in the glusterfs.spec work correctly as is. These are the
%preun, %post, and %postun scriptlets that are "closed" by a following
%preun, %post, and %postun, or poetentially another scriptlet, e.g.
%file.
The ones that don't work correctly (only one actually) are those where
there is a comment in the spec file before it is closed by another
scriptlet. Further complicating things is that the type of scriptlet
affects what rpm does and what `rpm -qp --scripts ...` shows.
The specific one that didn't work was the "%postun libs" scriptlet. It
is followed by a comment before being "closed" by the %files section (or
scriptlet). It can be written two ways: "%postun libs\n/sbin/ldconfig"
or "%postun libs -p /sbin/ldconfig" Either way it's written, `rpm -qp
--scripts glusterfs-libs...` will include the comment lines between the
%postun libs line and the following %files line.
But the way rpm executes these depends on how they're written. If
written as "%postun libs\n/sbin/ldconfig" rpm will simply run
/sbin/ldconfig with no command line options, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig" ], [ ]);
But when written as "%postun libs -p /sbin/ldconfig", it will copy
the comment lines to a temp file, and pass the temp file name and "1"
as (command line) parameters, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig", "/tmp/tmpXXXXXX", "1" ],
[ ]);
Which results in ldconfig exiting with an error. (Remember, both ways show
the comment in `rpm -qp --scripts ...`)
(Note though, that the similar "%postun api -p /sbin/ldconfig" is run
correctly, because it is "closed" by the following "%postun server"
scriptlet.)
Finally, through trial and error, it appears that rpm can be tricked with
a hack, and "closure" of the scriptlet forcedlike this:
%postun libs -p /sbin/ldconfig
%if ( 0%{?_undocumented_hack_closes_scriptlets} )
%postun
%endif
in which case ldconfig appears to run correctly. Note also that here too
the comment will be included in the output of `rpm -qp --scripts ...`
But that's very ugly hack.
Change-Id: I587a490ddcdf47d01605479bc8ef8b0e439108fb
BUG: 1315024
Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
Reviewed-on: http://review.gluster.org/13613
Smoke: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
2016-03-06 00:06:18 +03:00
/sbin/ldconfig
2013-10-18 09:36:59 +04:00
%if ( 0%{!?_without_syslog:1} )
%if ( 0%{?fedora} ) || ( 0%{?rhel} && 0%{?rhel} >= 6 )
2017-10-04 21:22:05 +03:00
%systemd_postun_with_restart rsyslog
2013-10-18 09:36:59 +04:00
%endif
%endif
2016-04-26 17:10:05 +03:00
exit 0
2009-04-16 17:15:48 +04:00
2016-05-12 22:42:10 +03:00
%post api
/sbin/ldconfig
2014-02-28 09:40:51 +04:00
2016-10-18 12:27:47 +03:00
%if ( 0%{!?_without_events:1} )
%post events
2017-10-04 21:22:05 +03:00
%systemd_post glustereventsd
2016-10-18 12:27:47 +03:00
%endif
2014-02-28 09:40:51 +04:00
%if ( 0%{!?_without_georeplication:1} )
%post geo-replication
if [ $1 -ge 1 ]; then
2017-10-04 21:22:05 +03:00
%systemd_postun_with_restart glusterd
2014-02-28 09:40:51 +04:00
fi
packaging: rpm scriptlet cleanup, handle -p /sbin/ldconfig
The RPM documention indicates that during an rpm install or erase, the
script(lets): %post, %preun, and %postun (and %pre, %build, %install,
etc.) are copied to a temp file, and then the temp file is run as a
(/bin/sh or bash) script.
Unfortunately the documentation is not clear about how rpmbuild and/or
rpm determine where the end of any scriptlet is when it is copied to
the file.
Most things in the glusterfs.spec work correctly as is. These are the
%preun, %post, and %postun scriptlets that are "closed" by a following
%preun, %post, and %postun, or poetentially another scriptlet, e.g.
%file.
The ones that don't work correctly (only one actually) are those where
there is a comment in the spec file before it is closed by another
scriptlet. Further complicating things is that the type of scriptlet
affects what rpm does and what `rpm -qp --scripts ...` shows.
The specific one that didn't work was the "%postun libs" scriptlet. It
is followed by a comment before being "closed" by the %files section (or
scriptlet). It can be written two ways: "%postun libs\n/sbin/ldconfig"
or "%postun libs -p /sbin/ldconfig" Either way it's written, `rpm -qp
--scripts glusterfs-libs...` will include the comment lines between the
%postun libs line and the following %files line.
But the way rpm executes these depends on how they're written. If
written as "%postun libs\n/sbin/ldconfig" rpm will simply run
/sbin/ldconfig with no command line options, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig" ], [ ]);
But when written as "%postun libs -p /sbin/ldconfig", it will copy
the comment lines to a temp file, and pass the temp file name and "1"
as (command line) parameters, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig", "/tmp/tmpXXXXXX", "1" ],
[ ]);
Which results in ldconfig exiting with an error. (Remember, both ways show
the comment in `rpm -qp --scripts ...`)
(Note though, that the similar "%postun api -p /sbin/ldconfig" is run
correctly, because it is "closed" by the following "%postun server"
scriptlet.)
Finally, through trial and error, it appears that rpm can be tricked with
a hack, and "closure" of the scriptlet forcedlike this:
%postun libs -p /sbin/ldconfig
%if ( 0%{?_undocumented_hack_closes_scriptlets} )
%postun
%endif
in which case ldconfig appears to run correctly. Note also that here too
the comment will be included in the output of `rpm -qp --scripts ...`
But that's very ugly hack.
Change-Id: I587a490ddcdf47d01605479bc8ef8b0e439108fb
BUG: 1315024
Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
Reviewed-on: http://review.gluster.org/13613
Smoke: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
2016-03-06 00:06:18 +03:00
exit 0
2014-02-28 09:40:51 +04:00
%endif
2016-05-12 22:42:10 +03:00
%post libs
/sbin/ldconfig
2014-02-28 09:40:51 +04:00
2018-01-31 18:38:34 +03:00
%if ( 0%{!?_without_server:1} )
2014-02-28 09:40:51 +04:00
%post server
# Legacy server
2017-10-04 21:22:05 +03:00
%systemd_post glusterd
2016-04-12 18:35:38 +03:00
%if ( 0%{_for_fedora_koji_builds} )
2017-10-04 21:22:05 +03:00
%systemd_post glusterfsd
2016-04-12 18:35:38 +03:00
%endif
2015-02-25 17:07:22 +03:00
# ".cmd_log_history" is renamed to "cmd_history.log" in GlusterFS-3.7 .
# While upgrading glusterfs-server package form GlusterFS version <= 3.6 to
# GlusterFS version 3.7, ".cmd_log_history" should be renamed to
2015-02-13 14:40:37 +03:00
# "cmd_history.log" to retain cli command history contents.
if [ -f %{_localstatedir} /log/glusterfs/.cmd_log_history ]; then
mv %{_localstatedir} /log/glusterfs/.cmd_log_history \
%{_localstatedir} /log/glusterfs/cmd_history.log
fi
2014-02-28 09:40:51 +04:00
# Genuine Fedora (and EPEL) builds never put gluster files in /etc; if
# there are any files in /etc from a prior gluster.org install, move them
# to /var/lib. (N.B. Starting with 3.3.0 all gluster files are in /var/lib
# in gluster.org RPMs.) Be careful to copy them on the off chance that
# /etc and /var/lib are on separate file systems
if [ -d /etc/glusterd -a ! -h %{_sharedstatedir} /glusterd ]; then
mkdir -p %{_sharedstatedir} /glusterd
cp -a /etc/glusterd %{_sharedstatedir} /glusterd
rm -rf /etc/glusterd
ln -sf %{_sharedstatedir} /glusterd /etc/glusterd
fi
# Rename old volfiles in an RPM-standard way. These aren't actually
# considered package config files, so %%config doesn't work for them.
if [ -d %{_sharedstatedir} /glusterd/vols ]; then
for file in $(find %{_sharedstatedir} /glusterd/vols -name '*.vol' ); do
newfile=${file}.rpmsave
echo " w a r n i n g : $ { f i l e } s a v e d a s $ { n e w f i l e } "
cp ${file} ${newfile}
done
fi
# add marker translator
# but first make certain that there are no old libs around to bite us
# BZ 834847
if [ -e /etc/ld.so.conf.d/glusterfs.conf ]; then
rm -f /etc/ld.so.conf.d/glusterfs.conf
/sbin/ldconfig
fi
2015-08-21 22:39:53 +03:00
%if (0%{?_with_firewalld:1})
2017-01-06 19:16:38 +03:00
%firewalld_reload
2015-08-21 22:39:53 +03:00
%endif
2014-02-28 09:40:51 +04:00
pidof -c -o %PPID -x glusterd &> /dev/null
if [ $? -eq 0 ]; then
kill -9 `pgrep -f gsyncd.py` &> /dev/null
2014-06-27 01:14:39 +04:00
killall --wait glusterd &> /dev/null
2014-02-28 09:40:51 +04:00
glusterd --xlator-option *.upgrade=on -N
2015-05-19 12:01:23 +03:00
#Cleaning leftover glusterd socket file which is created by glusterd in
#rpm_script_t context.
2017-08-10 20:13:39 +03:00
rm -f %{_rundir} /glusterd.socket
2015-05-19 12:01:23 +03:00
2014-09-25 17:11:46 +04:00
# glusterd _was_ running, we killed it, it exited after *.upgrade=on,
# so start it again
2017-10-04 21:22:05 +03:00
%service_start glusterd
2014-02-28 09:40:51 +04:00
else
glusterd --xlator-option *.upgrade=on -N
2015-05-19 12:01:23 +03:00
#Cleaning leftover glusterd socket file which is created by glusterd in
#rpm_script_t context.
2017-08-10 20:13:39 +03:00
rm -f %{_rundir} /glusterd.socket
2014-02-28 09:40:51 +04:00
fi
packaging: rpm scriptlet cleanup, handle -p /sbin/ldconfig
The RPM documention indicates that during an rpm install or erase, the
script(lets): %post, %preun, and %postun (and %pre, %build, %install,
etc.) are copied to a temp file, and then the temp file is run as a
(/bin/sh or bash) script.
Unfortunately the documentation is not clear about how rpmbuild and/or
rpm determine where the end of any scriptlet is when it is copied to
the file.
Most things in the glusterfs.spec work correctly as is. These are the
%preun, %post, and %postun scriptlets that are "closed" by a following
%preun, %post, and %postun, or poetentially another scriptlet, e.g.
%file.
The ones that don't work correctly (only one actually) are those where
there is a comment in the spec file before it is closed by another
scriptlet. Further complicating things is that the type of scriptlet
affects what rpm does and what `rpm -qp --scripts ...` shows.
The specific one that didn't work was the "%postun libs" scriptlet. It
is followed by a comment before being "closed" by the %files section (or
scriptlet). It can be written two ways: "%postun libs\n/sbin/ldconfig"
or "%postun libs -p /sbin/ldconfig" Either way it's written, `rpm -qp
--scripts glusterfs-libs...` will include the comment lines between the
%postun libs line and the following %files line.
But the way rpm executes these depends on how they're written. If
written as "%postun libs\n/sbin/ldconfig" rpm will simply run
/sbin/ldconfig with no command line options, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig" ], [ ]);
But when written as "%postun libs -p /sbin/ldconfig", it will copy
the comment lines to a temp file, and pass the temp file name and "1"
as (command line) parameters, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig", "/tmp/tmpXXXXXX", "1" ],
[ ]);
Which results in ldconfig exiting with an error. (Remember, both ways show
the comment in `rpm -qp --scripts ...`)
(Note though, that the similar "%postun api -p /sbin/ldconfig" is run
correctly, because it is "closed" by the following "%postun server"
scriptlet.)
Finally, through trial and error, it appears that rpm can be tricked with
a hack, and "closure" of the scriptlet forcedlike this:
%postun libs -p /sbin/ldconfig
%if ( 0%{?_undocumented_hack_closes_scriptlets} )
%postun
%endif
in which case ldconfig appears to run correctly. Note also that here too
the comment will be included in the output of `rpm -qp --scripts ...`
But that's very ugly hack.
Change-Id: I587a490ddcdf47d01605479bc8ef8b0e439108fb
BUG: 1315024
Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
Reviewed-on: http://review.gluster.org/13613
Smoke: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
2016-03-06 00:06:18 +03:00
exit 0
2018-01-31 18:38:34 +03:00
%endif
2014-02-28 09:40:51 +04:00
2017-04-26 15:11:56 +03:00
##-----------------------------------------------------------------------------
## All %%pre should be placed here and keep them sorted
##
%pre
getent group gluster > /dev/null || groupadd -r gluster
2017-08-10 20:13:39 +03:00
getent passwd gluster > /dev/null || useradd -r -g gluster -d %{_rundir} /gluster -s /sbin/nologin -c " G l u s t e r F S d a e m o n s " gluster
2017-04-26 15:11:56 +03:00
exit 0
2014-02-28 09:40:51 +04:00
##-----------------------------------------------------------------------------
packaging: rpm scriptlet cleanup, handle -p /sbin/ldconfig
The RPM documention indicates that during an rpm install or erase, the
script(lets): %post, %preun, and %postun (and %pre, %build, %install,
etc.) are copied to a temp file, and then the temp file is run as a
(/bin/sh or bash) script.
Unfortunately the documentation is not clear about how rpmbuild and/or
rpm determine where the end of any scriptlet is when it is copied to
the file.
Most things in the glusterfs.spec work correctly as is. These are the
%preun, %post, and %postun scriptlets that are "closed" by a following
%preun, %post, and %postun, or poetentially another scriptlet, e.g.
%file.
The ones that don't work correctly (only one actually) are those where
there is a comment in the spec file before it is closed by another
scriptlet. Further complicating things is that the type of scriptlet
affects what rpm does and what `rpm -qp --scripts ...` shows.
The specific one that didn't work was the "%postun libs" scriptlet. It
is followed by a comment before being "closed" by the %files section (or
scriptlet). It can be written two ways: "%postun libs\n/sbin/ldconfig"
or "%postun libs -p /sbin/ldconfig" Either way it's written, `rpm -qp
--scripts glusterfs-libs...` will include the comment lines between the
%postun libs line and the following %files line.
But the way rpm executes these depends on how they're written. If
written as "%postun libs\n/sbin/ldconfig" rpm will simply run
/sbin/ldconfig with no command line options, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig" ], [ ]);
But when written as "%postun libs -p /sbin/ldconfig", it will copy
the comment lines to a temp file, and pass the temp file name and "1"
as (command line) parameters, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig", "/tmp/tmpXXXXXX", "1" ],
[ ]);
Which results in ldconfig exiting with an error. (Remember, both ways show
the comment in `rpm -qp --scripts ...`)
(Note though, that the similar "%postun api -p /sbin/ldconfig" is run
correctly, because it is "closed" by the following "%postun server"
scriptlet.)
Finally, through trial and error, it appears that rpm can be tricked with
a hack, and "closure" of the scriptlet forcedlike this:
%postun libs -p /sbin/ldconfig
%if ( 0%{?_undocumented_hack_closes_scriptlets} )
%postun
%endif
in which case ldconfig appears to run correctly. Note also that here too
the comment will be included in the output of `rpm -qp --scripts ...`
But that's very ugly hack.
Change-Id: I587a490ddcdf47d01605479bc8ef8b0e439108fb
BUG: 1315024
Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
Reviewed-on: http://review.gluster.org/13613
Smoke: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
2016-03-06 00:06:18 +03:00
## All %%preun should be placed here and keep them sorted
2014-02-28 09:40:51 +04:00
##
2016-10-18 12:27:47 +03:00
%if ( 0%{!?_without_events:1} )
%preun events
if [ $1 -eq 0 ]; then
2017-10-04 21:22:05 +03:00
if [ -f %glustereventsd_svcfile ]; then
%service_stop glustereventsd
%systemd_preun glustereventsd
2016-10-18 12:27:47 +03:00
fi
fi
exit 0
%endif
2018-01-31 18:38:34 +03:00
%if ( 0%{!?_without_server:1} )
2014-02-28 09:40:51 +04:00
%preun server
if [ $1 -eq 0 ]; then
2017-10-04 21:22:05 +03:00
if [ -f %glusterfsd_svcfile ]; then
%service_stop glusterfsd
2014-02-28 09:40:51 +04:00
fi
2017-10-04 21:22:05 +03:00
%service_stop glusterd
if [ -f %glusterfsd_svcfile ]; then
%systemd_preun glusterfsd
2014-02-28 09:40:51 +04:00
fi
2017-10-04 21:22:05 +03:00
%systemd_preun glusterd
2014-02-28 09:40:51 +04:00
fi
if [ $1 -ge 1 ]; then
2017-10-04 21:22:05 +03:00
if [ -f %glusterfsd_svcfile ]; then
%systemd_postun_with_restart glusterfsd
2014-02-28 09:40:51 +04:00
fi
2017-10-04 21:22:05 +03:00
%systemd_postun_with_restart glusterd
2014-02-28 09:40:51 +04:00
fi
packaging: rpm scriptlet cleanup, handle -p /sbin/ldconfig
The RPM documention indicates that during an rpm install or erase, the
script(lets): %post, %preun, and %postun (and %pre, %build, %install,
etc.) are copied to a temp file, and then the temp file is run as a
(/bin/sh or bash) script.
Unfortunately the documentation is not clear about how rpmbuild and/or
rpm determine where the end of any scriptlet is when it is copied to
the file.
Most things in the glusterfs.spec work correctly as is. These are the
%preun, %post, and %postun scriptlets that are "closed" by a following
%preun, %post, and %postun, or poetentially another scriptlet, e.g.
%file.
The ones that don't work correctly (only one actually) are those where
there is a comment in the spec file before it is closed by another
scriptlet. Further complicating things is that the type of scriptlet
affects what rpm does and what `rpm -qp --scripts ...` shows.
The specific one that didn't work was the "%postun libs" scriptlet. It
is followed by a comment before being "closed" by the %files section (or
scriptlet). It can be written two ways: "%postun libs\n/sbin/ldconfig"
or "%postun libs -p /sbin/ldconfig" Either way it's written, `rpm -qp
--scripts glusterfs-libs...` will include the comment lines between the
%postun libs line and the following %files line.
But the way rpm executes these depends on how they're written. If
written as "%postun libs\n/sbin/ldconfig" rpm will simply run
/sbin/ldconfig with no command line options, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig" ], [ ]);
But when written as "%postun libs -p /sbin/ldconfig", it will copy
the comment lines to a temp file, and pass the temp file name and "1"
as (command line) parameters, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig", "/tmp/tmpXXXXXX", "1" ],
[ ]);
Which results in ldconfig exiting with an error. (Remember, both ways show
the comment in `rpm -qp --scripts ...`)
(Note though, that the similar "%postun api -p /sbin/ldconfig" is run
correctly, because it is "closed" by the following "%postun server"
scriptlet.)
Finally, through trial and error, it appears that rpm can be tricked with
a hack, and "closure" of the scriptlet forcedlike this:
%postun libs -p /sbin/ldconfig
%if ( 0%{?_undocumented_hack_closes_scriptlets} )
%postun
%endif
in which case ldconfig appears to run correctly. Note also that here too
the comment will be included in the output of `rpm -qp --scripts ...`
But that's very ugly hack.
Change-Id: I587a490ddcdf47d01605479bc8ef8b0e439108fb
BUG: 1315024
Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
Reviewed-on: http://review.gluster.org/13613
Smoke: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
2016-03-06 00:06:18 +03:00
exit 0
2018-01-31 18:38:34 +03:00
%endif
2014-02-28 09:40:51 +04:00
2019-01-30 11:54:14 +03:00
%preun thin-arbiter
if [ $1 -eq 0 ]; then
if [ -f %glusterta_svcfile ]; then
%service_stop gluster-ta-volume
%systemd_preun gluster-ta-volume
fi
fi
2014-02-28 09:40:51 +04:00
##-----------------------------------------------------------------------------
packaging: rpm scriptlet cleanup, handle -p /sbin/ldconfig
The RPM documention indicates that during an rpm install or erase, the
script(lets): %post, %preun, and %postun (and %pre, %build, %install,
etc.) are copied to a temp file, and then the temp file is run as a
(/bin/sh or bash) script.
Unfortunately the documentation is not clear about how rpmbuild and/or
rpm determine where the end of any scriptlet is when it is copied to
the file.
Most things in the glusterfs.spec work correctly as is. These are the
%preun, %post, and %postun scriptlets that are "closed" by a following
%preun, %post, and %postun, or poetentially another scriptlet, e.g.
%file.
The ones that don't work correctly (only one actually) are those where
there is a comment in the spec file before it is closed by another
scriptlet. Further complicating things is that the type of scriptlet
affects what rpm does and what `rpm -qp --scripts ...` shows.
The specific one that didn't work was the "%postun libs" scriptlet. It
is followed by a comment before being "closed" by the %files section (or
scriptlet). It can be written two ways: "%postun libs\n/sbin/ldconfig"
or "%postun libs -p /sbin/ldconfig" Either way it's written, `rpm -qp
--scripts glusterfs-libs...` will include the comment lines between the
%postun libs line and the following %files line.
But the way rpm executes these depends on how they're written. If
written as "%postun libs\n/sbin/ldconfig" rpm will simply run
/sbin/ldconfig with no command line options, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig" ], [ ]);
But when written as "%postun libs -p /sbin/ldconfig", it will copy
the comment lines to a temp file, and pass the temp file name and "1"
as (command line) parameters, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig", "/tmp/tmpXXXXXX", "1" ],
[ ]);
Which results in ldconfig exiting with an error. (Remember, both ways show
the comment in `rpm -qp --scripts ...`)
(Note though, that the similar "%postun api -p /sbin/ldconfig" is run
correctly, because it is "closed" by the following "%postun server"
scriptlet.)
Finally, through trial and error, it appears that rpm can be tricked with
a hack, and "closure" of the scriptlet forcedlike this:
%postun libs -p /sbin/ldconfig
%if ( 0%{?_undocumented_hack_closes_scriptlets} )
%postun
%endif
in which case ldconfig appears to run correctly. Note also that here too
the comment will be included in the output of `rpm -qp --scripts ...`
But that's very ugly hack.
Change-Id: I587a490ddcdf47d01605479bc8ef8b0e439108fb
BUG: 1315024
Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
Reviewed-on: http://review.gluster.org/13613
Smoke: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
2016-03-06 00:06:18 +03:00
## All %%postun should be placed here and keep them sorted
2014-02-28 09:40:51 +04:00
##
2011-11-10 06:27:25 +04:00
%postun
2013-10-18 09:36:59 +04:00
%if ( 0%{!?_without_syslog:1} )
%if ( 0%{?fedora} ) || ( 0%{?rhel} && 0%{?rhel} >= 6 )
2017-10-04 21:22:05 +03:00
%systemd_postun_with_restart rsyslog
2013-10-18 09:36:59 +04:00
%endif
%endif
2009-04-16 17:15:48 +04:00
2018-01-31 18:38:34 +03:00
%if ( 0%{!?_without_server:1} )
packaging: rpm scriptlet cleanup, handle -p /sbin/ldconfig
The RPM documention indicates that during an rpm install or erase, the
script(lets): %post, %preun, and %postun (and %pre, %build, %install,
etc.) are copied to a temp file, and then the temp file is run as a
(/bin/sh or bash) script.
Unfortunately the documentation is not clear about how rpmbuild and/or
rpm determine where the end of any scriptlet is when it is copied to
the file.
Most things in the glusterfs.spec work correctly as is. These are the
%preun, %post, and %postun scriptlets that are "closed" by a following
%preun, %post, and %postun, or poetentially another scriptlet, e.g.
%file.
The ones that don't work correctly (only one actually) are those where
there is a comment in the spec file before it is closed by another
scriptlet. Further complicating things is that the type of scriptlet
affects what rpm does and what `rpm -qp --scripts ...` shows.
The specific one that didn't work was the "%postun libs" scriptlet. It
is followed by a comment before being "closed" by the %files section (or
scriptlet). It can be written two ways: "%postun libs\n/sbin/ldconfig"
or "%postun libs -p /sbin/ldconfig" Either way it's written, `rpm -qp
--scripts glusterfs-libs...` will include the comment lines between the
%postun libs line and the following %files line.
But the way rpm executes these depends on how they're written. If
written as "%postun libs\n/sbin/ldconfig" rpm will simply run
/sbin/ldconfig with no command line options, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig" ], [ ]);
But when written as "%postun libs -p /sbin/ldconfig", it will copy
the comment lines to a temp file, and pass the temp file name and "1"
as (command line) parameters, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig", "/tmp/tmpXXXXXX", "1" ],
[ ]);
Which results in ldconfig exiting with an error. (Remember, both ways show
the comment in `rpm -qp --scripts ...`)
(Note though, that the similar "%postun api -p /sbin/ldconfig" is run
correctly, because it is "closed" by the following "%postun server"
scriptlet.)
Finally, through trial and error, it appears that rpm can be tricked with
a hack, and "closure" of the scriptlet forcedlike this:
%postun libs -p /sbin/ldconfig
%if ( 0%{?_undocumented_hack_closes_scriptlets} )
%postun
%endif
in which case ldconfig appears to run correctly. Note also that here too
the comment will be included in the output of `rpm -qp --scripts ...`
But that's very ugly hack.
Change-Id: I587a490ddcdf47d01605479bc8ef8b0e439108fb
BUG: 1315024
Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
Reviewed-on: http://review.gluster.org/13613
Smoke: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
2016-03-06 00:06:18 +03:00
%postun server
2016-04-26 17:10:05 +03:00
%if (0%{?_with_firewalld:1})
2017-01-06 19:16:38 +03:00
%firewalld_reload
2015-08-21 22:39:53 +03:00
%endif
2016-04-26 17:10:05 +03:00
exit 0
2018-01-31 18:38:34 +03:00
%endif
2015-08-21 22:39:53 +03:00
2014-02-28 09:40:51 +04:00
##-----------------------------------------------------------------------------
packaging: rpm scriptlet cleanup, handle -p /sbin/ldconfig
The RPM documention indicates that during an rpm install or erase, the
script(lets): %post, %preun, and %postun (and %pre, %build, %install,
etc.) are copied to a temp file, and then the temp file is run as a
(/bin/sh or bash) script.
Unfortunately the documentation is not clear about how rpmbuild and/or
rpm determine where the end of any scriptlet is when it is copied to
the file.
Most things in the glusterfs.spec work correctly as is. These are the
%preun, %post, and %postun scriptlets that are "closed" by a following
%preun, %post, and %postun, or poetentially another scriptlet, e.g.
%file.
The ones that don't work correctly (only one actually) are those where
there is a comment in the spec file before it is closed by another
scriptlet. Further complicating things is that the type of scriptlet
affects what rpm does and what `rpm -qp --scripts ...` shows.
The specific one that didn't work was the "%postun libs" scriptlet. It
is followed by a comment before being "closed" by the %files section (or
scriptlet). It can be written two ways: "%postun libs\n/sbin/ldconfig"
or "%postun libs -p /sbin/ldconfig" Either way it's written, `rpm -qp
--scripts glusterfs-libs...` will include the comment lines between the
%postun libs line and the following %files line.
But the way rpm executes these depends on how they're written. If
written as "%postun libs\n/sbin/ldconfig" rpm will simply run
/sbin/ldconfig with no command line options, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig" ], [ ]);
But when written as "%postun libs -p /sbin/ldconfig", it will copy
the comment lines to a temp file, and pass the temp file name and "1"
as (command line) parameters, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig", "/tmp/tmpXXXXXX", "1" ],
[ ]);
Which results in ldconfig exiting with an error. (Remember, both ways show
the comment in `rpm -qp --scripts ...`)
(Note though, that the similar "%postun api -p /sbin/ldconfig" is run
correctly, because it is "closed" by the following "%postun server"
scriptlet.)
Finally, through trial and error, it appears that rpm can be tricked with
a hack, and "closure" of the scriptlet forcedlike this:
%postun libs -p /sbin/ldconfig
%if ( 0%{?_undocumented_hack_closes_scriptlets} )
%postun
%endif
in which case ldconfig appears to run correctly. Note also that here too
the comment will be included in the output of `rpm -qp --scripts ...`
But that's very ugly hack.
Change-Id: I587a490ddcdf47d01605479bc8ef8b0e439108fb
BUG: 1315024
Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
Reviewed-on: http://review.gluster.org/13613
Smoke: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
2016-03-06 00:06:18 +03:00
## All %%files should be placed here and keep them grouped
2014-02-28 09:40:51 +04:00
##
2011-11-10 06:27:25 +04:00
%files
2018-04-16 11:19:44 +03:00
%doc ChangeLog COPYING-GPLV2 COPYING-LGPLV3 INSTALL README.md THANKS COMMITMENT
2011-11-10 06:27:25 +04:00
%{_mandir} /man8/*gluster*.8*
2018-01-31 18:38:34 +03:00
%if ( 0%{!?_without_server:1} )
2013-08-07 17:11:48 +04:00
%exclude %{_mandir} /man8/gluster.8*
2018-01-31 18:38:34 +03:00
%endif
2011-11-10 06:27:25 +04:00
%dir %{_localstatedir} /log/glusterfs
2013-06-17 21:44:10 +04:00
%if ( 0%{!?_without_rdma:1} )
%exclude %{_libdir} /glusterfs/%{version} %{?prereltag} /rpc-transport/rdma*
2010-09-22 08:23:45 +04:00
%endif
2018-01-31 18:38:34 +03:00
%if 0%{?!_without_server:1}
2017-07-13 18:35:50 +03:00
%dir %{_datadir} /glusterfs
2014-12-12 16:12:35 +03:00
%dir %{_datadir} /glusterfs/scripts
2017-07-13 18:35:50 +03:00
%{_datadir} /glusterfs/scripts/post-upgrade-script-for-quota.sh
%{_datadir} /glusterfs/scripts/pre-upgrade-script-for-quota.sh
2018-01-31 18:38:34 +03:00
%endif
2015-05-05 11:28:15 +03:00
# xlators that are needed on the client- and on the server-side
2017-07-13 18:35:50 +03:00
%dir %{_libdir} /glusterfs
%dir %{_libdir} /glusterfs/%{version} %{?prereltag}
2015-05-05 11:28:15 +03:00
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /auth
2017-07-13 18:35:50 +03:00
%{_libdir} /glusterfs/%{version} %{?prereltag} /auth/addr.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /auth/login.so
2015-05-05 11:28:15 +03:00
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /rpc-transport
2017-07-13 18:35:50 +03:00
%{_libdir} /glusterfs/%{version} %{?prereltag} /rpc-transport/socket.so
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator
2015-05-05 11:28:15 +03:00
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/debug
2017-07-13 18:35:50 +03:00
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/debug/error-gen.so
2017-06-20 12:54:33 +03:00
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/debug/delay-gen.so
2017-07-13 18:35:50 +03:00
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/debug/io-stats.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/debug/sink.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/debug/trace.so
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/access-control.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/barrier.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/cdc.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/changelog.so
2018-04-30 11:43:58 +03:00
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/utime.so
2017-07-13 18:35:50 +03:00
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/gfid-access.so
2018-02-12 08:07:15 +03:00
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/namespace.so
2017-07-13 18:35:50 +03:00
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/read-only.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/shard.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/snapview-client.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/worm.so
2018-03-09 17:37:19 +03:00
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/cloudsync.so
2017-07-13 18:35:50 +03:00
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/meta.so
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/performance
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/performance/io-cache.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/performance/io-threads.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/performance/md-cache.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/performance/open-behind.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/performance/quick-read.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/performance/read-ahead.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/performance/readdir-ahead.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/performance/stat-prefetch.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/performance/write-behind.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/performance/nl-cache.so
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/system
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/system/posix-acl.so
2017-08-10 20:13:39 +03:00
%dir %attr (0775,gluster,gluster) %{_rundir} /gluster
2018-01-31 18:38:34 +03:00
%if 0%{?_tmpfilesdir:1} && 0%{!?_without_server:1}
2016-01-27 10:29:58 +03:00
%{_tmpfilesdir} /gluster.conf
%endif
2015-05-05 11:28:15 +03:00
2014-02-28 09:40:51 +04:00
%files api
%exclude %{_libdir} /*.so
2014-04-25 18:14:14 +04:00
# libgfapi files
2014-02-28 09:40:51 +04:00
%{_libdir} /libgfapi.*
2017-07-13 18:35:50 +03:00
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/mount
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/mount/api.so
2013-07-30 22:00:46 +04:00
2014-02-28 09:40:51 +04:00
%files api-devel
%{_libdir} /pkgconfig/glusterfs-api.pc
%{_libdir} /libgfapi.so
2017-07-13 18:35:50 +03:00
%dir %{_includedir} /glusterfs
%dir %{_includedir} /glusterfs/api
%{_includedir} /glusterfs/api/*
2013-01-30 20:29:54 +04:00
2018-01-31 18:38:34 +03:00
%if ( 0%{!?_without_server:1} )
2013-08-07 17:11:48 +04:00
%files cli
%{_sbindir} /gluster
%{_mandir} /man8/gluster.8*
2014-06-04 13:31:14 +04:00
%{_sysconfdir} /bash_completion.d/gluster
2018-01-31 18:38:34 +03:00
%endif
2013-08-07 17:11:48 +04:00
2018-09-10 16:02:33 +03:00
%files cloudsync-plugins
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /cloudsync-plugins
%{_libdir} /glusterfs/%{version} %{?prereltag} /cloudsync-plugins/cloudsyncs3.so
2014-02-28 09:40:51 +04:00
%files devel
2015-10-14 18:13:50 +03:00
%dir %{_includedir} /glusterfs
2017-07-13 18:35:50 +03:00
%{_includedir} /glusterfs/*
2014-02-28 09:40:51 +04:00
%exclude %{_includedir} /glusterfs/api
%exclude %{_libdir} /libgfapi.so
%{_libdir} /*.so
2015-05-20 16:10:38 +03:00
%{_libdir} /pkgconfig/libgfchangelog.pc
2014-02-28 09:40:51 +04:00
2015-05-05 11:28:15 +03:00
%files client-xlators
2017-07-13 18:35:50 +03:00
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/cluster
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/cluster/*.so
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/protocol
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/protocol/client.so
2015-05-05 11:28:15 +03:00
2014-02-28 09:40:51 +04:00
%files extra-xlators
2017-07-13 18:35:50 +03:00
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/quiesce.so
2018-06-29 21:10:53 +03:00
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/playground
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/playground/template.so
2010-08-16 11:26:33 +04:00
2014-02-28 09:40:51 +04:00
%files fuse
2015-05-05 11:28:15 +03:00
# glusterfs is a symlink to glusterfsd, -server depends on -fuse.
%{_sbindir} /glusterfs
%{_sbindir} /glusterfsd
%config (noreplace) %{_sysconfdir} /logrotate.d/glusterfs
2017-07-13 18:35:50 +03:00
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/mount
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/mount/fuse.so
2014-02-28 09:40:51 +04:00
/sbin/mount.glusterfs
%if ( 0%{!?_without_fusermount:1} )
%{_bindir} /fusermount-glusterfs
%endif
2011-06-06 08:11:19 +04:00
2018-01-31 18:38:34 +03:00
%if ( 0%{?_with_gnfs:1} && 0%{!?_without_server:1} )
2017-03-27 23:09:56 +03:00
%files gnfs
2017-07-13 18:35:50 +03:00
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator
2017-03-27 23:09:56 +03:00
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/nfs
2017-07-13 18:35:50 +03:00
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/nfs/server.so
2017-03-27 23:09:56 +03:00
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/nfs
%ghost %attr (0600,-,-) %{_sharedstatedir} /glusterd/nfs/nfs-server.vol
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/nfs/run
%ghost %attr (0600,-,-) %{_sharedstatedir} /glusterd/nfs/run/nfs.pid
%endif
2019-01-30 11:54:14 +03:00
%files thin-arbiter
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/thin-arbiter.so
%dir %{_datadir} /glusterfs/scripts
%{_datadir} /glusterfs/scripts/setup-thin-arbiter.sh
%config %{_sysconfdir} /glusterfs/thin-arbiter.vol
%if ( 0%{?_with_systemd:1} )
%{_unitdir} /gluster-ta-volume.service
%endif
2014-02-28 09:40:51 +04:00
%if ( 0%{!?_without_georeplication:1} )
2011-04-15 09:08:47 +04:00
%files geo-replication
2014-08-05 16:29:42 +04:00
%config (noreplace) %{_sysconfdir} /logrotate.d/glusterfs-georep
2016-04-12 18:35:38 +03:00
%{_sbindir} /gfind_missing_files
geo-rep: Simplify Non root user(mountbroker) Setup
Setting up Non root Geo-replication is troublesome. Lot of steps
involved like user setup, directory creation, setting up proper
permissions, editing glusterd.vol file etc.
Introducing `gluster-mountbroker` command, with this tool non root
user setup steps are(Run the following commands in any one Slave
node),
gluster-mountbroker setup <MOUNT ROOT> <GROUP>
For example,
gluster-mountbroker setup /var/mountbroker-root geogroup
Add user using,
gluster-mountbroker add <VOLUME> <USER>
For example,
gluster-mountbroker add slavevol geoaccount
Remove user or Volume using,
gluster-mountbroker remove [--volume <VOLUME>] [--user <USER>]
Example,
gluster-mountbroker remove --volume slavevol --user geoaccount
gluster-mountbroker remove --user geoaccount
gluster-mountbroker remove --volume slavevol
Check the status of setup using,
gluster-mountbroker status
Once the changes are complete, restart glusterd in all Slave nodes.
and follow the Geo-rep instructions.
Change-Id: Ied3fa009df6a886b24ddd86d39283fcfcff68c82
BUG: 1343333
Signed-off-by: Aravinda VK <avishwan@redhat.com>
Reviewed-on: http://review.gluster.org/14544
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
Smoke: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Kotresh HR <khiremat@redhat.com>
2016-05-26 13:22:53 +03:00
%{_sbindir} /gluster-mountbroker
2017-07-13 18:35:50 +03:00
%dir %{_libexecdir} /glusterfs
%dir %{_libexecdir} /glusterfs/python
%dir %{_libexecdir} /glusterfs/python/syncdaemon
%{_libexecdir} /glusterfs/gsyncd
%{_libexecdir} /glusterfs/python/syncdaemon/*
%{_libexecdir} /glusterfs/gverify.sh
%{_libexecdir} /glusterfs/set_geo_rep_pem_keys.sh
%{_libexecdir} /glusterfs/peer_gsec_create
%{_libexecdir} /glusterfs/peer_mountbroker
%{_libexecdir} /glusterfs/peer_mountbroker.py*
%{_libexecdir} /glusterfs/gfind_missing_files
%{_libexecdir} /glusterfs/peer_georep-sshkey.py*
2016-06-15 11:24:37 +03:00
%{_sbindir} /gluster-georep-sshkey
2016-04-12 18:35:38 +03:00
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/geo-replication
%ghost %attr (0644,-,-) %{_sharedstatedir} /glusterd/geo-replication/gsyncd_template.conf
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/gsync-create
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/gsync-create/post
%attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/gsync-create/post/S56glusterd-geo-rep-create-post.sh
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/gsync-create/pre
2017-07-13 18:35:50 +03:00
%dir %{_datadir} /glusterfs
%dir %{_datadir} /glusterfs/scripts
%{_datadir} /glusterfs/scripts/get-gfid.sh
%{_datadir} /glusterfs/scripts/slave-upgrade.sh
%{_datadir} /glusterfs/scripts/gsync-upgrade.sh
%{_datadir} /glusterfs/scripts/generate-gfid-file.sh
%{_datadir} /glusterfs/scripts/gsync-sync-gfid
%{_datadir} /glusterfs/scripts/schedule_georep.py*
2015-11-13 20:55:17 +03:00
%endif
2011-04-15 09:08:47 +04:00
2014-02-28 09:40:51 +04:00
%files libs
%{_libdir} /*.so.*
%exclude %{_libdir} /libgfapi.*
2014-02-06 15:46:20 +04:00
core: python3
see https://review.gluster.org/#/c/19788/,
https://review.gluster.org/#/c/19871/,
https://review.gluster.org/#/c/19952/,
https://review.gluster.org/#/c/20104/,
https://review.gluster.org/#/c/20162/,
https://review.gluster.org/#/c/20185/,
https://review.gluster.org/#/c/20207/,
https://review.gluster.org/#/c/20227/,
https://review.gluster.org/#/c/20307/,
https://review.gluster.org/#/c/20320/,
https://review.gluster.org/#/c/20332/,
https://review.gluster.org/#/c/20364/,
https://review.gluster.org/#/c/20441/, and
https://review.gluster.org/#/c/20484
shebangs changed from /usr/bin/python2 to /usr/bin/python3.
(Reminder, various distribution packaging guidelines require use
of explicit python version and don't allow '#!/usr/bin/env python',
regardless of how handy that idiom may be.)
glusterfs.spec(.in) package python{2,3}-gluster and python2 or
python3 dependencies as appropriate.
configure(.ac):
+ test for and use python2 or python3 as appropriate. If build
machine has python2 and python3, use python3. Override by
setting PYTHON=/usr/bin/python2 when running configure.
+ PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
better match to the original python sysconfig.get_python_inc().
All those other extraneous flags breaks the build.
+ Only change the shebangs once. Changing them over and over
again, e.g., during a `make glusterrpms` in extras/LinuxRPM
just sends make (is it really make that's looping?) into an
infinite loop. If you figure out why, let me know.
+ Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
Everything else has 2.7 or 3.x
+ logic from https://review.gluster.org/c/glusterfs/+/21050, which
needs to be removed/merged after that patch is merged.
Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
mysterious RHEL > 7.
Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
updates: #411
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
2018-08-29 18:09:27 +03:00
%files -n python%{_pythonver}-gluster
2015-04-15 09:59:16 +03:00
# introducing glusterfs module in site packages.
# so that all other gluster submodules can reside in the same namespace.
core: python3
see https://review.gluster.org/#/c/19788/,
https://review.gluster.org/#/c/19871/,
https://review.gluster.org/#/c/19952/,
https://review.gluster.org/#/c/20104/,
https://review.gluster.org/#/c/20162/,
https://review.gluster.org/#/c/20185/,
https://review.gluster.org/#/c/20207/,
https://review.gluster.org/#/c/20227/,
https://review.gluster.org/#/c/20307/,
https://review.gluster.org/#/c/20320/,
https://review.gluster.org/#/c/20332/,
https://review.gluster.org/#/c/20364/,
https://review.gluster.org/#/c/20441/, and
https://review.gluster.org/#/c/20484
shebangs changed from /usr/bin/python2 to /usr/bin/python3.
(Reminder, various distribution packaging guidelines require use
of explicit python version and don't allow '#!/usr/bin/env python',
regardless of how handy that idiom may be.)
glusterfs.spec(.in) package python{2,3}-gluster and python2 or
python3 dependencies as appropriate.
configure(.ac):
+ test for and use python2 or python3 as appropriate. If build
machine has python2 and python3, use python3. Override by
setting PYTHON=/usr/bin/python2 when running configure.
+ PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
better match to the original python sysconfig.get_python_inc().
All those other extraneous flags breaks the build.
+ Only change the shebangs once. Changing them over and over
again, e.g., during a `make glusterrpms` in extras/LinuxRPM
just sends make (is it really make that's looping?) into an
infinite loop. If you figure out why, let me know.
+ Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
Everything else has 2.7 or 3.x
+ logic from https://review.gluster.org/c/glusterfs/+/21050, which
needs to be removed/merged after that patch is merged.
Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
mysterious RHEL > 7.
Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
updates: #411
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
2018-08-29 18:09:27 +03:00
%if ( %{_usepython3} )
%dir %{python3_sitelib} /gluster
2019-02-22 17:17:48 +03:00
%{python3_sitelib} /gluster/__init__.*
%{python3_sitelib} /gluster/__pycache__
core: python3
see https://review.gluster.org/#/c/19788/,
https://review.gluster.org/#/c/19871/,
https://review.gluster.org/#/c/19952/,
https://review.gluster.org/#/c/20104/,
https://review.gluster.org/#/c/20162/,
https://review.gluster.org/#/c/20185/,
https://review.gluster.org/#/c/20207/,
https://review.gluster.org/#/c/20227/,
https://review.gluster.org/#/c/20307/,
https://review.gluster.org/#/c/20320/,
https://review.gluster.org/#/c/20332/,
https://review.gluster.org/#/c/20364/,
https://review.gluster.org/#/c/20441/, and
https://review.gluster.org/#/c/20484
shebangs changed from /usr/bin/python2 to /usr/bin/python3.
(Reminder, various distribution packaging guidelines require use
of explicit python version and don't allow '#!/usr/bin/env python',
regardless of how handy that idiom may be.)
glusterfs.spec(.in) package python{2,3}-gluster and python2 or
python3 dependencies as appropriate.
configure(.ac):
+ test for and use python2 or python3 as appropriate. If build
machine has python2 and python3, use python3. Override by
setting PYTHON=/usr/bin/python2 when running configure.
+ PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
better match to the original python sysconfig.get_python_inc().
All those other extraneous flags breaks the build.
+ Only change the shebangs once. Changing them over and over
again, e.g., during a `make glusterrpms` in extras/LinuxRPM
just sends make (is it really make that's looping?) into an
infinite loop. If you figure out why, let me know.
+ Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
Everything else has 2.7 or 3.x
+ logic from https://review.gluster.org/c/glusterfs/+/21050, which
needs to be removed/merged after that patch is merged.
Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
mysterious RHEL > 7.
Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
updates: #411
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
2018-08-29 18:09:27 +03:00
%{python3_sitelib} /gluster/cliutils
%else
2017-07-13 18:35:50 +03:00
%dir %{python2_sitelib} /gluster
2019-02-22 17:17:48 +03:00
%{python2_sitelib} /gluster/__init__.*
2017-07-13 18:35:50 +03:00
%{python2_sitelib} /gluster/cliutils
core: python3
see https://review.gluster.org/#/c/19788/,
https://review.gluster.org/#/c/19871/,
https://review.gluster.org/#/c/19952/,
https://review.gluster.org/#/c/20104/,
https://review.gluster.org/#/c/20162/,
https://review.gluster.org/#/c/20185/,
https://review.gluster.org/#/c/20207/,
https://review.gluster.org/#/c/20227/,
https://review.gluster.org/#/c/20307/,
https://review.gluster.org/#/c/20320/,
https://review.gluster.org/#/c/20332/,
https://review.gluster.org/#/c/20364/,
https://review.gluster.org/#/c/20441/, and
https://review.gluster.org/#/c/20484
shebangs changed from /usr/bin/python2 to /usr/bin/python3.
(Reminder, various distribution packaging guidelines require use
of explicit python version and don't allow '#!/usr/bin/env python',
regardless of how handy that idiom may be.)
glusterfs.spec(.in) package python{2,3}-gluster and python2 or
python3 dependencies as appropriate.
configure(.ac):
+ test for and use python2 or python3 as appropriate. If build
machine has python2 and python3, use python3. Override by
setting PYTHON=/usr/bin/python2 when running configure.
+ PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
better match to the original python sysconfig.get_python_inc().
All those other extraneous flags breaks the build.
+ Only change the shebangs once. Changing them over and over
again, e.g., during a `make glusterrpms` in extras/LinuxRPM
just sends make (is it really make that's looping?) into an
infinite loop. If you figure out why, let me know.
+ Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
Everything else has 2.7 or 3.x
+ logic from https://review.gluster.org/c/glusterfs/+/21050, which
needs to be removed/merged after that patch is merged.
Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
mysterious RHEL > 7.
Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
updates: #411
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
2018-08-29 18:09:27 +03:00
%endif
2015-04-15 09:59:16 +03:00
2014-02-28 09:40:51 +04:00
%if ( 0%{!?_without_rdma:1} )
%files rdma
2017-07-13 18:35:50 +03:00
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /rpc-transport
%{_libdir} /glusterfs/%{version} %{?prereltag} /rpc-transport/rdma*
2013-05-22 18:20:36 +04:00
%endif
2014-02-28 09:40:51 +04:00
%files regression-tests
2017-07-13 18:35:50 +03:00
%dir %{_datadir} /glusterfs
%{_datadir} /glusterfs/run-tests.sh
%{_datadir} /glusterfs/tests
2016-12-01 12:35:06 +03:00
%exclude %{_datadir} /glusterfs/tests/vagrant
2014-02-28 09:40:51 +04:00
%if ( 0%{!?_without_ocf:1} )
%files resource-agents
# /usr/lib is the standard for OCF, also on x86_64
%{_prefix} /lib/ocf/resource.d/glusterfs
2013-06-17 21:44:10 +04:00
%endif
2011-11-10 06:27:25 +04:00
2018-01-31 18:38:34 +03:00
%if ( 0%{!?_without_server:1} )
2011-11-10 06:27:25 +04:00
%files server
2014-04-25 18:14:14 +04:00
%doc extras/clear_xattrs.sh
2016-04-12 18:35:38 +03:00
# sysconf
2013-01-30 20:29:54 +04:00
%config (noreplace) %{_sysconfdir} /glusterfs
2019-01-30 11:54:14 +03:00
%exclude %{_sysconfdir} /glusterfs/thin-arbiter.vol
2016-09-13 13:08:24 +03:00
%exclude %{_sysconfdir} /glusterfs/eventsconfig.json
2017-03-27 23:09:56 +03:00
%exclude %{_sharedstatedir} /glusterd/nfs/nfs-server.vol
%exclude %{_sharedstatedir} /glusterd/nfs/run/nfs.pid
%if ( 0%{?_with_gnfs:1} )
%exclude %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/nfs/*
%endif
2016-04-12 18:35:38 +03:00
%config (noreplace) %{_sysconfdir} /sysconfig/glusterd
2013-06-17 21:44:10 +04:00
%if ( 0%{_for_fedora_koji_builds} )
2013-01-30 20:29:54 +04:00
%config (noreplace) %{_sysconfdir} /sysconfig/glusterfsd
%endif
2016-04-12 18:35:38 +03:00
2013-01-30 20:29:54 +04:00
# init files
2017-10-04 21:22:05 +03:00
%glusterd_svcfile
2013-10-09 16:29:18 +04:00
%if ( 0%{_for_fedora_koji_builds} )
2017-10-04 21:22:05 +03:00
%glusterfsd_svcfile
2013-01-30 20:29:54 +04:00
%endif
2017-05-19 09:51:37 +03:00
%if ( 0%{?_with_systemd:1} )
2017-10-04 21:22:05 +03:00
%glusterfssharedstorage_svcfile
2017-05-19 09:51:37 +03:00
%endif
2016-04-12 18:35:38 +03:00
2013-01-30 20:29:54 +04:00
# binaries
2011-11-10 06:27:25 +04:00
%{_sbindir} /glusterd
2013-12-15 06:35:04 +04:00
%{_sbindir} /glfsheal
2017-02-17 10:07:27 +03:00
%{_sbindir} /gf_attach
2017-07-20 14:38:12 +03:00
%{_sbindir} /gluster-setgfid2path
2015-05-05 11:28:15 +03:00
# {_sbindir}/glusterfsd is the actual binary, but glusterfs (client) is a
# symlink. The binary itself (and symlink) are part of the glusterfs-fuse
# package, because glusterfs-server depends on that anyway.
2017-07-13 18:35:50 +03:00
2017-07-20 14:38:12 +03:00
# Manpages
%{_mandir} /man8/gluster-setgfid2path.8*
2017-07-13 18:35:50 +03:00
# xlators
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/arbiter.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/bit-rot.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/bitrot-stub.so
dentry fop serializer: added new server side xlator for dentry fop serialization
Problems addressed by this xlator :
[1]. To prevent race between parallel mkdir,mkdir and lookup etc.
Fops like mkdir/create, lookup, rename, unlink, link that happen on a
particular dentry must be serialized to ensure atomicity.
Another possible case can be a fresh lookup to find existance of a path
whose gfid is not set yet. Further, storage/posix employs a ctime based
heuristic 'is_fresh_file' (interval time is less than 1 second of current
time) to check fresh-ness of file. With serialization of these two fops
(lookup & mkdir), we eliminate the race altogether.
[2]. Staleness of dentries
This causes exponential increase in traversal time for any inode in the
subtree of the directory pointed by stale dentry.
Cause : Stale dentry is created because of following two operations:
a. dentry creation due to inode_link, done during operations like
lookup, mkdir, create, mknod, symlink, create and
b. dentry unlinking due to various operations like rmdir, rename,
unlink.
The reason is __inode_link uses __is_dentry_cyclic, which explores
all possible path to avoid cyclic link formation during inode
linkage. __is_dentry_cyclic explores stale-dentry(ies) and its
all ancestors which is increases traversing time exponentially.
Implementation : To acheive this all fops on dentry must take entry locks
before they proceed, once they have acquired locks, they perform the fop
and then release the lock.
Some documentation from email conversation:
[1] http://www.gluster.org/pipermail/gluster-devel/2015-December/047314.html
[2] http://www.gluster.org/pipermail/gluster-devel/2015-August/046428.html
With this patch, the feature is optional, enable it by running:
`gluster volume set $volname features.sdfs enable`
Also the feature is tested for a month without issues in the
experiemental branch for all the regression.
Change-Id: I6e80ba3cabfa6facd5dda63bd482b9bf18b6b79b
Fixes: #397
BUG: 1304962
Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
Signed-off-by: Amar Tumballi <amarts@redhat.com>
Signed-off-by: Sunny Kumar <sunkumar@redhat.com>
2018-01-22 12:08:17 +03:00
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/sdfs.so
2017-07-13 18:35:50 +03:00
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/index.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/locks.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/posix*
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/snapview-server.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/marker.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/quota*
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/selinux.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/trash.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/upcall.so
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/features/leases.so
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/mgmt
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/mgmt/glusterd.so
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/protocol
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/protocol/server.so
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/storage
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/storage/posix.so
%dir %{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/performance
%{_libdir} /glusterfs/%{version} %{?prereltag} /xlator/performance/decompounder.so
2015-03-19 15:12:02 +03:00
2016-04-12 18:35:38 +03:00
# snap_scheduler
2015-03-19 15:12:02 +03:00
%{_sbindir} /snap_scheduler.py
%{_sbindir} /gcron.py
2016-08-26 11:35:07 +03:00
%{_sbindir} /conf.py
2015-03-19 15:12:02 +03:00
2016-04-12 18:35:38 +03:00
# /var/lib/glusterd, e.g. hookscripts, etc.
%ghost %attr (0644,-,-) %config (noreplace) %{_sharedstatedir} /glusterd/glusterd.info
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/bitd
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/groups
%attr (0644,-,-) %{_sharedstatedir} /glusterd/groups/virt
2017-02-01 14:41:46 +03:00
%attr (0644,-,-) %{_sharedstatedir} /glusterd/groups/metadata-cache
2017-05-10 13:56:35 +03:00
%attr (0644,-,-) %{_sharedstatedir} /glusterd/groups/gluster-block
2017-06-09 09:01:19 +03:00
%attr (0644,-,-) %{_sharedstatedir} /glusterd/groups/nl-cache
2018-06-28 08:12:56 +03:00
%attr (0644,-,-) %{_sharedstatedir} /glusterd/groups/db-workload
2018-11-28 10:09:31 +03:00
%attr (0644,-,-) %{_sharedstatedir} /glusterd/groups/distributed-virt
2018-12-06 12:35:20 +03:00
%attr (0644,-,-) %{_sharedstatedir} /glusterd/groups/samba
2016-04-12 18:35:38 +03:00
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/glusterfind
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/glusterfind/.keys
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/glustershd
2016-05-11 14:23:10 +03:00
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1
2016-04-12 18:35:38 +03:00
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/add-brick
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/add-brick/post
%attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/add-brick/post/disabled-quota-root-xattr-heal.sh
2017-11-03 09:19:42 +03:00
%attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/add-brick/post/S13create-subdir-mounts.sh
2016-04-12 18:35:38 +03:00
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/add-brick/pre
2017-11-03 09:19:42 +03:00
%attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/add-brick/pre/S28Quota-enable-root-xattr-heal.sh
2014-01-02 23:03:18 +04:00
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/create
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/create/post
%attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/create/post/S10selinux-label-brick.sh
2012-06-08 13:59:31 +04:00
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/create/pre
2016-04-12 18:35:38 +03:00
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/copy-file
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/copy-file/post
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/copy-file/pre
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/delete
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/delete/post
2016-07-15 10:45:21 +03:00
%{_sharedstatedir} /glusterd/hooks/1/delete/post/S57glusterfind-delete-post
2014-01-02 23:03:18 +04:00
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/delete/pre
%attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/delete/pre/S10selinux-del-fcontext.sh
2015-12-23 15:57:14 +03:00
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/remove-brick
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/remove-brick/post
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/remove-brick/pre
2016-04-12 18:35:38 +03:00
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/reset
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/reset/post
2015-12-23 15:57:14 +03:00
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/reset/pre
2016-04-12 18:35:38 +03:00
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/set
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/set/post
%attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/set/post/S30samba-set.sh
%attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/set/post/S32gluster_enable_shared_storage.sh
2015-12-23 15:57:14 +03:00
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/set/pre
2016-04-12 18:35:38 +03:00
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/start
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/start/post
%attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/start/post/S29CTDBsetup.sh
%attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/start/post/S30samba-start.sh
2015-12-23 15:57:14 +03:00
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/start/pre
2016-04-12 18:35:38 +03:00
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/stop
2015-12-23 15:57:14 +03:00
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/stop/post
2016-04-12 18:35:38 +03:00
%dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/stop/pre
%attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/stop/pre/S30samba-stop.sh
%attr (0755,-,-) %{_sharedstatedir} /glusterd/hooks/1/stop/pre/S29CTDB-teardown.sh
2017-07-31 19:22:46 +03:00
%config (noreplace) %ghost %attr (0600,-,-) %{_sharedstatedir} /glusterd/options
2016-04-12 18:35:38 +03:00
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/peers
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/quotad
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/scrub
2016-05-11 14:23:10 +03:00
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/snaps
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/ss_brick
2016-04-12 18:35:38 +03:00
%ghost %dir %attr (0755,-,-) %{_sharedstatedir} /glusterd/vols
2011-11-10 06:27:25 +04:00
2015-05-27 09:26:53 +03:00
# Extra utility script
2017-07-13 18:35:50 +03:00
%dir %{_libexecdir} /glusterfs
%dir %{_datadir} /glusterfs/scripts
%{_datadir} /glusterfs/scripts/stop-all-gluster-processes.sh
2017-05-19 09:51:37 +03:00
%if ( 0%{?_with_systemd:1} )
2017-07-13 18:35:50 +03:00
%{_libexecdir} /glusterfs/mount-shared-storage.sh
2017-09-27 09:07:28 +03:00
%{_datadir} /glusterfs/scripts/control-cpu-load.sh
%{_datadir} /glusterfs/scripts/control-mem.sh
2017-05-19 09:51:37 +03:00
%endif
2015-05-27 09:26:53 +03:00
2015-02-18 16:37:23 +03:00
# Incrementalapi
2017-07-13 18:35:50 +03:00
%{_libexecdir} /glusterfs/glusterfind
2015-02-18 16:37:23 +03:00
%{_bindir} /glusterfind
2017-07-13 18:35:50 +03:00
%{_libexecdir} /glusterfs/peer_add_secret_pub
2015-02-18 16:37:23 +03:00
2015-08-21 22:39:53 +03:00
%if ( 0%{?_with_firewalld:1} )
2016-06-28 21:48:14 +03:00
%{_prefix} /lib/firewalld/services/glusterfs.xml
2015-08-21 22:39:53 +03:00
%endif
2018-01-31 18:38:34 +03:00
# end of server files
%endif
2015-02-18 16:37:23 +03:00
eventsapi: Gluster Eventing Feature implementation
[Depends on http://review.gluster.org/14627]
Design is available in `glusterfs-specs`, A change from the design
is support of webhook instead of Websockets as discussed in the design
http://review.gluster.org/13115
Since Websocket support depends on REST APIs, I will add Websocket support
once REST APIs patch gets merged
Usage:
Run following command to start/stop Eventsapi server in all Peers,
which will collect the notifications from any Gluster daemon and emits
to configured client.
gluster-eventsapi start|stop|restart|reload
Status of running services can be checked using,
gluster-eventsapi status
Events listener is a HTTP(S) server which listens to events emited by
the Gluster. Create a HTTP Server to listen on POST and register that
URL using,
gluster-eventsapi webhook-add <URL> [--bearer-token <TOKEN>]
For example, if HTTP Server running in `http://192.168.122.188:9000`
then add that URL using,
gluster-eventsapi webhook-add http://192.168.122.188:9000
If it expects a Token then specify it using `--bearer-token` or `-t`
We can also test Webhook if all peer nodes can send message or not
using,
gluster-eventsapi webhook-test <URL> [--bearer-token <TOKEN>]
Configurations can be viewed/updated using,
gluster-eventsapi config-get [--name]
gluster-eventsapi config-set <NAME> <VALUE>
gluster-eventsapi config-reset <NAME|all>
If any one peer node was down during config-set/reset or webhook
modifications, Run sync command from good node when a peer node comes
back. Automatic update is not yet implemented.
gluster-eventsapi sync
Basic Events Client(HTTP Server) is included with the code, Start
running the client with required port and start listening to the
events.
/usr/share/glusterfs/scripts/eventsdash.py --port 8080
Default port is 9000, if no port is specified, once it started running
then configure gluster-eventsapi to send events to that client.
Eventsapi Client can be outside of the Cluster, it can be run event on
Windows. But only requirement is the client URL should be accessible
by all peer nodes.(Or ngrok(https://ngrok.com) like tools can be used)
Events implemented with this patch,
- Volume Create
- Volume Start
- Volume Stop
- Volume Delete
- Peer Attach
- Peer Detach
It is easy to add/support more events, since it touches Gluster cmd
code and to avoid merge conflicts I will add support for more events
once this patch merges.
BUG: 1334044
Change-Id: I316827ac9dd1443454df7deffe4f54835f7f6a08
Signed-off-by: Aravinda VK <avishwan@redhat.com>
Reviewed-on: http://review.gluster.org/14248
Smoke: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
2016-05-05 16:04:41 +03:00
# Events
%if ( 0%{!?_without_events:1} )
%files events
2016-09-13 13:08:24 +03:00
%config (noreplace) %{_sysconfdir} /glusterfs/eventsconfig.json
2017-07-13 18:35:50 +03:00
%dir %{_sharedstatedir} /glusterd
%dir %{_sharedstatedir} /glusterd/events
%dir %{_libexecdir} /glusterfs
2019-02-21 08:55:55 +03:00
%{_libexecdir} /glusterfs/gfevents
2017-07-13 18:35:50 +03:00
%{_libexecdir} /glusterfs/peer_eventsapi.py*
eventsapi: Gluster Eventing Feature implementation
[Depends on http://review.gluster.org/14627]
Design is available in `glusterfs-specs`, A change from the design
is support of webhook instead of Websockets as discussed in the design
http://review.gluster.org/13115
Since Websocket support depends on REST APIs, I will add Websocket support
once REST APIs patch gets merged
Usage:
Run following command to start/stop Eventsapi server in all Peers,
which will collect the notifications from any Gluster daemon and emits
to configured client.
gluster-eventsapi start|stop|restart|reload
Status of running services can be checked using,
gluster-eventsapi status
Events listener is a HTTP(S) server which listens to events emited by
the Gluster. Create a HTTP Server to listen on POST and register that
URL using,
gluster-eventsapi webhook-add <URL> [--bearer-token <TOKEN>]
For example, if HTTP Server running in `http://192.168.122.188:9000`
then add that URL using,
gluster-eventsapi webhook-add http://192.168.122.188:9000
If it expects a Token then specify it using `--bearer-token` or `-t`
We can also test Webhook if all peer nodes can send message or not
using,
gluster-eventsapi webhook-test <URL> [--bearer-token <TOKEN>]
Configurations can be viewed/updated using,
gluster-eventsapi config-get [--name]
gluster-eventsapi config-set <NAME> <VALUE>
gluster-eventsapi config-reset <NAME|all>
If any one peer node was down during config-set/reset or webhook
modifications, Run sync command from good node when a peer node comes
back. Automatic update is not yet implemented.
gluster-eventsapi sync
Basic Events Client(HTTP Server) is included with the code, Start
running the client with required port and start listening to the
events.
/usr/share/glusterfs/scripts/eventsdash.py --port 8080
Default port is 9000, if no port is specified, once it started running
then configure gluster-eventsapi to send events to that client.
Eventsapi Client can be outside of the Cluster, it can be run event on
Windows. But only requirement is the client URL should be accessible
by all peer nodes.(Or ngrok(https://ngrok.com) like tools can be used)
Events implemented with this patch,
- Volume Create
- Volume Start
- Volume Stop
- Volume Delete
- Peer Attach
- Peer Detach
It is easy to add/support more events, since it touches Gluster cmd
code and to avoid merge conflicts I will add support for more events
once this patch merges.
BUG: 1334044
Change-Id: I316827ac9dd1443454df7deffe4f54835f7f6a08
Signed-off-by: Aravinda VK <avishwan@redhat.com>
Reviewed-on: http://review.gluster.org/14248
Smoke: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
2016-05-05 16:04:41 +03:00
%{_sbindir} /glustereventsd
%{_sbindir} /gluster-eventsapi
%{_datadir} /glusterfs/scripts/eventsdash.py*
%if ( 0%{?_with_systemd:1} )
%{_unitdir} /glustereventsd.service
2016-08-31 06:03:44 +03:00
%else
%{_sysconfdir} /init.d/glustereventsd
eventsapi: Gluster Eventing Feature implementation
[Depends on http://review.gluster.org/14627]
Design is available in `glusterfs-specs`, A change from the design
is support of webhook instead of Websockets as discussed in the design
http://review.gluster.org/13115
Since Websocket support depends on REST APIs, I will add Websocket support
once REST APIs patch gets merged
Usage:
Run following command to start/stop Eventsapi server in all Peers,
which will collect the notifications from any Gluster daemon and emits
to configured client.
gluster-eventsapi start|stop|restart|reload
Status of running services can be checked using,
gluster-eventsapi status
Events listener is a HTTP(S) server which listens to events emited by
the Gluster. Create a HTTP Server to listen on POST and register that
URL using,
gluster-eventsapi webhook-add <URL> [--bearer-token <TOKEN>]
For example, if HTTP Server running in `http://192.168.122.188:9000`
then add that URL using,
gluster-eventsapi webhook-add http://192.168.122.188:9000
If it expects a Token then specify it using `--bearer-token` or `-t`
We can also test Webhook if all peer nodes can send message or not
using,
gluster-eventsapi webhook-test <URL> [--bearer-token <TOKEN>]
Configurations can be viewed/updated using,
gluster-eventsapi config-get [--name]
gluster-eventsapi config-set <NAME> <VALUE>
gluster-eventsapi config-reset <NAME|all>
If any one peer node was down during config-set/reset or webhook
modifications, Run sync command from good node when a peer node comes
back. Automatic update is not yet implemented.
gluster-eventsapi sync
Basic Events Client(HTTP Server) is included with the code, Start
running the client with required port and start listening to the
events.
/usr/share/glusterfs/scripts/eventsdash.py --port 8080
Default port is 9000, if no port is specified, once it started running
then configure gluster-eventsapi to send events to that client.
Eventsapi Client can be outside of the Cluster, it can be run event on
Windows. But only requirement is the client URL should be accessible
by all peer nodes.(Or ngrok(https://ngrok.com) like tools can be used)
Events implemented with this patch,
- Volume Create
- Volume Start
- Volume Stop
- Volume Delete
- Peer Attach
- Peer Detach
It is easy to add/support more events, since it touches Gluster cmd
code and to avoid merge conflicts I will add support for more events
once this patch merges.
BUG: 1334044
Change-Id: I316827ac9dd1443454df7deffe4f54835f7f6a08
Signed-off-by: Aravinda VK <avishwan@redhat.com>
Reviewed-on: http://review.gluster.org/14248
Smoke: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
2016-05-05 16:04:41 +03:00
%endif
%endif
2009-04-16 17:15:48 +04:00
%changelog
2019-03-08 18:17:14 +03:00
* Wed Mar 6 2019 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- remove unneeded ldconfig in scriptlets
- reported by Igor Gnatenko in Fedora
- https://src.fedoraproject.org/rpms/glusterfs/pull-request/5
* Mon Mar 4 2019 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- s390x has RDMA, since around Fedora 27 and in RHEL7 since June 2016.
2019-01-30 11:54:14 +03:00
* Tue Feb 26 2019 Ashish Pandey <aspandey@redhat.com>
- Add thin-arbiter package
2019-02-21 08:55:55 +03:00
* Sun Feb 24 2019 Aravinda VK <avishwan@redhat.com>
- Renamed events package to gfevents
2019-02-11 08:37:49 +03:00
* Thu Feb 21 2019 Jiffin Tony Thottan <jthottan@redhat.com>
- Obsoleting gluster-gnfs package
2018-11-28 10:09:31 +03:00
* Wed Nov 28 2018 Krutika Dhananjay <kdhananj@redhat.com>
- Install /var/lib/glusterd/groups/distributed-virt by default
2018-11-13 14:53:17 +03:00
* Tue Nov 13 2018 Niels de Vos <ndevos@redhat.com>
- Add an option to build with ThreadSanitizer (TSAN)
2018-08-10 02:32:22 +03:00
* Fri Sep 7 2018 Niels de Vos <ndevos@redhat.com>
- Add an option to build with address sanitizer (ASAN)
2018-07-29 13:28:43 +03:00
* Sun Jul 29 2018 Niels de Vos <ndevos@redhat.com>
- Disable building glusterfs-resource-agents on el6 (#1609551)
2018-02-12 11:11:04 +03:00
* Thu Feb 22 2018 Kotresh HR <khiremat@redhat.com>
- Added util-linux as dependency to georeplication rpm (#1544382)
2018-01-31 18:38:34 +03:00
* Thu Feb 1 2018 Niels de Vos <ndevos@redhat.com>
- Add '--without server' option to facilitate el6 builds (#1074947)
2018-01-24 20:56:14 +03:00
* Wed Jan 24 2018 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- python-ctypes no long exists, now in python stdlib (#1538258)
2018-01-18 23:24:00 +03:00
* Thu Jan 18 2018 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- Fedora 28 glibc has removed rpc headers and rpcgen, use libtirpc
2017-12-25 16:40:16 +03:00
* Mon Dec 25 2017 Niels de Vos <ndevos@redhat.com>
- Fedora 28 has renamed pyxattr
2018-01-18 23:24:00 +03:00
* Wed Sep 27 2017 Mohit Agrawal <moagrawa@redhat.com>
2017-09-27 09:07:28 +03:00
- Added control-cpu-load.sh and control-mem.sh scripts to glusterfs-server section(#1496335)
2017-08-22 17:21:48 +03:00
* Tue Aug 22 2017 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- libibverbs-devel, librdmacm-devel -> rdma-core-devel #1483995
2017-07-20 14:38:12 +03:00
* Thu Jul 20 2017 Aravinda VK <avishwan@redhat.com>
- Added new tool/binary to set the gfid2path xattr on files
2017-07-13 18:35:50 +03:00
* Thu Jul 13 2017 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- various directories not owned by any package
2017-05-19 09:51:37 +03:00
* Fri Jun 16 2017 Jiffin Tony Thottan <jthottan@redhat.com>
- Add glusterfssharedstorage.service systemd file
2017-06-09 09:01:19 +03:00
* Fri Jun 9 2017 Poornima G <pgurusid@redhat.com>
- Install /var/lib/glusterd/groups/nl-cache by default
2017-05-10 13:56:35 +03:00
* Wed May 10 2017 Pranith Kumar K <pkarampu@redhat.com>
- Install /var/lib/glusterd/groups/gluster-block by default
2017-03-27 23:09:56 +03:00
* Thu Apr 27 2017 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- gnfs in an optional subpackage
2017-04-26 15:11:56 +03:00
* Wed Apr 26 2017 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- /var/run/gluster owner gluster:gluster(0775) for qemu(gfapi)
statedumps (#1445569)
2014-01-02 23:03:18 +04:00
* Mon Apr 24 2017 Jiffin Tony Thottan <jhottan@redhat.com>
- Install SELinux hook scripts that manage contexts for bricks (#1047975)
2017-04-20 16:46:46 +03:00
* Thu Apr 20 2017 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- firewalld-filesystem -> firewalld (#1443959)
2017-04-13 19:26:29 +03:00
* Thu Apr 13 2017 Niels de Vos <ndevos@redhat.com>
- the -regression-tests sub-package needs " b c " for some tests (#1442145)
2017-03-21 00:24:37 +03:00
* Mon Mar 20 2017 Niels de Vos <ndevos@redhat.com>
- Drop dependency on psmisc, pkill is used instead of killall (#1197308)
2017-02-16 22:32:36 +03:00
* Thu Feb 16 2017 Niels de Vos <ndevos@redhat.com>
- Obsolete and Provide python-gluster for upgrading from glusterfs < 3.10
2017-04-21 20:43:08 +03:00
* Tue Feb 7 2017 Kaleb S. KEITHLEY <kkeithle@redhat.com>
2017-02-01 15:50:17 +03:00
- remove ganesha (#1418417)
2017-02-01 14:41:46 +03:00
* Wed Feb 1 2017 Poornima G <pgurusid@redhat.com>
- Install /var/lib/glusterd/groups/metadata-cache by default
2017-01-18 20:51:19 +03:00
* Wed Jan 18 2017 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- python2 (versus python3) cleanup (#1414902)
2017-01-06 18:37:54 +03:00
* Fri Jan 13 2017 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- switch to storhaug HA
2017-01-06 19:16:38 +03:00
* Fri Jan 6 2017 Niels de Vos <ndevos@redhat.com>
- use macro provided by firewalld-filesystem to reload firewalld
2016-11-23 13:34:26 +03:00
* Thu Nov 24 2016 Jiffin Tony Thottan <jhottan@redhat.com>
- remove S31ganesha-reset.sh from hooks (#1397795)
2016-09-22 15:22:50 +03:00
* Thu Sep 22 2016 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- python-ctypes no long exists, now in python stdlib (#1378436)
2016-09-13 13:08:24 +03:00
* Wed Sep 14 2016 Aravinda VK <avishwan@redhat.com>
- Changed attribute of eventsconfig.json file as same as other configs (#1375532)
2016-08-31 06:03:44 +03:00
* Thu Sep 08 2016 Aravinda VK <avishwan@redhat.com>
- Added init script for glustereventsd (#1365395)
2016-08-26 11:35:07 +03:00
* Wed Aug 31 2016 Avra Sengupta <asengupt@redhat.com>
- Added conf.py for snap scheduler
2016-06-15 11:24:37 +03:00
* Wed Aug 31 2016 Aravinda VK <avishwan@redhat.com>
- Added new Geo-replication utility " g l u s t e r - g e o r e p - s s h k e y " (#1356508)
geo-rep: Simplify Non root user(mountbroker) Setup
Setting up Non root Geo-replication is troublesome. Lot of steps
involved like user setup, directory creation, setting up proper
permissions, editing glusterd.vol file etc.
Introducing `gluster-mountbroker` command, with this tool non root
user setup steps are(Run the following commands in any one Slave
node),
gluster-mountbroker setup <MOUNT ROOT> <GROUP>
For example,
gluster-mountbroker setup /var/mountbroker-root geogroup
Add user using,
gluster-mountbroker add <VOLUME> <USER>
For example,
gluster-mountbroker add slavevol geoaccount
Remove user or Volume using,
gluster-mountbroker remove [--volume <VOLUME>] [--user <USER>]
Example,
gluster-mountbroker remove --volume slavevol --user geoaccount
gluster-mountbroker remove --user geoaccount
gluster-mountbroker remove --volume slavevol
Check the status of setup using,
gluster-mountbroker status
Once the changes are complete, restart glusterd in all Slave nodes.
and follow the Geo-rep instructions.
Change-Id: Ied3fa009df6a886b24ddd86d39283fcfcff68c82
BUG: 1343333
Signed-off-by: Aravinda VK <avishwan@redhat.com>
Reviewed-on: http://review.gluster.org/14544
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
Smoke: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Kotresh HR <khiremat@redhat.com>
2016-05-26 13:22:53 +03:00
* Thu Aug 25 2016 Aravinda VK <avishwan@redhat.com>
2016-06-15 11:24:37 +03:00
- Added gluster-mountbroker utility for geo-rep mountbroker setup (#1343333)
geo-rep: Simplify Non root user(mountbroker) Setup
Setting up Non root Geo-replication is troublesome. Lot of steps
involved like user setup, directory creation, setting up proper
permissions, editing glusterd.vol file etc.
Introducing `gluster-mountbroker` command, with this tool non root
user setup steps are(Run the following commands in any one Slave
node),
gluster-mountbroker setup <MOUNT ROOT> <GROUP>
For example,
gluster-mountbroker setup /var/mountbroker-root geogroup
Add user using,
gluster-mountbroker add <VOLUME> <USER>
For example,
gluster-mountbroker add slavevol geoaccount
Remove user or Volume using,
gluster-mountbroker remove [--volume <VOLUME>] [--user <USER>]
Example,
gluster-mountbroker remove --volume slavevol --user geoaccount
gluster-mountbroker remove --user geoaccount
gluster-mountbroker remove --volume slavevol
Check the status of setup using,
gluster-mountbroker status
Once the changes are complete, restart glusterd in all Slave nodes.
and follow the Geo-rep instructions.
Change-Id: Ied3fa009df6a886b24ddd86d39283fcfcff68c82
BUG: 1343333
Signed-off-by: Aravinda VK <avishwan@redhat.com>
Reviewed-on: http://review.gluster.org/14544
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
Smoke: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Kotresh HR <khiremat@redhat.com>
2016-05-26 13:22:53 +03:00
2016-08-17 10:38:41 +03:00
* Mon Aug 22 2016 Milind Changire <mchangir@redhat.com>
- Add psmisc as dependency for glusterfs-fuse for killall command (#1367665)
2016-08-01 09:41:24 +03:00
* Thu Aug 4 2016 Jiffin Tony Thottan <jthottan@redhat.com>
- Remove ganesha.so from client xlators
2016-07-08 10:00:25 +03:00
* Sun Jul 31 2016 Soumya Koduri <skoduri@redhat.com>
- Add dependency on portblock resource agent for ganesha package (#1354439)
2016-08-05 14:27:26 +03:00
* Mon Jul 18 2016 Aravinda VK <avishwan@redhat.com>
eventsapi: Gluster Eventing Feature implementation
[Depends on http://review.gluster.org/14627]
Design is available in `glusterfs-specs`, A change from the design
is support of webhook instead of Websockets as discussed in the design
http://review.gluster.org/13115
Since Websocket support depends on REST APIs, I will add Websocket support
once REST APIs patch gets merged
Usage:
Run following command to start/stop Eventsapi server in all Peers,
which will collect the notifications from any Gluster daemon and emits
to configured client.
gluster-eventsapi start|stop|restart|reload
Status of running services can be checked using,
gluster-eventsapi status
Events listener is a HTTP(S) server which listens to events emited by
the Gluster. Create a HTTP Server to listen on POST and register that
URL using,
gluster-eventsapi webhook-add <URL> [--bearer-token <TOKEN>]
For example, if HTTP Server running in `http://192.168.122.188:9000`
then add that URL using,
gluster-eventsapi webhook-add http://192.168.122.188:9000
If it expects a Token then specify it using `--bearer-token` or `-t`
We can also test Webhook if all peer nodes can send message or not
using,
gluster-eventsapi webhook-test <URL> [--bearer-token <TOKEN>]
Configurations can be viewed/updated using,
gluster-eventsapi config-get [--name]
gluster-eventsapi config-set <NAME> <VALUE>
gluster-eventsapi config-reset <NAME|all>
If any one peer node was down during config-set/reset or webhook
modifications, Run sync command from good node when a peer node comes
back. Automatic update is not yet implemented.
gluster-eventsapi sync
Basic Events Client(HTTP Server) is included with the code, Start
running the client with required port and start listening to the
events.
/usr/share/glusterfs/scripts/eventsdash.py --port 8080
Default port is 9000, if no port is specified, once it started running
then configure gluster-eventsapi to send events to that client.
Eventsapi Client can be outside of the Cluster, it can be run event on
Windows. But only requirement is the client URL should be accessible
by all peer nodes.(Or ngrok(https://ngrok.com) like tools can be used)
Events implemented with this patch,
- Volume Create
- Volume Start
- Volume Stop
- Volume Delete
- Peer Attach
- Peer Detach
It is easy to add/support more events, since it touches Gluster cmd
code and to avoid merge conflicts I will add support for more events
once this patch merges.
BUG: 1334044
Change-Id: I316827ac9dd1443454df7deffe4f54835f7f6a08
Signed-off-by: Aravinda VK <avishwan@redhat.com>
Reviewed-on: http://review.gluster.org/14248
Smoke: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
2016-05-05 16:04:41 +03:00
- Added new subpackage events(glusterfs-events) (#1334044)
2016-07-15 10:45:21 +03:00
* Fri Jul 15 2016 Aravinda VK <avishwan@redhat.com>
- Removed " . p y " extension from symlink(S57glusterfind-delete-post)(#1356868)
2016-07-14 10:34:09 +03:00
* Thu Jul 14 2016 Aravinda VK <avishwan@redhat.com>
- Removed extra packaging line of cliutils(python-gluster)(#1342356)
2016-05-31 11:09:05 +03:00
* Mon Jul 11 2016 Aravinda VK <avishwan@redhat.com>
- Added Python subpackage " c l i u t i l s " under gluster
2016-05-31 21:00:35 +03:00
* Tue May 31 2016 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- broken brp-python-bytecompile in RHEL7 results in installed
but unpackaged files.
2016-05-06 19:07:41 +03:00
* Fri May 6 2016 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- additional dirs and files in /var/lib/glusterd/... (#1326410)
2016-04-26 17:10:05 +03:00
* Tue Apr 26 2016 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- %%postun libs w/o firewalld on RHEL6 (#1330583)
2016-04-12 18:35:38 +03:00
* Tue Apr 12 2016 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- additional dirs and files in /var/lib/glusterd/... (#1326410)
packaging: rpm scriptlet cleanup, handle -p /sbin/ldconfig
The RPM documention indicates that during an rpm install or erase, the
script(lets): %post, %preun, and %postun (and %pre, %build, %install,
etc.) are copied to a temp file, and then the temp file is run as a
(/bin/sh or bash) script.
Unfortunately the documentation is not clear about how rpmbuild and/or
rpm determine where the end of any scriptlet is when it is copied to
the file.
Most things in the glusterfs.spec work correctly as is. These are the
%preun, %post, and %postun scriptlets that are "closed" by a following
%preun, %post, and %postun, or poetentially another scriptlet, e.g.
%file.
The ones that don't work correctly (only one actually) are those where
there is a comment in the spec file before it is closed by another
scriptlet. Further complicating things is that the type of scriptlet
affects what rpm does and what `rpm -qp --scripts ...` shows.
The specific one that didn't work was the "%postun libs" scriptlet. It
is followed by a comment before being "closed" by the %files section (or
scriptlet). It can be written two ways: "%postun libs\n/sbin/ldconfig"
or "%postun libs -p /sbin/ldconfig" Either way it's written, `rpm -qp
--scripts glusterfs-libs...` will include the comment lines between the
%postun libs line and the following %files line.
But the way rpm executes these depends on how they're written. If
written as "%postun libs\n/sbin/ldconfig" rpm will simply run
/sbin/ldconfig with no command line options, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig" ], [ ]);
But when written as "%postun libs -p /sbin/ldconfig", it will copy
the comment lines to a temp file, and pass the temp file name and "1"
as (command line) parameters, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig", "/tmp/tmpXXXXXX", "1" ],
[ ]);
Which results in ldconfig exiting with an error. (Remember, both ways show
the comment in `rpm -qp --scripts ...`)
(Note though, that the similar "%postun api -p /sbin/ldconfig" is run
correctly, because it is "closed" by the following "%postun server"
scriptlet.)
Finally, through trial and error, it appears that rpm can be tricked with
a hack, and "closure" of the scriptlet forcedlike this:
%postun libs -p /sbin/ldconfig
%if ( 0%{?_undocumented_hack_closes_scriptlets} )
%postun
%endif
in which case ldconfig appears to run correctly. Note also that here too
the comment will be included in the output of `rpm -qp --scripts ...`
But that's very ugly hack.
Change-Id: I587a490ddcdf47d01605479bc8ef8b0e439108fb
BUG: 1315024
Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
Reviewed-on: http://review.gluster.org/13613
Smoke: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
2016-03-06 00:06:18 +03:00
* Mon Mar 7 2016 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- %%pre, %%post etc. scriptlet cleanup, ... -p /sbin/ldconfig (#1315024)
2016-01-22 09:41:18 +03:00
* Fri Jan 22 2016 Aravinda VK <avishwan@redhat.com>
- Added schedule_georep.py script to the glusterfs-geo-replication (#1300956)
2016-01-08 18:43:15 +03:00
* Sat Jan 16 2016 Niels de Vos <ndevos@redhat.com>
- glusterfs-server depends on -api (#1296931)
2016-01-10 15:42:58 +03:00
* Sun Jan 10 2016 Niels de Vos <ndevos@redhat.com>
- build system got fixed so that special glupy build is not needed anymore
2015-12-28 12:26:20 +03:00
* Mon Dec 28 2015 Niels de Vos <ndevos@redhat.com>
- hook scripts in glusterfs-ganesha use dbus-send, add dependency (#1294446)
2015-12-23 15:57:14 +03:00
* Tue Dec 22 2015 Niels de Vos <ndevos@redhat.com>
- move hook scripts for nfs-ganesha to the -ganesha sub-package
- use standard 'make' installation for the hook scripts (#1174765)
2015-09-01 19:12:21 +03:00
* Tue Sep 1 2015 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- erroneous ghost of ../hooks/1/delete causes install failure (#1258975)
2015-08-21 22:39:53 +03:00
* Tue Aug 25 2015 Anand Nekkunti <anekkunt@redhat.com>
- adding glusterfs-firewalld service (#1253967)
2015-06-18 01:21:59 +03:00
* Tue Aug 18 2015 Niels de Vos <ndevos@redhat.com>
- Include missing directories for glusterfind hooks scripts (#1225465)
2015-06-15 11:43:44 +03:00
* Mon Jun 15 2015 Niels de Vos <ndevos@redhat.com>
- Replace hook script S31ganesha-set.sh by S31ganesha-start.sh (#1231738)
2015-06-12 14:49:55 +03:00
* Fri Jun 12 2015 Aravinda VK <avishwan@redhat.com>
- Added rsync as dependency to georeplication rpm (#1231205)
2015-05-27 15:35:35 +03:00
* Tue Jun 02 2015 Aravinda VK <avishwan@redhat.com>
- Added post hook for volume delete as part of glusterfind (#1225465)
2015-05-27 09:26:53 +03:00
* Wed May 27 2015 Aravinda VK <avishwan@redhat.com>
- Added stop-all-gluster-processes.sh in glusterfs-server section (#1204641)
2015-05-20 16:34:26 +03:00
* Wed May 20 2015 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- python-gluster should be 'noarch' (#1219954)
2015-05-20 16:10:38 +03:00
* Wed May 20 2015 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- move libgf{db,changelog}.pc from -api-devel to -devel (#1223385)
2015-05-19 12:01:23 +03:00
* Wed May 20 2015 Anand Nekkunti <anekkunt@redhat.com>
- glusterd.socket file cleanup during post run upgrade (#1210404)
glusterd/shared_storage: Provide a volume set option to create and mount the shared storage
Introducing a global volume set option(cluster.enable-shared-storage)
which helps create and set-up the shared storage meta volume.
gluster volume set all cluster.enable-shared-storage enable
On enabling this option, the system analyzes the number of peers
in the cluster, which are currently connected, and chooses three
such peers(including the node the command is issued from). From these
peers a volume(gluster_shared_storage) is created. Depending on the
number of peers available the volume is either a replica 3
volume(if there are 3 connected peers), or a replica 2 volume(if there
are 2 connected peers). "/var/run/gluster/ss_brick" serves as the
brick path on each node for the shared storage volume. We also mount
the shared storage at "/var/run/gluster/shared_storage" on all the nodes
in the cluster as part of enabling this option. If there is only one node
in the cluster, or only one node is up then the command will fail
Once the volume is created, and mounted the maintainance of the
volume like adding-bricks, removing bricks etc., is expected to
be the onus of the user.
On disabling the option, we provide the user a warning, and on
affirmation from the user we stop the shared storage volume, and unmount
it from all the nodes in the cluster.
gluster volume set all cluster.enable-shared-storage disable
Change-Id: Idd92d67b93f444244f99ede9f634ef18d2945dbc
BUG: 1222013
Signed-off-by: Avra Sengupta <asengupt@redhat.com>
Reviewed-on: http://review.gluster.org/10793
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Tested-by: NetBSD Build System <jenkins@build.gluster.org>
Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
2015-05-14 12:30:59 +03:00
* Tue May 19 2015 Avra Sengupta <asengupt@redhat.com>
- Added S32gluster_enable_shared_storage.sh as volume set hook script (#1222013)
2015-05-18 17:02:48 +03:00
* Mon May 18 2015 Milind Changire <mchangir@redhat.com>
- Move file peer_add_secret_pub to the server RPM to support glusterfind (#1221544)
2015-05-17 16:26:03 +03:00
* Sun May 17 2015 Niels de Vos <ndevos@redhat.com>
- Fix building on RHEL-5 based distributions (#1222317)
2015-05-05 11:28:15 +03:00
* Tue May 05 2015 Niels de Vos <ndevos@redhat.com>
- Introduce glusterfs-client-xlators to reduce dependencies (#1195947)
2015-04-15 09:59:16 +03:00
* Wed Apr 15 2015 Humble Chirammal <hchiramm@redhat.com>
- Introducing python-gluster package to own gluster namespace in sitelib (#1211848)
2015-03-27 21:13:05 +03:00
* Sat Mar 28 2015 Mohammed Rafi KC <rkavunga@redhat.com>
- Add dependency for librdmacm version >= 1.0.15 (#1206744)
2015-03-24 12:54:25 +03:00
* Tue Mar 24 2015 Niels de Vos <ndevos@redhat.com>
- move libgfdb (with sqlite dependency) to -server subpackage (#1194753)
2015-03-17 16:27:05 +03:00
* Tue Mar 17 2015 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- glusterfs-ganesha sub-package
2015-01-29 13:23:19 +03:00
* Thu Mar 12 2015 Kotresh H R <khiremat@redhat.com>
- gfind_missing_files tool is included (#1187140)
2015-02-18 16:37:23 +03:00
* Tue Mar 03 2015 Aravinda VK <avishwan@redhat.com>
- Included glusterfind files as part of server package.
2015-02-09 15:33:20 +03:00
* Sun Mar 1 2015 Avra Sengupta <asengupt@redhat.com>
- Added installation of snap-scheduler
2015-02-18 16:47:01 +03:00
* Thu Feb 26 2015 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- enable cmocka unittest support only when asked for (#1067059)
2015-02-10 21:13:35 +03:00
* Tue Feb 24 2015 Niels de Vos <ndevos@redhat.com>
- POSIX ACL conversion needs BuildRequires libacl-devel (#1185654)
2015-02-18 16:47:01 +03:00
* Wed Feb 18 2015 Andreas Schneider <asn@redhat.com>
- Change cmockery2 to cmocka.
2015-01-06 12:42:59 +03:00
* Wed Feb 18 2015 Kaushal M <kaushal@redhat.com>
- add userspace-rcu as a requirement
2015-02-13 14:40:37 +03:00
* Fri Feb 13 2015 Gaurav Kumar Garg <ggarg@redhat.com>
- .cmd_log_history file should be renamed to cmd_history.log post
upgrade (#1165996)
2015-01-30 11:47:23 +03:00
* Fri Jan 30 2015 Nandaja Varma <nvarma@redhat.com>
- remove checks for rpmbuild/mock from run-tests.sh (#178008)
2015-01-16 15:48:49 +03:00
* Fri Jan 16 2015 Niels de Vos <ndevos@redhat.com>
- add support for /run/gluster through a tmpfiles.d config file (#1182934)
geo-rep: mountbroker user management
Non root geo-replication setup is now simplified. This
patch provides cli for mountbroker user and options management
To set Options,
gluster system:: execute mountbroker opt <KEY> <VALUE>
# for example,
gluster system:: execute mountbroker opt mountbroker-root /var/mountbroker-root
gluster system:: execute mountbroker opt geo-replication-log-group geogroup
gluster system:: execute mountbroker opt rpc-auth-allow-insecure on
To remove option,
gluster system:: execute mountbroker optdel <KEY>
# for example,
gluster system:: execute mountbroker optdel geo-replication-log-group
To add/edit user,
gluster system:: execute mountbroker user <USERNAME> <VOLUMES>
# for example
gluster system:: execute mountbroker user geoaccount slavevol1,slavevol2
To remove user,
gluster system:: execute mountbroker userdel <USERNAME>
# for example
gluster system:: execute mountbroker userdel geoaccount
For info,
gluster system:: execute mountbroker info
gluster system:: execute mountbroker -j info
For JSON output add -j after mountbroker, for example,
gluster system:: execute mountbroker -j user geoaccount slavevol1,slavevol2
PS: Each peer prints its own JSON output, aggregator required from consumer side
BUG: 1136312
Change-Id: Ie52210c0bcc91ac2ffd3ba58988222ffca62b47f
Signed-off-by: Aravinda VK <avishwan@redhat.com>
Reviewed-on: http://review.gluster.org/9398
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: darshan n <dnarayan@redhat.com>
Reviewed-by: Kotresh HR <khiremat@redhat.com>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
2015-01-06 15:50:45 +03:00
* Tue Jan 6 2015 Aravinda VK<avishwan@redhat.com>
- Added new libexec script for mountbroker user management (peer_mountbroker)
2014-12-12 16:12:35 +03:00
* Fri Dec 12 2014 Niels de Vos <ndevos@redhat.com>
- do not package all /usr/share/glusterfs/* files in regression-tests (#1169005)
2014-09-25 17:11:46 +04:00
* Fri Sep 26 2014 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- smarter logic in %%post server (#1146426)
2014-07-02 12:51:39 +04:00
* Wed Sep 24 2014 Balamurugan Arumugam <barumuga@redhat.com>
- remove /sbin/ldconfig as interpreter (#1145989)
2014-09-05 08:12:18 +04:00
* Fri Sep 5 2014 Lalatendu Mohanty <lmohanty@redhat.com>
- Changed the description as " G l u s t e r F S a d i s t r i b u t e d f i l e s y s t e m "
2014-08-05 16:29:42 +04:00
* Tue Aug 5 2014 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- logrotate files (#1126832)
2014-04-24 00:18:57 +04:00
* Wed Jul 16 2014 Luis Pabon <lpabon@redhat.com>
- Added cmockery2 dependency
2014-06-27 01:14:39 +04:00
* Fri Jun 27 2014 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- killall --wait in %%post server, (#1113543)
2014-08-27 12:35:15 +04:00
* Thu Jun 19 2014 Humble Chirammal <hchiramm@redhat.com>
- Added dynamic loading of fuse module with glusterfs-fuse package installation in el5.
2014-06-04 13:31:14 +04:00
* Thu Jun 12 2014 Varun Shastry <vshastry@redhat.com>
- Add bash completion config to the cli package
2014-06-03 17:45:42 +04:00
* Tue Jun 03 2014 Vikhyat Umrao <vumrao@redhat.com>
- add nfs-utils package dependency for server package (#1065654)
2014-05-22 15:16:15 +04:00
* Thu May 22 2014 Poornima G <pgurusid@redhat.com>
- Rename old hookscripts in an RPM-standard way.
2014-05-19 11:25:34 +04:00
* Tue May 20 2014 Niels de Vos <ndevos@redhat.com>
- Almost drop calling ./autogen.sh
2014-04-25 18:14:14 +04:00
* Fri Apr 25 2014 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- Sync with Fedora spec (#1091408, #1091392)
2014-04-25 09:46:02 +04:00
* Fri Apr 25 2014 Arumugam Balamurugan <barumuga@redhat.com>
- fix RHEL 7 build failure " I n s t a l l e d ( b u t u n p a c k a g e d ) f i l e ( s ) f o u n d " (#1058188)
2014-02-28 09:40:51 +04:00
* Wed Apr 02 2014 Arumugam Balamurugan <barumuga@redhat.com>
- cleanup to rearrange spec file elements
2014-02-27 11:09:43 +04:00
* Wed Apr 02 2014 Arumugam Balamurugan <barumuga@redhat.com>
- add version/release dynamically (#1074919)
packaging: rpm scriptlet cleanup, handle -p /sbin/ldconfig
The RPM documention indicates that during an rpm install or erase, the
script(lets): %post, %preun, and %postun (and %pre, %build, %install,
etc.) are copied to a temp file, and then the temp file is run as a
(/bin/sh or bash) script.
Unfortunately the documentation is not clear about how rpmbuild and/or
rpm determine where the end of any scriptlet is when it is copied to
the file.
Most things in the glusterfs.spec work correctly as is. These are the
%preun, %post, and %postun scriptlets that are "closed" by a following
%preun, %post, and %postun, or poetentially another scriptlet, e.g.
%file.
The ones that don't work correctly (only one actually) are those where
there is a comment in the spec file before it is closed by another
scriptlet. Further complicating things is that the type of scriptlet
affects what rpm does and what `rpm -qp --scripts ...` shows.
The specific one that didn't work was the "%postun libs" scriptlet. It
is followed by a comment before being "closed" by the %files section (or
scriptlet). It can be written two ways: "%postun libs\n/sbin/ldconfig"
or "%postun libs -p /sbin/ldconfig" Either way it's written, `rpm -qp
--scripts glusterfs-libs...` will include the comment lines between the
%postun libs line and the following %files line.
But the way rpm executes these depends on how they're written. If
written as "%postun libs\n/sbin/ldconfig" rpm will simply run
/sbin/ldconfig with no command line options, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig" ], [ ]);
But when written as "%postun libs -p /sbin/ldconfig", it will copy
the comment lines to a temp file, and pass the temp file name and "1"
as (command line) parameters, i.e.
execve ("/sbin/ldconfig", [ "/sbin/ldconfig", "/tmp/tmpXXXXXX", "1" ],
[ ]);
Which results in ldconfig exiting with an error. (Remember, both ways show
the comment in `rpm -qp --scripts ...`)
(Note though, that the similar "%postun api -p /sbin/ldconfig" is run
correctly, because it is "closed" by the following "%postun server"
scriptlet.)
Finally, through trial and error, it appears that rpm can be tricked with
a hack, and "closure" of the scriptlet forcedlike this:
%postun libs -p /sbin/ldconfig
%if ( 0%{?_undocumented_hack_closes_scriptlets} )
%postun
%endif
in which case ldconfig appears to run correctly. Note also that here too
the comment will be included in the output of `rpm -qp --scripts ...`
But that's very ugly hack.
Change-Id: I587a490ddcdf47d01605479bc8ef8b0e439108fb
BUG: 1315024
Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
Reviewed-on: http://review.gluster.org/13613
Smoke: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
2016-03-06 00:06:18 +03:00
* Thu Mar 27 2014 Kaleb S. KEITHLEY <kkeithle@redhat.com>
2016-01-08 18:43:15 +03:00
- attr dependency (#1184626)
2014-03-26 16:00:32 +04:00
* Wed Mar 26 2014 Poornima G <pgurusid@redhat.com>
- Include the hook scripts of add-brick, volume start, stop and set
2014-02-16 19:58:46 +04:00
* Wed Feb 26 2014 Niels de Vos <ndevos@redhat.com>
- Drop glusterfs-devel dependency from glusterfs-api (#1065750)
2014-03-22 00:13:16 +04:00
* Wed Feb 19 2014 Justin Clift <justin@gluster.org>
- Rename gluster.py to glupy.py to avoid namespace conflict (#1018619)
- Move the main Glupy files into glusterfs-extra-xlators rpm
- Move the Glupy Translator examples into glusterfs-devel rpm
2014-02-06 15:46:20 +04:00
* Thu Feb 06 2014 Aravinda VK <avishwan@redhat.com>
- Include geo-replication upgrade scripts and hook scripts.
2014-01-15 17:22:44 +04:00
* Wed Jan 15 2014 Niels de Vos <ndevos@redhat.com>
- Install /var/lib/glusterd/groups/virt by default
2014-01-04 20:29:26 +04:00
* Sat Jan 4 2014 Niels de Vos <ndevos@redhat.com>
- The main glusterfs package should not provide glusterfs-libs (#1048489)
2013-12-10 16:26:46 +04:00
* Tue Dec 10 2013 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- Sync with Fedora glusterfs.spec 3.5.0-0.1.qa3
2013-12-23 23:13:17 +04:00
* Fri Oct 11 2013 Harshavardhana <fharshav@redhat.com>
2013-10-09 08:30:21 +04:00
- Add '_sharedstatedir' macro to `/var/lib` on <= RHEL5 (#1003184)
2013-10-09 16:29:18 +04:00
* Wed Oct 9 2013 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- Sync with Fedora glusterfs.spec 3.4.1-2+
2013-10-09 13:13:11 +04:00
* Wed Oct 9 2013 Niels de Vos <ndevos@redhat.com>
- glusterfs-api-devel requires glusterfs-devel (#1016938, #1017094)
2013-10-09 16:29:18 +04:00
* Mon Sep 30 2013 Niels de Vos <ndevos@redhat.com>
2013-09-30 11:05:14 +04:00
- Package gfapi.py into the Python site-packages path (#1005146)
2013-08-21 11:50:41 +04:00
* Tue Sep 17 2013 Harshavardhana <fharshav@redhat.com>
- Provide a new package called " g l u s t e r f s - r e g r e s s i o n - t e s t s " for standalone
regression testing.
2013-08-22 18:25:58 +04:00
* Thu Aug 22 2013 Niels de Vos <ndevos@redhat.com>
- Correct the day/date for some entries in this changelog (#1000019)
2013-08-07 17:11:48 +04:00
* Wed Aug 7 2013 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- Sync with Fedora glusterfs.spec
- add Requires
- add -cli subpackage,
- fix other minor differences with Fedora glusterfs.spec
2013-07-30 22:00:46 +04:00
* Tue Jul 30 2013 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- Sync with Fedora glusterfs.spec, add glusterfs-libs RPM for oVirt/qemu-kvm
2013-07-10 16:02:41 +04:00
* Thu Jul 25 2013 Csaba Henk <csaba@redhat.com>
2013-12-10 16:26:46 +04:00
- Added peer_add_secret_pub and peer_gsec_create to %%{_libexecdir} /glusterfs
2013-07-10 16:02:41 +04:00
2013-06-01 14:47:57 +04:00
* Thu Jul 25 2013 Aravinda VK <avishwan@redhat.com>
2013-12-10 16:26:46 +04:00
- Added gverify.sh to %%{_libexecdir} /glusterfs directory.
2013-06-01 14:47:57 +04:00
2013-07-26 07:10:55 +04:00
* Thu Jul 25 2013 Harshavardhana <fharshav@redhat.com>
- Allow to build with '--without bd' to disable 'bd' xlator
2013-06-27 18:44:44 +04:00
* Thu Jun 27 2013 Kaleb S. KEITHLEY <kkeithle@redhat.com>
2013-12-10 16:26:46 +04:00
- fix the hardening fix for shlibs, use %%sed macro, shorter ChangeLog
2013-06-27 18:44:44 +04:00
2013-06-26 15:25:22 +04:00
* Wed Jun 26 2013 Niels de Vos <ndevos@redhat.com>
- move the mount/api xlator to glusterfs-api
2013-06-17 21:44:10 +04:00
* Fri Jun 7 2013 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- Sync with Fedora glusterfs.spec, remove G4S/UFO and Swift
2013-03-04 14:44:40 +04:00
* Mon Mar 4 2013 Niels de Vos <ndevos@redhat.com>
- Package /var/run/gluster so that statedumps can be created
2013-01-30 20:29:54 +04:00
* Wed Feb 6 2013 Kaleb S. KEITHLEY <kkeithle@redhat.com>
- Sync with Fedora glusterfs.spec
2012-12-10 17:41:10 +04:00
* Tue Dec 11 2012 Filip Pytloun <filip.pytloun@gooddata.com>
- add sysconfig file
2012-11-06 13:13:07 +04:00
* Thu Oct 25 2012 Niels de Vos <ndevos@redhat.com>
- Add a sub-package for the OCF resource agents
2012-09-05 12:09:07 +04:00
* Wed Sep 05 2012 Niels de Vos <ndevos@redhat.com>
- Don't use python-ctypes on SLES (from Jörg Petersen)
2012-07-10 18:47:07 +04:00
* Tue Jul 10 2012 Niels de Vos <ndevos@redhat.com>
- Include extras/clear_xattrs.sh in the glusterfs-server sub-package
2012-06-08 13:59:31 +04:00
* Thu Jun 07 2012 Niels de Vos <ndevos@redhat.com>
- Mark /var/lib/glusterd as owned by glusterfs, subdirs belong to -server
2012-05-09 22:06:58 +04:00
* Wed May 9 2012 Kaleb S. KEITHLEY <kkeithle[at]redhat.com>
- Add BuildRequires: libxml2-devel so that configure will DTRT on for
- Fedora's Koji build system
2011-11-10 06:27:25 +04:00
* Wed Nov 9 2011 Joe Julian <me@joejulian.name> - git master
- Merge fedora specfile into gluster's spec.in.
- Add conditionals to allow the same spec file to be used for both 3.1 and 3.2
- http://bugs.gluster.com/show_bug.cgi?id=2970
* Wed Oct 5 2011 Joe Julian <me@joejulian.name> - 3.2.4-1
- Update to 3.2.4
- Removed the $local_fs requirement from the init scripts as in RHEL/CentOS that's provided
- by netfs, which needs to be started after glusterd.
* Sun Sep 25 2011 Joe Julian <me@joejulian.name> - 3.2.3-2
- Merged in upstream changes
- Fixed version reporting 3.2git
- Added nfs init script (disabled by default)
2013-08-22 18:25:58 +04:00
* Thu Sep 1 2011 Joe Julian <me@joejulian.name> - 3.2.3-1
2011-11-10 06:27:25 +04:00
- Update to 3.2.3
* Tue Jul 19 2011 Joe Julian <me@joejulian.name> - 3.2.2-3
- Add readline and libtermcap dependencies
* Tue Jul 19 2011 Joe Julian <me@joejulian.name> - 3.2.2-2
- Critical patch to prevent glusterd from walking outside of its own volume during rebalance
* Thu Jul 14 2011 Joe Julian <me@joejulian.name> - 3.2.2-1
- Update to 3.2.2
* Wed Jul 13 2011 Joe Julian <me@joejulian.name> - 3.2.1-2
- fix hardcoded path to gsyncd in source to match the actual file location
2013-08-22 18:25:58 +04:00
* Tue Jun 21 2011 Joe Julian <me@joejulian.name> - 3.2.1
2011-11-10 06:27:25 +04:00
- Update to 3.2.1
* Mon Jun 20 2011 Joe Julian <me@joejulian.name> - 3.1.5
- Update to 3.1.5
2013-08-22 18:25:58 +04:00
* Tue May 31 2011 Joe Julian <me@joejulian.name> - 3.1.5-qa1.4
2011-11-10 06:27:25 +04:00
- Current git
* Sun May 29 2011 Joe Julian <me@joejulian.name> - 3.1.5-qa1.2
- set _sharedstatedir to /var/lib for FHS compliance in RHEL5/CentOS5
- mv /etc/glusterd, if it exists, to the new state dir for upgrading from gluster packaging
* Sat May 28 2011 Joe Julian <me@joejulian.name> - 3.1.5-qa1.1
- Update to 3.1.5-qa1
- Add patch to remove optimization disabling
- Add patch to remove forced 64 bit compile
- Obsolete glusterfs-core to allow for upgrading from gluster packaging
2013-08-22 18:25:58 +04:00
* Sat Mar 19 2011 Jonathan Steffan <jsteffan@fedoraproject.org> - 3.1.3-1
2011-11-10 06:27:25 +04:00
- Update to 3.1.3
- Merge in more upstream SPEC changes
- Remove patches from GlusterFS bugzilla #2309 and #2311
- Remove inode-gen.patch
* Sun Feb 06 2011 Jonathan Steffan <jsteffan@fedoraproject.org> - 3.1.2-3
- Add back in legacy SPEC elements to support older branches
2013-08-22 18:25:58 +04:00
* Thu Feb 03 2011 Jonathan Steffan <jsteffan@fedoraproject.org> - 3.1.2-2
2011-11-10 06:27:25 +04:00
- Add patches from CloudFS project
* Tue Jan 25 2011 Jonathan Steffan <jsteffan@fedoraproject.org> - 3.1.2-1
- Update to 3.1.2
* Wed Jan 5 2011 Dan Horák <dan[at]danny.cz> - 3.1.1-3
- no InfiniBand on s390(x)
* Sat Jan 1 2011 Jonathan Steffan <jsteffan@fedoraproject.org> - 3.1.1-2
- Update to support readline
- Update to not parallel build
* Mon Dec 27 2010 Silas Sewell <silas@sewell.ch> - 3.1.1-1
- Update to 3.1.1
- Change package names to mirror upstream
* Mon Dec 20 2010 Jonathan Steffan <jsteffan@fedoraproject.org> - 3.0.7-1
- Update to 3.0.7
* Wed Jul 28 2010 Jonathan Steffan <jsteffan@fedoraproject.org> - 3.0.5-1
- Update to 3.0.x
* Sat Apr 10 2010 Jonathan Steffan <jsteffan@fedoraproject.org> - 2.0.9-2
- Move python version requires into a proper BuildRequires otherwise
the spec always turned off python bindings as python is not part
of buildsys-build and the chroot will never have python unless we
require it
- Temporarily set -D_FORTIFY_SOURCE=1 until upstream fixes code
GlusterFS Bugzilla #197 (#555728)
- Move glusterfs-volgen to devel subpackage (#555724)
- Update description (#554947)
* Sat Jan 2 2010 Jonathan Steffan <jsteffan@fedoraproject.org> - 2.0.9-1
- Update to 2.0.9
2013-08-22 18:25:58 +04:00
* Sun Nov 8 2009 Jonathan Steffan <jsteffan@fedoraproject.org> - 2.0.8-1
2011-11-10 06:27:25 +04:00
- Update to 2.0.8
- Remove install of glusterfs-volgen, it's properly added to
automake upstream now
* Sat Oct 31 2009 Jonathan Steffan <jsteffan@fedoraproject.org> - 2.0.7-1
- Update to 2.0.7
- Install glusterfs-volgen, until it's properly added to automake
by upstream
- Add macro to be able to ship more docs
* Thu Sep 17 2009 Peter Lemenkov <lemenkov@gmail.com> 2.0.6-2
- Rebuilt with new fuse
* Sat Sep 12 2009 Matthias Saou <http://freshrpms.net/> 2.0.6-1
- Update to 2.0.6.
- No longer default to disable the client on RHEL5 (#522192).
- Update spec file URLs.
* Mon Jul 27 2009 Matthias Saou <http://freshrpms.net/> 2.0.4-1
- Update to 2.0.4.
* Thu Jun 11 2009 Matthias Saou <http://freshrpms.net/> 2.0.1-2
- Remove libglusterfs/src/y.tab.c to fix koji F11/devel builds.
* Sat May 16 2009 Matthias Saou <http://freshrpms.net/> 2.0.1-1
- Update to 2.0.1.
* Thu May 7 2009 Matthias Saou <http://freshrpms.net/> 2.0.0-1
- Update to 2.0.0 final.
* Wed Apr 29 2009 Matthias Saou <http://freshrpms.net/> 2.0.0-0.3.rc8
- Move glusterfsd to common, since the client has a symlink to it.
* Fri Apr 24 2009 Matthias Saou <http://freshrpms.net/> 2.0.0-0.2.rc8
- Update to 2.0.0rc8.
* Sun Apr 12 2009 Matthias Saou <http://freshrpms.net/> 2.0.0-0.2.rc7
- Update glusterfsd init script to the new style init.
- Update files to match the new default vol file names.
- Include logrotate for glusterfsd, use a pid file by default.
- Include logrotate for glusterfs, using killall for lack of anything better.
* Sat Apr 11 2009 Matthias Saou <http://freshrpms.net/> 2.0.0-0.1.rc7
- Update to 2.0.0rc7.
- Rename " l i b s " to " c o m m o n " and move the binary, man page and log dir there.
* Tue Feb 24 2009 Fedora Release Engineering <rel-eng@lists.fedoraproject.org>
- Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild
* Mon Feb 16 2009 Matthias Saou <http://freshrpms.net/> 2.0.0-0.1.rc1
- Update to 2.0.0rc1.
- Include new libglusterfsclient.h.
* Mon Feb 16 2009 Matthias Saou <http://freshrpms.net/> 1.3.12-1
- Update to 1.3.12.
- Remove no longer needed ocreat patch.
* Thu Jul 17 2008 Matthias Saou <http://freshrpms.net/> 1.3.10-1
- Update to 1.3.10.
- Remove mount patch, it's been included upstream now.
* Fri May 16 2008 Matthias Saou <http://freshrpms.net/> 1.3.9-1
- Update to 1.3.9.
* Fri May 9 2008 Matthias Saou <http://freshrpms.net/> 1.3.8-1
- Update to 1.3.8 final.
2013-08-22 18:25:58 +04:00
* Wed Apr 23 2008 Matthias Saou <http://freshrpms.net/> 1.3.8-0.10
2011-11-10 06:27:25 +04:00
- Include short patch to include fixes from latest TLA 751.
2013-08-22 18:25:58 +04:00
* Tue Apr 22 2008 Matthias Saou <http://freshrpms.net/> 1.3.8-0.9
2011-11-10 06:27:25 +04:00
- Update to 1.3.8pre6.
- Include glusterfs binary in both the client and server packages, now that
glusterfsd is a symlink to it instead of a separate binary.
* Sun Feb 3 2008 Matthias Saou <http://freshrpms.net/> 1.3.8-0.8
- Add python version check and disable bindings for version < 2.4.
* Sun Feb 3 2008 Matthias Saou <http://freshrpms.net/> 1.3.8-0.7
- Add --without client rpmbuild option, make it the default for RHEL (no fuse).
(I hope " r h e l " is the proper default macro name, couldn't find it...)
* Wed Jan 30 2008 Matthias Saou <http://freshrpms.net/> 1.3.8-0.6
- Add --without ibverbs rpmbuild option to the package.
* Mon Jan 14 2008 Matthias Saou <http://freshrpms.net/> 1.3.8-0.5
- Update to current TLA again, patch-636 which fixes the known segfaults.
* Thu Jan 10 2008 Matthias Saou <http://freshrpms.net/> 1.3.8-0.4
- Downgrade to glusterfs--mainline--2.5--patch-628 which is more stable.
* Tue Jan 8 2008 Matthias Saou <http://freshrpms.net/> 1.3.8-0.3
- Update to current TLA snapshot.
- Include umount.glusterfs wrapper script (really needed? dunno).
- Include patch to mount wrapper to avoid multiple identical mounts.
* Sun Dec 30 2007 Matthias Saou <http://freshrpms.net/> 1.3.8-0.1
- Update to current TLA snapshot, which includes " v o l u m e - n a m e = " fstab option.
* Mon Dec 3 2007 Matthias Saou <http://freshrpms.net/> 1.3.7-6
- Re-add the /var/log/glusterfs directory in the client sub-package (required).
- Include custom patch to support vol= in fstab for -n glusterfs client option.
* Mon Nov 26 2007 Matthias Saou <http://freshrpms.net/> 1.3.7-4
- Re-enable libibverbs.
- Check and update License field to GPLv3+.
- Add glusterfs-common obsoletes, to provide upgrade path from old packages.
- Include patch to add mode to O_CREATE opens.
* Thu Nov 22 2007 Matthias Saou <http://freshrpms.net/> 1.3.7-3
- Remove Makefile* files from examples.
- Include RHEL/Fedora type init script, since the included ones don't do.
* Wed Nov 21 2007 Matthias Saou <http://freshrpms.net/> 1.3.7-1
- Major spec file cleanup.
2013-07-30 22:00:46 +04:00
- Add missing %%clean section.
2011-11-10 06:27:25 +04:00
- Fix ldconfig calls (weren't set for the proper sub-package).
* Sat Aug 4 2007 Matt Paine <matt@mattsoftware.com> - 1.3.pre7
- Added support to build rpm without ibverbs support (use --without ibverbs
switch)
* Sun Jul 15 2007 Matt Paine <matt@mattsoftware.com> - 1.3.pre6
- Initial spec file
