diff options
Diffstat (limited to '')
85 files changed, 1676 insertions, 92 deletions
diff --git a/debian/changelog b/debian/changelog index a1e3a86..8b07bf8 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,53 @@ +fence-agents (4.12.1-2~exp1) experimental; urgency=medium + + [ Lucas Kanashiro ] + * Create fence-agents-common binary package + * d/control: add one binary package paragraph for each fence agent + * d/fence-agents-*.install: install agents in the approppriate package + * Make fence-agents binary package a metapackage depending on all agents + * d/rules: fix dh_install overrides + * d/rules: no need to override dh_gencontrol + * d/rules: install pycache files to avoid dh_missing error + * d/t/control: adjust some test dependencies due to the split + * Update changelog + + [ Valentin Vidic ] + * d/control: add ${misc:Depends} for fence-agents + * d/control: update package descriptions + * d/rules: do not install pycache files + * d/control: update package descriptions + * d/tests: use Recommends in autopkgtests + * d/control: add python3-openstackclient dependency + + [ Lucas Kanashiro ] + * d/fence-agents-apc-snmp.install: install mib file + * d/control: add python3-socks as runtime dependency of GCE agent + * d/control: add python3-pexpect as a runtime dependency of netio agent + * d/control: add python3-pexpect as runtime dependency of raritan agent + * d/fence-agents-vmware.install: add fence_vmware_helper.pl + + [ Valentin Vidic ] + * d/control: update fence-agents-netio description and depends + * d/control: cleanup depends for fence-agents-common + * d/control: update description for fence-agents-vmware + * d/rules: install fence-vmware-helper to libexec directory + * d/control: update description for fence-agents-crosslink + * d/install: fix mib install for fence-agents-apc-snmp + * d/control: update description for fence-agents-apc-snmp + + [ Lucas Kanashiro ] + * d/control: fix architecture of binary packages + + [ Valentin Vidic ] + * d/rules: remove deprecated zvm agent + * d/control: update description for fence-agents-zvm + * d/control: update description for fence-agents-aliyun + * d/rules: update list of agents skipped in testing + * d/control: update descriptions + * Update metadata test for fence_virt + + -- Valentin Vidic <vvidic@debian.org> Sun, 02 Jul 2023 16:46:59 +0200 + fence-agents (4.12.1-1~progress7.99u1) graograman-backports; urgency=medium * Initial reupload to graograman-backports. diff --git a/debian/control b/debian/control index 440d86b..50dcd89 100644 --- a/debian/control +++ b/debian/control @@ -46,44 +46,1418 @@ XSBC-Original-Vcs-Browser: https://salsa.debian.org/ha-team/fence-agents XSBC-Original-Vcs-Git: https://salsa.debian.org/ha-team/fence-agents.git Package: fence-agents -Architecture: any -Depends: ${misc:Depends}, ${perl:Depends}, ${python3:Depends}, ${shlibs:Depends}, +Architecture: all +Depends: ${misc:Depends}, +Recommends: fence-agents-ack-manual, + fence-agents-aliyun, + fence-agents-alom, + fence-agents-amt, + fence-agents-apc, + fence-agents-apc-snmp, + fence-agents-aws, + fence-agents-azure-arm, + fence-agents-bladecenter, + fence-agents-brocade, + fence-agents-cdu, + fence-agents-cisco-mds, + fence-agents-cisco-ucs, + fence-agents-compute, + fence-agents-crosslink, + fence-agents-cyberpower-ssh, + fence-agents-docker, + fence-agents-drac, + fence-agents-drac5, + fence-agents-dummy, + fence-agents-eaton-snmp, + fence-agents-ecloud, + fence-agents-emerson, + fence-agents-eps, + fence-agents-gce, + fence-agents-hds-cb, + fence-agents-heuristics-ping, + fence-agents-hpblade, + fence-agents-ibmblade, + fence-agents-ibm-powervs, + fence-agents-ibm-vpc, + fence-agents-ibmz, + fence-agents-ifmib, + fence-agents-ilo2, + fence-agents-ilo-moonshot, + fence-agents-ilo-mp, + fence-agents-ilo-ssh, + fence-agents-intelmodular, + fence-agents-ipdu, + fence-agents-ipmilan, + fence-agents-ironic, + fence-agents-kdump, + fence-agents-kubevirt, + fence-agents-ldom, + fence-agents-lindy-pdu, + fence-agents-lpar, + fence-agents-mpath, + fence-agents-netio, + fence-agents-openstack, + fence-agents-ovh, + fence-agents-powerman, + fence-agents-pve, + fence-agents-raritan, + fence-agents-raritan-px3, + fence-agents-rcd-serial, + fence-agents-redfish, + fence-agents-rhevm, + fence-agents-rsa, + fence-agents-rsb, + fence-agents-sanbox2, + fence-agents-scsi, + fence-agents-skalar, + fence-agents-vbox, + fence-agents-virsh, + fence-agents-vmware, + fence-agents-vmware-rest, + fence-agents-vmware-soap, + fence-agents-vmware-vcloud, + fence-agents-wti, + fence-agents-xenapi, + fence-virt, +Suggests: fence-agents-sbd +Description: Fence Agents for Red Hat Cluster - all agents + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + This package is a metapackage depending on all available fence agents. + +Package: fence-agents-common +Architecture: all +Depends: ${misc:Depends}, + ${python3:Depends}, + python3-pexpect, + python3-pycurl, +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - common files + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + This package provides common files used by all fence agents. + +Package: fence-agents-aliyun +Architecture: all +Depends: ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}) +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Aliyun agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + This package provides an I/O fencing agent for Aliyun Web Services in Alibaba + Cloud. + . + Note: This agent requires Aliyun Python SDK to be functional. + +Package: fence-agents-ack-manual +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}) +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - manual ack agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_ack_manual tells fenced to stop retrying and consider the node fenced. + . + It is important that this only be done after the node has been manually turned + off or prevented from writing to shared storage. Without this manual action + and verification, the storage that fencing protects may become corrupted. + +Package: fence-agents-alom +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client, + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Sun ALOM agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_alom is an I/O Fencing agent which can be used with ALOM connected + machines. + +Package: fence-agents-amt +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + amtterm +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Intel AMT agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_amt is an I/O Fencing agent which can be used with Intel AMT. + +Package: fence-agents-apc +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client, + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - APC over telnet/ssh agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_apc is an I/O Fencing agent which can be used with the APC network power + switch. It logs into device via telnet/ssh and reboots a specified outlet. + Lengthy telnet/ssh connections should be avoided while a GFS cluster is running + because the connection will block any necessary fencing actions. + +Package: fence-agents-apc-snmp +Architecture: all +Depends: ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + snmp +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - APC over SNMP agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + This package provides an I/O Fencing agents which can be used with the APC + network power switch or Tripplite PDU devices. It logs into a device via SNMP + and reboots a specified outlet. It supports SNMP v1, v2c, v3 with all + combinations of authenticity/privacy settings. + +Package: fence-agents-aws +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), python3-boto3, + python3-requests +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - AWS agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_aws is an I/O Fencing agent for AWS (Amazon Web Services). It uses the + boto3 library to connect to AWS. + +Package: fence-agents-azure-arm +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-azure +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Azure ARM agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_azure_arm is an I/O Fencing agent for Azure Resource Manager. It uses + Azure SDK for Python to connect to Azure. + +Package: fence-agents-bladecenter +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client, + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - IBM BladeCenter telnet agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_bladecenter is an I/O Fencing agent which can be used with IBM + BladeCenters with recent enough firmware that includes telnet support. It logs + into a Brocade chasis via telnet or ssh and uses the command line interface to + power on and off blades. + +Package: fence-agents-brocade +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client, + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - HP Brocade agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_brocade is an I/O Fencing agent which can be used with Brocade FC + switches. It logs into a Brocade switch via telnet and disables a specified + port. Disabling the port which a machine is connected to effectively fences + that machine. Lengthy telnet connections to the switch should be avoided while + a GFS cluster is running because the connection will block any necessary + fencing actions. + +Package: fence-agents-cdu +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}) +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Sentry Switch CDU agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_cdu is an I/O Fencing agent which can be used with the Sentry Switch + CDU. It logs into the device via telnet and power's on/off an outlet. + +Package: fence-agents-cisco-mds +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + snmp +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Cisco MDS agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_cisco_mds is an I/O Fencing agent which can be used with any Cisco MDS + 9000 series with SNMP enabled device. + +Package: fence-agents-cisco-ucs +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-pycurl +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Cisco UCS agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_cisco_ucs is an I/O Fencing agent which can be used with Cisco UCS to + fence machines. + +Package: fence-agents-compute +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-novaclient +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - OpenStack Compute agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + It tells Nova that compute nodes are down and to reschedule flagged instances. + +Package: fence-agents-crosslink +Architecture: all +Depends: ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + iputils-ping +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - crosslink cable agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + This package provides an agent that helps two-node clusters to tackle the + situation where one node lost power and cannot be fenced by telling pacemaker + that if the node is not reachable over the crosslink cable, it can be assumed + to be dead. + +Package: fence-agents-cyberpower-ssh +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - CyberPower agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_cyberpower_ssh is an I/O Fencing agent which can be used with the + CyberPower network power switch. It logs into device via ssh and reboots a + specified outlet. Lengthy ssh connections should be avoided while a GFS cluster + is running because the connection will block any necessary fencing actions. + +Package: fence-agents-docker +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-pycurl +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Docker agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_docker is I/O fencing agent which can be used with the Docker Engine + containers. You can use this fence-agent without any authentication, or you can + use TLS authentication. + +Package: fence-agents-drac +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Dell DRAC 4 agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_drac is an I/O Fencing agent which can be used with the Dell Remote + Access Card (DRAC). This card provides remote access to controlling power to a + server. It logs into the DRAC through the telnet interface of the card. + +Package: fence-agents-drac5 +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client, + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Dell DRAC 5 agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_drac5 is an I/O Fencing agent which can be used with the Dell Remote + Access Card v5 or CMC (DRAC). This device provides remote access to controlling + power to a server. It logs into the DRAC through the telnet/ssh interface of + the card. + +Package: fence-agents-dummy +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}) +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - dummy agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + Fence agent used for testing purpose. + +Package: fence-agents-eaton-snmp +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + snmp +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Eaton SNMP agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_eaton_snmp is an I/O Fencing agent which can be used with the Eaton + network power switch. It logs into a device via SNMP and reboots a specified + outlet. It supports SNMP v1 and v3 with all combinations of + authenticity/privacy settings. + +Package: fence-agents-ecloud +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-requests +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - ANS eCloud agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_ecloud is a fence agent for use with the ANS eCloud platform which is + compatible with eCloud VPC and eCloud v1. + +Package: fence-agents-emerson +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}) +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Emerson SNMP agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_emerson is an I/O Fencing agent which can be used with MPX and MPH2 + managed rack PDU. + +Package: fence-agents-eps +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}) +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - ePowerSwitch agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_eps is an I/O Fencing agent which can be used with the ePowerSwitch 8M+ + power switch to fence connected machines. Fence agent works ONLY on 8M+ device, + because this is only one, which has support for hidden page feature. + +Package: fence-agents-gce +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), python3-googleapi, - python3-oauth2client, - python3-pycurl, + python3-socks +Suggests: python3-oauth2client +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Google Compute Engine agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_gce is an I/O Fencing agent for GCE (Google Cloud Engine). It uses the + googleapiclient library to connect to GCE. + +Package: fence-agents-hds-cb +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Hitachi Compute Blade agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_hds_cb is an I/O Fencing agent which can be used with Hitachi Compute + Blades with recent enough firmware that includes telnet support. + +Package: fence-agents-heuristics-ping +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + iputils-ping, +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - heuristics ping agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_heuristics_ping uses ping-heuristics to control execution of another + fence agent on the same fencing level. + . + This is not a fence agent by itself. Its only purpose is to enable/disable + another fence agent that lives on the same fencing level but after + fence_heuristics_ping. + +Package: fence-agents-hpblade +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client, + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - HPE BladeSystem agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_hpblade is an I/O Fencing agent which can be used with HPE BladeSystem + and HPE Integrity Superdome X. It logs into the onboard administrator of an + enclosure via telnet or ssh and uses the command line interface to power blades + or partitions on or off. + +Package: fence-agents-ibmblade +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + snmp +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - IBM BladeCenter SNMP agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_ibmblade is an I/O Fencing agent which can be used with IBM BladeCenter + chassis. It issues SNMP Set request to BladeCenter chassis, rebooting, powering + up or down the specified Blade Server. + +Package: fence-agents-ibm-powervs +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-pycurl +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - IBM PowerVS agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_ibm_powervs is an I/O Fencing agent which can be used with IBM PowerVS + to fence virtual machines. + +Package: fence-agents-ibm-vpc +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-pycurl +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - IBM Cloud VPC agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_ibm_vpc is an I/O Fencing agent which can be used with IBM Cloud VPC to + fence virtual machines. + +Package: fence-agents-ibmz +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-requests +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - IBM zSystems agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_ibmz is a power fencing agent which uses the HMC Web Services API to + fence IBM zSystems LPARs. + +Package: fence-agents-ifmib +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + snmp +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - IF-MIB SNMP agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_ifmib is an I/O Fencing agent which can be used with any SNMP IF-MIB + capable device. + . + It was written with managed ethernet switches in mind, in order to fence iSCSI + SAN connections. However, there are many devices that support the IF-MIB + interface. The agent uses IF-MIB::ifAdminStatus to control the state of an + interface. + +Package: fence-agents-ilo2 +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + gnutls-bin, + python3-pexpect, + python3-xmlschema +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - HP iLO2 agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + Fence agents for HP iLO2 devices that are accessed via the HTTP(s) protocol. + +Package: fence-agents-ilo-moonshot +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client, + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - HP Moonshot iLO agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + Fence agent for HP iLO Moonshot devices that are accessed via telnet or SSH. + +Package: fence-agents-ilo-mp +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client, + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - HP iLO MP agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + Fence agent for HP Integrated Lights-Out Management Processor devices that are + accessed via telnet or SSH. + +Package: fence-agents-ilo-ssh +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - HP iLO over SSH agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_ilo_ssh is a fence agent that connects to iLO device. It logs into + device via ssh and reboot a specified outlet. + +Package: fence-agents-intelmodular +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + snmp +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Intel Modular agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_intelmodular is an I/O Fencing agent which can be used with Intel + Modular device (tested on Intel MFSYS25, should work with MFSYS35 as well). + +Package: fence-agents-ipdu +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + snmp +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - IBM iPDU agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_ipdu is an I/O Fencing agent which can be used with the IBM iPDU network + power switch. It logs into a device via SNMP and reboots a specified outlet. It + supports SNMP v3 with all combinations of authenticity/privacy settings. + +Package: fence-agents-ipmilan +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + ipmitool +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - IPMI agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + Fence agents to manage nodes with available IPMI interface. + +Package: fence-agents-ironic +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-openstackclient +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - OpenStack Ironic agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_ironic is a Fencing agent which can be used with machines controlled by + the Ironic (Bare Metal as a service) service. This agent calls the openstack + CLI. + +Package: fence-agents-kdump +Architecture: any +Depends: ${shlibs:Depends}, + ${misc:Depends}, + fence-agents-common (>= ${source:Version}) +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - kdump agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_kdump is an I/O fencing agent to be used with the kdump crash recovery + service. When the fence_kdump agent is invoked, it will listen for a message + from the failed node that acknowledges that the failed node it executing the + kdump crash kernel. Note that fence_kdump is not a replacement for traditional + fencing methods. The fence_kdump agent can only detect that a node has entered + the kdump crash recovery service. This allows the kdump crash recovery service + complete without being preempted by traditional power fencing methods. + +Package: fence-agents-kubevirt +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-kubernetes, + python3-openshift +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - KubeVirt agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_kubevirt is an I/O Fencing agent for KubeVirt. + +Package: fence-agents-ldom +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client, + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Sun LDom agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_ldom is an I/O Fencing agent which can be used with LDoms virtual + machines. This agent works so, that run ldm command on host machine. + +Package: fence-agents-lindy-pdu +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + snmp +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Lindy PDU agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_lindypdu is an I/O Fencing agent which can be used with the Lindy PDU + network power switch. It logs into a device via SNMP and reboots a specified + outlet. It supports SNMP v1 with all combinations of authenticity/privacy + settings. + +Package: fence-agents-lpar +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client, + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - IBM LPAR agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + Fence agent for IBM LPAR devices that are accessed via telnet or SSH. + +Package: fence-agents-mpath +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + multipath-tools +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - multipath reservation agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_mpath is an I/O fencing agent that uses SCSI-3 persistent reservations + to control access multipath devices. Underlying devices must support SCSI-3 + persistent reservations (SPC-3 or greater) as well as the "preempt-and-abort" + subcommand. + +Package: fence-agents-netio +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client, + python3-pexpect, + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Koukaam NETIO-230B agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + This package provides an I/O Fencing agent which can be used with the Koukaam + NETIO-230B Power Distribution Unit. It logs into device via telnet and reboots + a specified outlet. Lengthy telnet connections should be avoided while the + cluster is running because the connection will block any necessary fencing + actions. + +Package: fence-agents-openstack +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-novaclient, + python3-yaml +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - OpenStack Nova agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_openstack is a Fencing agent which can be used with machines controlled + by the OpenStack's Nova service. + +Package: fence-agents-ovh +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-suds +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - OVH agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_ovh is an Power Fencing agent which can be used within OVH datecentre. + Poweroff is simulated with a reboot into rescue-pro mode. + +Package: fence-agents-powerman +Architecture: all +Depends: ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + powerman +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Powerman agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + This package provides a fence agent for the Powerman management utility that + was designed for LLNL systems. + +Package: fence-agents-pve +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-pycurl +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Proxmox VE agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_pve agent can be used to fence virtual machines acting as nodes in a + virtualized cluster. + +Package: fence-agents-raritan +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), python3-pexpect, + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Raritan Dominion PX agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_raritan is an I/O Fencing agent which can be used with the Raritan + DPXS12-20 Power Distribution Unit. It logs into device via telnet and reboots a + specified outlet. Lengthy telnet connections should be avoided while a GFS + cluster is running because the connection will block any necessary fencing + actions. + +Package: fence-agents-raritan-px3 +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client, + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Raritan Dominion PX2/PX3 agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_raritan is an I/O Fencing agent which can be used with the Raritan PX2 + and PX3 Power Distribution Unit series. It logs into device via telnet or ssh + and reboots a specified outlet. Single outlets and grouped outlets are + supported. + +Package: fence-agents-rcd-serial +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}) +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - RCD serial agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_rcd_serial operates a serial cable that toggles a reset of an opposing + server using the reset switch on its motherboard. The cable itself is simple + with no power, network or moving parts. + +Package: fence-agents-redfish +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-requests +Suggests: python3-urllib3 +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Redfish agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_redfish is an I/O Fencing agent which can be used with Out-of-Band + controllers that support Redfish APIs. These controllers provide remote access + to control power on a server. + +Package: fence-agents-rhevm +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-pycurl +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - RHEV-M REST API agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_rhevm is an I/O Fencing agent which can be used with RHEV-M REST API to + fence virtual machines. + +Package: fence-agents-rsa +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client, + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - IBM RSA agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_rsa is an I/O Fencing agent which can be used with the IBM RSA II + management interface. It logs into an RSA II device via telnet and reboots the + associated machine. Lengthy telnet connections to the RSA II device should be + avoided while a GFS cluster is running because the connection will block any + necessary fencing actions. + +Package: fence-agents-rsb +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client, + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Fujitsu-Siemens RSB agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_rsb is an I/O Fencing agent which can be used with the Fujitsu-Siemens + RSB management interface. It logs into device via telnet/ssh and reboots a + specified outlet. Lengthy telnet/ssh connections should be avoided while a GFS + cluster is running because the connection will block any necessary fencing + actions. + +Package: fence-agents-sanbox2 +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-pexpect +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - QLogic SANBox2 FC switch agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_sanbox2 is an I/O Fencing agent which can be used with QLogic SANBox2 FC + switches. It logs into a SANBox2 switch via telnet and disables a specified + port. + +Package: fence-agents-sbd +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + sbd +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - STONITH Block Device agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_sbd is I/O Fencing agent which can be used in environments where sbd can + be used (shared storage). + +Package: fence-agents-scsi +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + sg3-utils +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - SCSI-3 reservation agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_scsi is an I/O fencing agent that uses SCSI-3 persistent reservations to + control access to shared storage devices. These devices must support SCSI-3 + persistent reservations (SPC-3 or greater) as well as the "preempt-and-abort" + subcommand. + +Package: fence-agents-skalar +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-requests, + python3-urllib3, +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Skala-R agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + Fence agent used to manage nodes in Skala-R. + +Package: fence-agents-vbox +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - VirtualBox agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_vbox is an I/O Fencing agent which can be used with the virtual machines + managed by VirtualBox. It logs via ssh to a dom0 where it runs VBoxManage to do + all of the work. + +Package: fence-agents-virsh +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - virsh agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_virsh is an I/O Fencing agent which can be used with the virtual + machines managed by libvirt. It logs via ssh to a dom0 and there run virsh + command, which does all work. + +Package: fence-agents-vmware +Architecture: all +Depends: ${misc:Depends}, + ${perl:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-pexpect +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - VMware agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + This package provides an I/O Fencing agent which can be used with the VMware + ESX, VMware ESXi or VMware Server to fence virtual machines. + . + Before using this agent, VI Perl Toolkit or vmrun command needs to be + installed on every machine running this agent. + +Package: fence-agents-vmware-rest +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-pycurl +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - VMware REST API agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_vmware_rest is an I/O Fencing agent which can be used with VMware API to + fence virtual machines. + +Package: fence-agents-vmware-soap +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), python3-requests, python3-suds -Breaks: cman (<= 3.0.12-2ubuntu4) -Replaces: cman (<= 3.0.12-2ubuntu4) -Recommends: libnet-telnet-perl, - openssh-client, - sg3-utils, - snmp -Suggests: fence-virt, -# Needed by fence_azure_arm: - python3-adal, - python3-azure, -# Needed by fence_openstack: - python3-keystoneauth1, - python3-keystoneclient, - python3-novaclient, -# Needed by fence_kubevirt: - python3-kubernetes, -Description: Fence Agents for Red Hat Cluster - Red Hat Fence Agents is a collection of scripts to handle remote - power management for several devices. They allow failed or - unreachable nodes to be forcibly restarted and removed from the - cluster. - . - Fence agents included: - ${agents} +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - VMware SOAP API agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_vmware_soap is an I/O Fencing agent which can be used with the virtual + machines managed by VMWare products that have SOAP API v4.1+. + +Package: fence-agents-vmware-vcloud +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-pycurl +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - VMware vCloud Director API agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_vmware_vcloud is an I/O Fencing agent which can be used with VMware + vCloud Director API to fence virtual machines. + +Package: fence-agents-wti +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + openssh-client, + python3-pexpect, + telnet +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - WTI Network Power Switch agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_wti is an I/O Fencing agent which can be used with the WTI Network Power + Switch (NPS). It logs into an NPS via telnet or ssh and boots a specified plug. + Lengthy telnet connections to the NPS should be avoided while a GFS cluster is + running because the connection will block any necessary fencing actions. + +Package: fence-agents-xenapi +Architecture: all +Depends: ${shlibs:Depends}, + ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}), + python3-pexpect +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - Citrix XenServer agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + fence_xenapi is an I/O Fencing agent used on Citrix XenServer hosts. It uses + the XenAPI, supplied by Citrix, to establish an XML-RPC session to a XenServer + host. Once the session is established, further XML-RPC commands are issued in + order to switch on, switch off, restart and query the status of virtual + machines running on the host. + +Package: fence-agents-zvm +Architecture: all +Depends: ${misc:Depends}, + ${python3:Depends}, + fence-agents-common (>= ${source:Version}) +Breaks: fence-agents (<< 4.12.1-2~exp1) +Replaces: fence-agents (<< 4.12.1-2~exp1) +Description: Fence Agents for Red Hat Cluster - IBM z/VM agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . + This package provides a fencing agent for z/VM virtual machines using SMAPI + service over TCP/IP. Package: fence-virt Architecture: any -Depends: ${shlibs:Depends}, ${misc:Depends} -Description: Pluggable fencing framework for virtual machines - agent +Depends: ${shlibs:Depends}, + ${misc:Depends}, + fence-agents-common (>= ${source:Version}) +Description: Fence Agents for Red Hat Cluster - virt agent + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . The fencing framework consists of the agent (fence_virt) and the host daemon (fence_virtd). The fence_virtd host daemon is responsible for processing fencing requests from fence_virt agents @@ -95,9 +1469,15 @@ Description: Pluggable fencing framework for virtual machines - agent Package: fence-virtd Architecture: any -Depends: ${shlibs:Depends}, ${misc:Depends} +Depends: ${shlibs:Depends}, + ${misc:Depends}, + fence-agents-common (>= ${source:Version}) Pre-Depends: ${misc:Pre-Depends} -Description: Pluggable fencing framework for virtual machines - daemon +Description: Fence Agents for Red Hat Cluster - virt daemon + Red Hat Fence Agents is a collection of scripts to handle remote power + management for several devices. They allow failed or unreachable nodes to be + forcibly restarted and removed from the cluster. + . The fencing framework consists of the agent (fence_virt) and the host daemon (fence_virtd). The fence_virtd host daemon is responsible for processing fencing requests from fence_virt agents diff --git a/debian/fence-agents-ack-manual.install b/debian/fence-agents-ack-manual.install new file mode 100644 index 0000000..345ddba --- /dev/null +++ b/debian/fence-agents-ack-manual.install @@ -0,0 +1,2 @@ +usr/sbin/fence_ack_manual +usr/share/man/man8/fence_ack_manual.8* diff --git a/debian/fence-agents-aliyun.install b/debian/fence-agents-aliyun.install new file mode 100644 index 0000000..6ef70c2 --- /dev/null +++ b/debian/fence-agents-aliyun.install @@ -0,0 +1,2 @@ +usr/sbin/fence_aliyun +usr/share/man/man8/fence_aliyun.8* diff --git a/debian/fence-agents-alom.install b/debian/fence-agents-alom.install new file mode 100644 index 0000000..c8e9aaa --- /dev/null +++ b/debian/fence-agents-alom.install @@ -0,0 +1,2 @@ +usr/sbin/fence_alom +usr/share/man/man8/fence_alom.8* diff --git a/debian/fence-agents-amt.install b/debian/fence-agents-amt.install new file mode 100644 index 0000000..5422b13 --- /dev/null +++ b/debian/fence-agents-amt.install @@ -0,0 +1,2 @@ +usr/sbin/fence_amt +usr/share/man/man8/fence_amt.8* diff --git a/debian/fence-agents-apc-snmp.docs b/debian/fence-agents-apc-snmp.docs new file mode 100644 index 0000000..fcf1455 --- /dev/null +++ b/debian/fence-agents-apc-snmp.docs @@ -0,0 +1 @@ +agents/apc_snmp/README diff --git a/debian/fence-agents-apc-snmp.install b/debian/fence-agents-apc-snmp.install new file mode 100644 index 0000000..a56ba13 --- /dev/null +++ b/debian/fence-agents-apc-snmp.install @@ -0,0 +1,5 @@ +usr/sbin/fence_apc_snmp +usr/sbin/fence_tripplite_snmp +usr/share/man/man8/fence_apc_snmp.8* +usr/share/man/man8/fence_tripplite_snmp.8* +agents/apc_snmp/powernet369.mib usr/share/snmp/mibs diff --git a/debian/fence-agents-apc.install b/debian/fence-agents-apc.install new file mode 100644 index 0000000..406d5a0 --- /dev/null +++ b/debian/fence-agents-apc.install @@ -0,0 +1,2 @@ +usr/sbin/fence_apc +usr/share/man/man8/fence_apc.8* diff --git a/debian/fence-agents-aws.install b/debian/fence-agents-aws.install new file mode 100644 index 0000000..bc21419 --- /dev/null +++ b/debian/fence-agents-aws.install @@ -0,0 +1,2 @@ +usr/sbin/fence_aws +usr/share/man/man8/fence_aws.8* diff --git a/debian/fence-agents-azure-arm.install b/debian/fence-agents-azure-arm.install new file mode 100644 index 0000000..29314f1 --- /dev/null +++ b/debian/fence-agents-azure-arm.install @@ -0,0 +1,3 @@ +usr/sbin/fence_azure_arm +usr/share/fence/azure_fence.py +usr/share/man/man8/fence_azure_arm.8* diff --git a/debian/fence-agents-bladecenter.install b/debian/fence-agents-bladecenter.install new file mode 100644 index 0000000..1b6ff47 --- /dev/null +++ b/debian/fence-agents-bladecenter.install @@ -0,0 +1,2 @@ +usr/sbin/fence_bladecenter +usr/share/man/man8/fence_bladecenter.8* diff --git a/debian/fence-agents-brocade.install b/debian/fence-agents-brocade.install new file mode 100644 index 0000000..d56f6ea --- /dev/null +++ b/debian/fence-agents-brocade.install @@ -0,0 +1,2 @@ +usr/sbin/fence_brocade +usr/share/man/man8/fence_brocade.8* diff --git a/debian/fence-agents-cdu.install b/debian/fence-agents-cdu.install new file mode 100644 index 0000000..00fac3c --- /dev/null +++ b/debian/fence-agents-cdu.install @@ -0,0 +1,2 @@ +usr/sbin/fence_cdu +usr/share/man/man8/fence_cdu.8* diff --git a/debian/fence-agents-cisco-mds.install b/debian/fence-agents-cisco-mds.install new file mode 100644 index 0000000..84b8d96 --- /dev/null +++ b/debian/fence-agents-cisco-mds.install @@ -0,0 +1,2 @@ +usr/sbin/fence_cisco_mds +usr/share/man/man8/fence_cisco_mds.8* diff --git a/debian/fence-agents-cisco-ucs.install b/debian/fence-agents-cisco-ucs.install new file mode 100644 index 0000000..4709298 --- /dev/null +++ b/debian/fence-agents-cisco-ucs.install @@ -0,0 +1,2 @@ +usr/sbin/fence_cisco_ucs +usr/share/man/man8/fence_cisco_ucs.8* diff --git a/debian/fence-agents.docs b/debian/fence-agents-common.docs index 37737c2..37737c2 100644 --- a/debian/fence-agents.docs +++ b/debian/fence-agents-common.docs diff --git a/debian/fence-agents-common.install b/debian/fence-agents-common.install new file mode 100644 index 0000000..c01dae6 --- /dev/null +++ b/debian/fence-agents-common.install @@ -0,0 +1,5 @@ +usr/lib/tmpfiles.d/fence-agents.conf +usr/share/cluster/relaxng* +usr/share/doc +usr/share/fence/fencing* +usr/share/pkgconfig/fence-agents.pc diff --git a/debian/fence-agents-compute.install b/debian/fence-agents-compute.install new file mode 100644 index 0000000..56cec9a --- /dev/null +++ b/debian/fence-agents-compute.install @@ -0,0 +1,4 @@ +usr/sbin/fence_compute +usr/sbin/fence_evacuate +usr/share/man/man8/fence_compute.8* +usr/share/man/man8/fence_evacuate.8* diff --git a/debian/fence-agents-crosslink.doc b/debian/fence-agents-crosslink.doc new file mode 100644 index 0000000..38f18b4 --- /dev/null +++ b/debian/fence-agents-crosslink.doc @@ -0,0 +1 @@ +agents/crosslink/README.md diff --git a/debian/fence-agents-crosslink.install b/debian/fence-agents-crosslink.install new file mode 100644 index 0000000..35d2f33 --- /dev/null +++ b/debian/fence-agents-crosslink.install @@ -0,0 +1,2 @@ +usr/sbin/fence_crosslink +usr/share/man/man8/fence_crosslink.8* diff --git a/debian/fence-agents-cyberpower-ssh.install b/debian/fence-agents-cyberpower-ssh.install new file mode 100644 index 0000000..2f3604a --- /dev/null +++ b/debian/fence-agents-cyberpower-ssh.install @@ -0,0 +1,2 @@ +usr/sbin/fence_cyberpower_ssh +usr/share/man/man8/fence_cyberpower_ssh.8* diff --git a/debian/fence-agents-docker.install b/debian/fence-agents-docker.install new file mode 100644 index 0000000..f332c37 --- /dev/null +++ b/debian/fence-agents-docker.install @@ -0,0 +1,2 @@ +usr/sbin/fence_docker +usr/share/man/man8/fence_docker.8* diff --git a/debian/fence-agents-drac.install b/debian/fence-agents-drac.install new file mode 100644 index 0000000..ff2fadf --- /dev/null +++ b/debian/fence-agents-drac.install @@ -0,0 +1,2 @@ +usr/sbin/fence_drac +usr/share/man/man8/fence_drac.8* diff --git a/debian/fence-agents-drac5.install b/debian/fence-agents-drac5.install new file mode 100644 index 0000000..a484b3f --- /dev/null +++ b/debian/fence-agents-drac5.install @@ -0,0 +1,2 @@ +usr/sbin/fence_drac5 +usr/share/man/man8/fence_drac5.8* diff --git a/debian/fence-agents-dummy.install b/debian/fence-agents-dummy.install new file mode 100644 index 0000000..291ba20 --- /dev/null +++ b/debian/fence-agents-dummy.install @@ -0,0 +1,2 @@ +usr/sbin/fence_dummy +usr/share/man/man8/fence_dummy.8* diff --git a/debian/fence-agents-eaton-snmp.install b/debian/fence-agents-eaton-snmp.install new file mode 100644 index 0000000..1d73d32 --- /dev/null +++ b/debian/fence-agents-eaton-snmp.install @@ -0,0 +1,2 @@ +usr/sbin/fence_eaton_snmp +usr/share/man/man8/fence_eaton_snmp.8* diff --git a/debian/fence-agents-ecloud.install b/debian/fence-agents-ecloud.install new file mode 100644 index 0000000..5087396 --- /dev/null +++ b/debian/fence-agents-ecloud.install @@ -0,0 +1,2 @@ +usr/sbin/fence_ecloud +usr/share/man/man8/fence_ecloud.8* diff --git a/debian/fence-agents-emerson.install b/debian/fence-agents-emerson.install new file mode 100644 index 0000000..dff7c0d --- /dev/null +++ b/debian/fence-agents-emerson.install @@ -0,0 +1,2 @@ +usr/sbin/fence_emerson +usr/share/man/man8/fence_emerson.8* diff --git a/debian/fence-agents-eps.install b/debian/fence-agents-eps.install new file mode 100644 index 0000000..db84ff9 --- /dev/null +++ b/debian/fence-agents-eps.install @@ -0,0 +1,2 @@ +usr/sbin/fence_eps +usr/share/man/man8/fence_eps.8* diff --git a/debian/fence-agents-gce.install b/debian/fence-agents-gce.install new file mode 100644 index 0000000..c7d144f --- /dev/null +++ b/debian/fence-agents-gce.install @@ -0,0 +1,2 @@ +usr/sbin/fence_gce +usr/share/man/man8/fence_gce.8* diff --git a/debian/fence-agents-hds-cb.install b/debian/fence-agents-hds-cb.install new file mode 100644 index 0000000..745e7b9 --- /dev/null +++ b/debian/fence-agents-hds-cb.install @@ -0,0 +1,2 @@ +usr/sbin/fence_hds_cb +usr/share/man/man8/fence_hds_cb.8* diff --git a/debian/fence-agents-heuristics-ping.install b/debian/fence-agents-heuristics-ping.install new file mode 100644 index 0000000..f481b56 --- /dev/null +++ b/debian/fence-agents-heuristics-ping.install @@ -0,0 +1,2 @@ +usr/sbin/fence_heuristics_ping +usr/share/man/man8/fence_heuristics_ping.8* diff --git a/debian/fence-agents-hpblade.install b/debian/fence-agents-hpblade.install new file mode 100644 index 0000000..ca88412 --- /dev/null +++ b/debian/fence-agents-hpblade.install @@ -0,0 +1,2 @@ +usr/sbin/fence_hpblade +usr/share/man/man8/fence_hpblade.8* diff --git a/debian/fence-agents-ibm-powervs.install b/debian/fence-agents-ibm-powervs.install new file mode 100644 index 0000000..9445e19 --- /dev/null +++ b/debian/fence-agents-ibm-powervs.install @@ -0,0 +1,2 @@ +usr/sbin/fence_ibm_powervs +usr/share/man/man8/fence_ibm_powervs.8* diff --git a/debian/fence-agents-ibm-vpc.install b/debian/fence-agents-ibm-vpc.install new file mode 100644 index 0000000..f88ee29 --- /dev/null +++ b/debian/fence-agents-ibm-vpc.install @@ -0,0 +1,2 @@ +usr/sbin/fence_ibm_vpc +usr/share/man/man8/fence_ibm_vpc.8* diff --git a/debian/fence-agents-ibmblade.install b/debian/fence-agents-ibmblade.install new file mode 100644 index 0000000..6453981 --- /dev/null +++ b/debian/fence-agents-ibmblade.install @@ -0,0 +1,2 @@ +usr/sbin/fence_ibmblade +usr/share/man/man8/fence_ibmblade.8* diff --git a/debian/fence-agents-ibmz.install b/debian/fence-agents-ibmz.install new file mode 100644 index 0000000..4523da1 --- /dev/null +++ b/debian/fence-agents-ibmz.install @@ -0,0 +1,2 @@ +usr/sbin/fence_ibmz +usr/share/man/man8/fence_ibmz.8* diff --git a/debian/fence-agents-ifmib.install b/debian/fence-agents-ifmib.install new file mode 100644 index 0000000..fa8cc4b --- /dev/null +++ b/debian/fence-agents-ifmib.install @@ -0,0 +1,2 @@ +usr/sbin/fence_ifmib +usr/share/man/man8/fence_ifmib.8* diff --git a/debian/fence-agents-ilo-moonshot.install b/debian/fence-agents-ilo-moonshot.install new file mode 100644 index 0000000..20c7e16 --- /dev/null +++ b/debian/fence-agents-ilo-moonshot.install @@ -0,0 +1,2 @@ +usr/sbin/fence_ilo_moonshot +usr/share/man/man8/fence_ilo_moonshot.8* diff --git a/debian/fence-agents-ilo-mp.install b/debian/fence-agents-ilo-mp.install new file mode 100644 index 0000000..a35b055 --- /dev/null +++ b/debian/fence-agents-ilo-mp.install @@ -0,0 +1,2 @@ +usr/sbin/fence_ilo_mp +usr/share/man/man8/fence_ilo_mp.8* diff --git a/debian/fence-agents-ilo-ssh.install b/debian/fence-agents-ilo-ssh.install new file mode 100644 index 0000000..5259f0d --- /dev/null +++ b/debian/fence-agents-ilo-ssh.install @@ -0,0 +1,8 @@ +usr/sbin/fence_ilo_ssh +usr/sbin/fence_ilo3_ssh +usr/sbin/fence_ilo4_ssh +usr/sbin/fence_ilo5_ssh +usr/share/man/man8/fence_ilo_ssh.8* +usr/share/man/man8/fence_ilo3_ssh.8* +usr/share/man/man8/fence_ilo4_ssh.8* +usr/share/man/man8/fence_ilo5_ssh.8* diff --git a/debian/fence-agents-ilo2.install b/debian/fence-agents-ilo2.install new file mode 100644 index 0000000..bbb2310 --- /dev/null +++ b/debian/fence-agents-ilo2.install @@ -0,0 +1,4 @@ +usr/sbin/fence_ilo +usr/sbin/fence_ilo2 +usr/share/man/man8/fence_ilo.8* +usr/share/man/man8/fence_ilo2.8* diff --git a/debian/fence-agents-intelmodular.install b/debian/fence-agents-intelmodular.install new file mode 100644 index 0000000..b2cffed --- /dev/null +++ b/debian/fence-agents-intelmodular.install @@ -0,0 +1,2 @@ +usr/sbin/fence_intelmodular +usr/share/man/man8/fence_intelmodular.8* diff --git a/debian/fence-agents-ipdu.install b/debian/fence-agents-ipdu.install new file mode 100644 index 0000000..729b186 --- /dev/null +++ b/debian/fence-agents-ipdu.install @@ -0,0 +1,2 @@ +usr/sbin/fence_ipdu +usr/share/man/man8/fence_ipdu.8* diff --git a/debian/fence-agents-ipmilan.install b/debian/fence-agents-ipmilan.install new file mode 100644 index 0000000..0717986 --- /dev/null +++ b/debian/fence-agents-ipmilan.install @@ -0,0 +1,14 @@ +usr/sbin/fence_ipmilan +usr/sbin/fence_idrac +usr/sbin/fence_ilo3 +usr/sbin/fence_ilo4 +usr/sbin/fence_ilo5 +usr/sbin/fence_ipmilanplus +usr/sbin/fence_imm +usr/share/man/man8/fence_ipmilan.8* +usr/share/man/man8/fence_idrac.8* +usr/share/man/man8/fence_ilo3.8* +usr/share/man/man8/fence_ilo4.8* +usr/share/man/man8/fence_ilo5.8* +usr/share/man/man8/fence_ipmilanplus.8* +usr/share/man/man8/fence_imm.8* diff --git a/debian/fence-agents-ironic.install b/debian/fence-agents-ironic.install new file mode 100644 index 0000000..53e2355 --- /dev/null +++ b/debian/fence-agents-ironic.install @@ -0,0 +1,2 @@ +usr/sbin/fence_ironic +usr/share/man/man8/fence_ironic.8* diff --git a/debian/fence-agents-kdump.install b/debian/fence-agents-kdump.install new file mode 100644 index 0000000..3eea248 --- /dev/null +++ b/debian/fence-agents-kdump.install @@ -0,0 +1,4 @@ +usr/libexec/fence-agents/fence_kdump_send +usr/sbin/fence_kdump +usr/share/man/man8/fence_kdump.8* +usr/share/man/man8/fence_kdump_send.8* diff --git a/debian/fence-agents-kubevirt.install b/debian/fence-agents-kubevirt.install new file mode 100644 index 0000000..02f4239 --- /dev/null +++ b/debian/fence-agents-kubevirt.install @@ -0,0 +1,2 @@ +usr/sbin/fence_kubevirt +usr/share/man/man8/fence_kubevirt.8* diff --git a/debian/fence-agents-ldom.install b/debian/fence-agents-ldom.install new file mode 100644 index 0000000..89aa5ef --- /dev/null +++ b/debian/fence-agents-ldom.install @@ -0,0 +1,2 @@ +usr/sbin/fence_ldom +usr/share/man/man8/fence_ldom.8* diff --git a/debian/fence-agents-lindy-pdu.install b/debian/fence-agents-lindy-pdu.install new file mode 100644 index 0000000..1ffa23a --- /dev/null +++ b/debian/fence-agents-lindy-pdu.install @@ -0,0 +1,2 @@ +usr/sbin/fence_lindypdu +usr/share/man/man8/fence_lindypdu.8* diff --git a/debian/fence-agents-lpar.install b/debian/fence-agents-lpar.install new file mode 100644 index 0000000..9c02907 --- /dev/null +++ b/debian/fence-agents-lpar.install @@ -0,0 +1,2 @@ +usr/sbin/fence_lpar +usr/share/man/man8/fence_lpar.8* diff --git a/debian/fence-agents-mpath.install b/debian/fence-agents-mpath.install new file mode 100644 index 0000000..19f025e --- /dev/null +++ b/debian/fence-agents-mpath.install @@ -0,0 +1,3 @@ +usr/sbin/fence_mpath +usr/share/cluster/fence_mpath* +usr/share/man/man8/fence_mpath.8* diff --git a/debian/fence-agents-netio.install b/debian/fence-agents-netio.install new file mode 100644 index 0000000..fc70241 --- /dev/null +++ b/debian/fence-agents-netio.install @@ -0,0 +1,2 @@ +usr/sbin/fence_netio +usr/share/man/man8/fence_netio.8* diff --git a/debian/fence-agents-openstack.install b/debian/fence-agents-openstack.install new file mode 100644 index 0000000..7c36c48 --- /dev/null +++ b/debian/fence-agents-openstack.install @@ -0,0 +1,2 @@ +usr/sbin/fence_openstack +usr/share/man/man8/fence_openstack.8* diff --git a/debian/fence-agents-ovh.install b/debian/fence-agents-ovh.install new file mode 100644 index 0000000..506ddf5 --- /dev/null +++ b/debian/fence-agents-ovh.install @@ -0,0 +1,2 @@ +usr/sbin/fence_ovh +usr/share/man/man8/fence_ovh.8* diff --git a/debian/fence-agents-powerman.install b/debian/fence-agents-powerman.install new file mode 100644 index 0000000..7f36bde --- /dev/null +++ b/debian/fence-agents-powerman.install @@ -0,0 +1,2 @@ +usr/sbin/fence_powerman +usr/share/man/man8/fence_powerman.8* diff --git a/debian/fence-agents-pve.install b/debian/fence-agents-pve.install new file mode 100644 index 0000000..0f04292 --- /dev/null +++ b/debian/fence-agents-pve.install @@ -0,0 +1,2 @@ +usr/sbin/fence_pve +usr/share/man/man8/fence_pve.8* diff --git a/debian/fence-agents-raritan-px3.install b/debian/fence-agents-raritan-px3.install new file mode 100644 index 0000000..aaa3725 --- /dev/null +++ b/debian/fence-agents-raritan-px3.install @@ -0,0 +1,2 @@ +usr/sbin/fence_raritan_px3 +usr/share/man/man8/fence_raritan_px3.8* diff --git a/debian/fence-agents-raritan.install b/debian/fence-agents-raritan.install new file mode 100644 index 0000000..cc5ce0b --- /dev/null +++ b/debian/fence-agents-raritan.install @@ -0,0 +1,2 @@ +usr/sbin/fence_raritan +usr/share/man/man8/fence_raritan.8* diff --git a/debian/fence-agents-rcd-serial.install b/debian/fence-agents-rcd-serial.install new file mode 100644 index 0000000..09a6525 --- /dev/null +++ b/debian/fence-agents-rcd-serial.install @@ -0,0 +1,2 @@ +usr/sbin/fence_rcd_serial +usr/share/man/man8/fence_rcd_serial.8* diff --git a/debian/fence-agents-redfish.install b/debian/fence-agents-redfish.install new file mode 100644 index 0000000..28dc690 --- /dev/null +++ b/debian/fence-agents-redfish.install @@ -0,0 +1,2 @@ +usr/sbin/fence_redfish +usr/share/man/man8/fence_redfish.8* diff --git a/debian/fence-agents-rhevm.install b/debian/fence-agents-rhevm.install new file mode 100644 index 0000000..5a7fad5 --- /dev/null +++ b/debian/fence-agents-rhevm.install @@ -0,0 +1,2 @@ +usr/sbin/fence_rhevm +usr/share/man/man8/fence_rhevm.8* diff --git a/debian/fence-agents-rsa.install b/debian/fence-agents-rsa.install new file mode 100644 index 0000000..6a0a9cf --- /dev/null +++ b/debian/fence-agents-rsa.install @@ -0,0 +1,2 @@ +usr/sbin/fence_rsa +usr/share/man/man8/fence_rsa.8* diff --git a/debian/fence-agents-rsb.install b/debian/fence-agents-rsb.install new file mode 100644 index 0000000..4b4eac9 --- /dev/null +++ b/debian/fence-agents-rsb.install @@ -0,0 +1,2 @@ +usr/sbin/fence_rsb +usr/share/man/man8/fence_rsb.8* diff --git a/debian/fence-agents-sanbox2.install b/debian/fence-agents-sanbox2.install new file mode 100644 index 0000000..4432a3c --- /dev/null +++ b/debian/fence-agents-sanbox2.install @@ -0,0 +1,2 @@ +usr/sbin/fence_sanbox2 +usr/share/man/man8/fence_sanbox2.8* diff --git a/debian/fence-agents-sbd.install b/debian/fence-agents-sbd.install new file mode 100644 index 0000000..a89b211 --- /dev/null +++ b/debian/fence-agents-sbd.install @@ -0,0 +1,2 @@ +usr/sbin/fence_sbd +usr/share/man/man8/fence_sbd.8* diff --git a/debian/fence-agents-scsi.install b/debian/fence-agents-scsi.install new file mode 100644 index 0000000..d92d07a --- /dev/null +++ b/debian/fence-agents-scsi.install @@ -0,0 +1,3 @@ +usr/sbin/fence_scsi +usr/share/cluster/fence_scsi* +usr/share/man/man8/fence_scsi.8* diff --git a/debian/fence-agents-skalar.install b/debian/fence-agents-skalar.install new file mode 100644 index 0000000..76b5665 --- /dev/null +++ b/debian/fence-agents-skalar.install @@ -0,0 +1,2 @@ +usr/sbin/fence_skalar +usr/share/man/man8/fence_skalar.8* diff --git a/debian/fence-agents-vbox.install b/debian/fence-agents-vbox.install new file mode 100644 index 0000000..0894b50 --- /dev/null +++ b/debian/fence-agents-vbox.install @@ -0,0 +1,2 @@ +usr/sbin/fence_vbox +usr/share/man/man8/fence_vbox.8* diff --git a/debian/fence-agents-virsh.install b/debian/fence-agents-virsh.install new file mode 100644 index 0000000..f5db142 --- /dev/null +++ b/debian/fence-agents-virsh.install @@ -0,0 +1,2 @@ +usr/sbin/fence_virsh +usr/share/man/man8/fence_virsh.8* diff --git a/debian/fence-agents-vmware-rest.install b/debian/fence-agents-vmware-rest.install new file mode 100644 index 0000000..e2995c2 --- /dev/null +++ b/debian/fence-agents-vmware-rest.install @@ -0,0 +1,2 @@ +usr/sbin/fence_vmware_rest +usr/share/man/man8/fence_vmware_rest.8* diff --git a/debian/fence-agents-vmware-soap.install b/debian/fence-agents-vmware-soap.install new file mode 100644 index 0000000..cdb3376 --- /dev/null +++ b/debian/fence-agents-vmware-soap.install @@ -0,0 +1,2 @@ +usr/sbin/fence_vmware_soap +usr/share/man/man8/fence_vmware_soap.8* diff --git a/debian/fence-agents-vmware-vcloud.install b/debian/fence-agents-vmware-vcloud.install new file mode 100644 index 0000000..13402cc --- /dev/null +++ b/debian/fence-agents-vmware-vcloud.install @@ -0,0 +1,2 @@ +usr/sbin/fence_vmware_vcloud +usr/share/man/man8/fence_vmware_vcloud.8* diff --git a/debian/fence-agents-vmware.install b/debian/fence-agents-vmware.install new file mode 100644 index 0000000..fee4d44 --- /dev/null +++ b/debian/fence-agents-vmware.install @@ -0,0 +1,2 @@ +usr/sbin/fence_vmware +usr/share/man/man8/fence_vmware.8* diff --git a/debian/fence-agents-wti.install b/debian/fence-agents-wti.install new file mode 100644 index 0000000..bac24bd --- /dev/null +++ b/debian/fence-agents-wti.install @@ -0,0 +1,2 @@ +usr/sbin/fence_wti +usr/share/man/man8/fence_wti.8* diff --git a/debian/fence-agents-xenapi.install b/debian/fence-agents-xenapi.install new file mode 100644 index 0000000..bf2164e --- /dev/null +++ b/debian/fence-agents-xenapi.install @@ -0,0 +1,3 @@ +usr/sbin/fence_xenapi +usr/share/fence/XenAPI.py +usr/share/man/man8/fence_xenapi.8* diff --git a/debian/fence-agents-zvm.install b/debian/fence-agents-zvm.install new file mode 100644 index 0000000..4037149 --- /dev/null +++ b/debian/fence-agents-zvm.install @@ -0,0 +1,2 @@ +usr/sbin/fence_zvmip +usr/share/man/man8/fence_zvmip.8* diff --git a/debian/fence-agents.install b/debian/fence-agents.install deleted file mode 100644 index 61a726a..0000000 --- a/debian/fence-agents.install +++ /dev/null @@ -1,9 +0,0 @@ -usr/lib/tmpfiles.d/fence-agents.conf -usr/libexec/fence-agents/fence_kdump_send -usr/sbin/fence* -usr/share/cluster/fence* -usr/share/cluster/relaxng* -usr/share/doc -usr/share/fence* -usr/share/man/man8/fence* -usr/share/pkgconfig/fence-agents.pc diff --git a/debian/patches/enable-zvm-agent b/debian/patches/enable-zvm-agent deleted file mode 100644 index 4b50e40..0000000 --- a/debian/patches/enable-zvm-agent +++ /dev/null @@ -1,17 +0,0 @@ -Description: Leave zvm enabled - Remove agent after bookworm release. -Author: Valentin Vidic <vvidic@debian.org> -Last-Update: 2023-01-14 ---- -This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ ---- a/configure.ac -+++ b/configure.ac -@@ -196,7 +196,7 @@ - fi - - FENCE_ZVM=0 --if echo "$AGENTS_LIST" | grep -q -E "zvm( |$)"; then -+if echo "$AGENTS_LIST" | grep -q -E "all|zvm( |$)"; then - FENCE_ZVM=1 - fi - diff --git a/debian/patches/fence-vmware-helper b/debian/patches/fence-vmware-helper new file mode 100644 index 0000000..f5dbb34 --- /dev/null +++ b/debian/patches/fence-vmware-helper @@ -0,0 +1,16 @@ +Description: Use helper from libexec directory +Author: Valentin Vidic <vvidic@debian.org> +Last-Update: 2023-04-23 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/agents/vmware/fence_vmware.py ++++ b/agents/vmware/fence_vmware.py +@@ -41,7 +41,7 @@ + VMRUN_MINIMUM_REQUIRED_VERSION = 2 + + # Default path to vmhelper command +-VMHELPER_COMMAND = "fence_vmware_helper" ++VMHELPER_COMMAND = "/usr/libexec/fence-agents/fence_vmware_helper" + # Default path to vmrun command + VMRUN_COMMAND = "/usr/bin/vmrun" + # Default type of vmware diff --git a/debian/patches/series b/debian/patches/series index 9c1a18a..dc1af89 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -2,5 +2,5 @@ disable-network-access spelling systemd-syslog-target logging-warn-deprecated -enable-zvm-agent fence-virt-key +fence-vmware-helper diff --git a/debian/rules b/debian/rules index 56ca903..68d5ce6 100755 --- a/debian/rules +++ b/debian/rules @@ -40,26 +40,14 @@ override_dh_install: rm -v debian/tmp/usr/share/doc/fence-agents/COPY* rm -v debian/tmp/usr/share/doc/fence-agents/README.licence rmdir debian/tmp/usr/share/doc/fence-agents -ifneq ($(DEB_HOST_ARCH),s390x) - # remove fence_zvm because it doesn't do anything except on 390x - rm -v debian/tmp/usr/sbin/fence_zvm - rm -v debian/tmp/usr/share/man/man8/fence_zvm.8 -endif dh_install - # test agents (skip ack_manual, it doesn't have --help, skip vmware_helper, it wants VIRuntime.pm) + install -m 755 -D agents/vmware/fence_vmware_helper.pl debian/fence-agents-vmware/usr/libexec/fence-agents/fence_vmware_helper # we test in tmp after install so the .pyc files generated don't make it into the package - for agent in debian/tmp/usr/sbin/*; do \ - case $${agent##*/} in fence_ack_manual|fence_vmware_helper|fence_virt) continue;; esac; \ + for agent in debian/*/usr/sbin/*; do \ + case $${agent##*/} in fence_ack_manual|fence_virt*|fence_xvm) continue;; esac; \ echo "Testing $$agent"; \ PYTHONPATH=debian/tmp/usr/share/fence $$agent --help >/dev/null || exit; \ done - # fence_virt is in a separate package - rm -v debian/fence-agents/usr/sbin/fence_virt - rm -v debian/fence-agents/usr/sbin/fence_virtd - rm -v debian/fence-agents/usr/sbin/fence_xvm - rm -v debian/fence-agents/usr/share/man/man8/fence_virt.8 - rm -v debian/fence-agents/usr/share/man/man8/fence_virtd.8 - rm -v debian/fence-agents/usr/share/man/man8/fence_xvm.8 # tests are slow and require network access so moved to debian/tests/{delay,metadata} override_dh_auto_test: @@ -78,16 +66,6 @@ override_dh_installinit: override_dh_missing: rm debian/tmp/usr/lib/*/fence-virt/*.*a - dh_missing --fail-missing + rm -r debian/tmp/usr/share/fence/__pycache__ -override_dh_gencontrol: - # extract agent descriptions for use in debian/control - export LC_ALL=C; \ - ( echo -n "agents="; \ - sed -ne 's/<resource-agent name="\(.*\)" shortdesc="\(.*\)".*/\1: \2/p' tests/data/metadata/*.xml | \ - sed -e 's/\(I.O \)\?\(Fence\|Fencing\) agent for //' | \ - grep -v 'fence_amt_ws:\|fence_virt:' | \ - while read line; do echo -n " $$line\$${Newline}"; done ; \ - echo ; \ - ) >> debian/fence-agents.substvars - dh_gencontrol + dh_missing --fail-missing diff --git a/debian/tests/control b/debian/tests/control index 0abf418..5adb300 100644 --- a/debian/tests/control +++ b/debian/tests/control @@ -1,15 +1,15 @@ Tests: metadata -Depends: fence-agents, python3-openstackclient, xsltproc, libxml2-utils, gawk +Depends: fence-agents, xsltproc, libxml2-utils, gawk, @recommends@ Tests: delay -Depends: fence-agents, python3-openstackclient, time, iputils-ping +Depends: fence-agents, time, @recommends@ Tests: fence-dummy -Depends: fence-agents +Depends: fence-agents-dummy Restrictions: allow-stderr Tests: fence-aws -Depends: fence-agents +Depends: fence-agents-aws Restrictions: skippable Test-Command: /usr/sbin/fence_virt -h diff --git a/debian/tests/metadata b/debian/tests/metadata index 21c1ece..cf91d28 100755 --- a/debian/tests/metadata +++ b/debian/tests/metadata @@ -13,8 +13,12 @@ for agent in /usr/sbin/fence_*; do TESTXML=tests/data/metadata/${agent##*/}.xml if [ -f "$TESTXML" ]; then - gawk 'BEGIN {store=-1} /name=".*_path"/ || /name=".*_file"/ {store=2} {if (store!=0) {print}; store--}' "$TMPXML" \ - | diff -u "$TESTXML" - + if [ "$agent" = "/usr/sbin/fence_virt" ]; then + diff -u "$TESTXML" "$TMPXML" + else + gawk 'BEGIN {store=-1} /name=".*_path"/ || /name=".*_file"/ {store=2} {if (store!=0) {print}; store--}' "$TMPXML" \ + | diff -u "$TESTXML" - + fi fi xsltproc lib/fence2rng.xsl "$TMPXML" \ |