How to Install and Uninstall pacemaker Package on openSUSE Leap
Last updated: November 07,2024
1. Install "pacemaker" package
Please follow the instructions below to install pacemaker on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
pacemaker
Copied
2. Uninstall "pacemaker" package
Here is a brief guide to show you how to uninstall pacemaker on openSUSE Leap:
$
sudo zypper remove
pacemaker
Copied
3. Information about the pacemaker package on openSUSE Leap
Information for package pacemaker:
----------------------------------
Repository : Update repository with updates from SUSE Linux Enterprise 15
Name : pacemaker
Version : 2.1.5+20221208.a3f44794f-150500.6.11.1
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 1.3 MiB
Installed : No
Status : not installed
Source package : pacemaker-2.1.5+20221208.a3f44794f-150500.6.11.1.src
Upstream URL : https://www.clusterlabs.org/
Summary : Scalable High-Availability cluster resource manager
Description :
Pacemaker is an advanced, scalable High-Availability cluster resource
manager.
It supports more than 16 node clusters with significant capabilities
for managing resources and dependencies.
It will run scripts at initialization, when machines go up or down,
when related resources fail and can be configured to periodically check
resource health.
----------------------------------
Repository : Update repository with updates from SUSE Linux Enterprise 15
Name : pacemaker
Version : 2.1.5+20221208.a3f44794f-150500.6.11.1
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 1.3 MiB
Installed : No
Status : not installed
Source package : pacemaker-2.1.5+20221208.a3f44794f-150500.6.11.1.src
Upstream URL : https://www.clusterlabs.org/
Summary : Scalable High-Availability cluster resource manager
Description :
Pacemaker is an advanced, scalable High-Availability cluster resource
manager.
It supports more than 16 node clusters with significant capabilities
for managing resources and dependencies.
It will run scripts at initialization, when machines go up or down,
when related resources fail and can be configured to periodically check
resource health.