]>
Commit | Line | Data |
---|---|---|
1 | # NOTE: obsoleted by -fence subpackage from cluster.spec (3.x) | |
2 | Summary: I/O fencing system | |
3 | Summary(pl.UTF-8): System barier I/O | |
4 | Name: fence | |
5 | Version: 2.03.11 | |
6 | Release: 1 | |
7 | Epoch: 1 | |
8 | License: GPL v2+ | |
9 | Group: Applications/System | |
10 | Source0: ftp://sources.redhat.com/pub/cluster/releases/cluster-%{version}.tar.gz | |
11 | # Source0-md5: 712b9f583472d1de614641bc0f4a0aaf | |
12 | Patch0: cluster-kernel.patch | |
13 | URL: http://sources.redhat.com/cluster/fence/ | |
14 | BuildRequires: cman-devel >= 2.03.11 | |
15 | BuildRequires: ccs-devel >= 2.03.11 | |
16 | BuildRequires: perl-base | |
17 | BuildRequires: rpm-pythonprov | |
18 | Requires: cman-libs >= 2.03.11 | |
19 | BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n) | |
20 | ||
21 | %define _sbindir /sbin | |
22 | ||
23 | %description | |
24 | The Fence system does I/O fencing of cluster members. Any member may | |
25 | join the default fence domain after which it will be fenced if it | |
26 | fails without leaving the fence domain cleanly. The lock_dlm GFS lock | |
27 | module will not permit GFS to be mounted until the node has joined a | |
28 | fence domain. | |
29 | ||
30 | The fence daemon, fenced, is usually started by running "fence_tool | |
31 | join". Once started, fenced joins the default fence domain and the | |
32 | node is subject to being fenced if it fails. A collection of fence | |
33 | agents are used by fenced to interface with hardware devices (usually | |
34 | to shut off its path to shared storage or cycle its power source.) | |
35 | ||
36 | %description -l pl.UTF-8 | |
37 | System Fence odpowiada za bariery I/O dla członków klastra. Każdy z | |
38 | członków może dołączyć do domyślnej domeny barier, po czym będzie | |
39 | odgrodzony jeśli zawiedzie nie opuszczając czysto domeny barier. Moduł | |
40 | blokujący GFS-a lock_dlm nie pozwoli na podmontowanie GFS-a dopóki | |
41 | węzeł nie dołączy do domeny barier. | |
42 | ||
43 | Demon fence, fenced, jest zwykle uruchamiany przez fence_tool join. Po | |
44 | uruchomieniu fenced dołącza do domyślnej domeny barier, a węzeł jest | |
45 | przedmiotem odgrodzenia jeśli zawiedzie. fenced wykorzystuje zbiór | |
46 | agentów fence do komunikacji z urządzeniami sprzętowymi (zwykle do | |
47 | odcinania drogi do dzielonej pamięci lub wyłączania i włączania | |
48 | zasilania). | |
49 | ||
50 | %prep | |
51 | %setup -q -n cluster-%{version} | |
52 | %patch0 -p1 | |
53 | ||
54 | %build | |
55 | ./configure \ | |
56 | --cc="%{__cc}" \ | |
57 | --cflags="%{rpmcflags} -Wall" \ | |
58 | --ldflags="%{rpmldflags}" \ | |
59 | --incdir=%{_includedir} \ | |
60 | --libdir=%{_libdir} \ | |
61 | --libexecdir=%{_libdir} \ | |
62 | --mandir=%{_mandir} \ | |
63 | --prefix=%{_prefix} \ | |
64 | --sbindir=%{_sbindir} \ | |
65 | --without_gfs \ | |
66 | --without_gfs2 \ | |
67 | --without_gnbd \ | |
68 | --without_kernel_modules | |
69 | ||
70 | # libgroup.a is not packaged anywhere, so we must build it here | |
71 | %{__make} -C group/lib | |
72 | ||
73 | %{__make} -C %{name} | |
74 | ||
75 | %install | |
76 | rm -rf $RPM_BUILD_ROOT | |
77 | ||
78 | %{__make} -C %{name} install \ | |
79 | DESTDIR=$RPM_BUILD_ROOT | |
80 | ||
81 | %clean | |
82 | rm -rf $RPM_BUILD_ROOT | |
83 | ||
84 | %files | |
85 | %defattr(644,root,root,755) | |
86 | %attr(755,root,root) %{_sbindir}/fence_* | |
87 | %attr(755,root,root) %{_sbindir}/fenced | |
88 | # TODO: PLDify | |
89 | #%attr(754,root,root) /etc/rc.d/init.d/scsi_reserve | |
90 | %{_datadir}/fence | |
91 | #%{_datadir}/snmp/mibs/powernet369.mib | |
92 | %{_mandir}/man8/fence.8* | |
93 | %{_mandir}/man8/fence_*.8* | |
94 | %{_mandir}/man8/fenced.8* |