Fence Agents for Pacemaker from RHCS
Fence Agents is a collection of scripts to handle remote power
management for several devices.
- Developed at network:ha-clustering:Factory
- Sources inherited from project openSUSE:Factory
-
2
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:zSystems/fence-agents && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
0001-Use-Python-3-for-all-scripts-bsc-1065966.patc |
0000005027 4.91 KB | |
_service | 0000000741 741 Bytes | |
_servicedata | 0000000448 448 Bytes | |
fence-agents-4.15.0+git.1719822011.7a2c0a7f.tar.xz | 0000339460 332 KB | |
fence-agents.changes | 0000058089 56.7 KB | |
fence-agents.spec | 0000005661 5.53 KB |
Latest Revision
- Update to version 4.15.0+git.1719822011.7a2c0a7f: * all agents: dont use Deprecated logging.warn() * symlinked agents: set agent_name to use when generating manpages * fence2man.xsl: improve text for symlinked agents * fence_sbd: --sbd-path defaults to /usr/sbin/sbd * configure: check additional paths for programs * fence_aws: log error if unknown state returned * fence_aws: improve list, list-status and status actions * fencing: use formatted strings to avoid failing when plug is int * fence_azure: fix pinning client api versions for compatibility across different azure sdk versions * fence_docker: Connect to Docker via a UNIX socket * fence_hpblade/fence_mpath/fence_scsi: use r"" for all regular expressions to avoid SyntaxWarning errors * fence_aws: fixes to not fail CI, and dont use boto3 buildreq on CI nodes where it's not installed * fence_eps: add fence_epsr2 for ePowerSwitch R2 and newer * fencing: add support for docs["agent_name"] to use the main agent name when generating manpages * spec: only require python3-azure-sdk for RHEL < 9 * spec: remove old python3-azure-sdk dependency * fence_aliyun: update order for new parameters * fence_aliyun: add credentials file support * lib/all agents: use r"" for all regular expressions to avoid SyntaxWarning errors
Comments 0