On Wed, Jul 25, 2018 at 12:02:38PM +0300, Roman Makhov wrote:
> Hi Jaco,
>
> Maybe it is because crm is core component of Pacemaker (
> https://wiki.clusterlabs.org/wiki/File:Stack.png)?
> "crmd Short for Cluster Resource Management Daemon. Largely a message
> broker for the PEngine and LRM, it
Hi Jaco,
Maybe it is because crm is core component of Pacemaker (
https://wiki.clusterlabs.org/wiki/File:Stack.png)?
"crmd Short for Cluster Resource Management Daemon. Largely a message
broker for the PEngine and LRM, it also elects a leader to co-ordinate the
activities (including
While we're at it, a cluster should generally have redundant cluster
links (two physically separate network links with corresponding
interface sections in the corosync configuration), especially if one of
those links is also used as the DRBD replication link. Otherwise, any
loss of communication
Hi
Sorry that was a typo. I use different name for my resource on in the LAB.
I found that after installing crmsh it fixed my problem, even though I don't
use crm it self.
cat /etc/yum.repos.d/ha-cluster.repo
[network_ha-clustering_Stable]
name=Stable High Availability/Clustering packages
Hi Jaco,
On Mon, Jul 23, 2018 at 11:10 PM, Jaco van Niekerk
wrote:
> Hi
> I am using the following packages:
> pcs-0.9.162-5.el7.centos.1.x86_64
> kmod-drbd84-8.4.11-1.el7_5.elrepo.x86_64
> drbd84-utils-9.3.1-1.el7.elrepo.x86_64
> pacemaker-1.1.18-11.el7_5.3.x86_64
>
Hi
I am using the following packages:
pcs-0.9.162-5.el7.centos.1.x86_64
kmod-drbd84-8.4.11-1.el7_5.elrepo.x86_64
drbd84-utils-9.3.1-1.el7.elrepo.x86_64
pacemaker-1.1.18-11.el7_5.3.x86_64
corosync-2.4.3-2.el7_5.1.x86_64
targetcli-2.1.fb46-6.el7_5.noarch
my /etc/drbd.conf
global { usage-count no;
