You can obtain the CIB by running the 'pcs cluster cib' command, which is recommended first step when you want to perform desired modifications (pcs -f <command>) for the one-off push. If diff-against is specified, pcs diffs contents of filename against contents of filename_original and pushes the result to the CIB.
Important to notethat if I execute pcs cluster stop server_b.test.local all resources inside the configure group are moved to the other node. What's going on? Like I said it worked and no changes have been made since then. Thank you in advance! EDIT: Now using the pcs -f option, make changes to the configuration saved in the drbd_cfg file. These changes will not be seen by the cluster until the drbd_cfg file is pushed into the live cluster's cib later on.[[email protected] var]# pcs cluster cib-push fs_cfg The constraint is for forcing the nfs server to be running in the same node where the volume is mounted and to be started before mounting the file system exported.
crmsh # crm node standby pcmk-1 pcs-0.9 # pcs cluster standby pcmk-1 pcs-0.10 # pcs node standby pcmk-1 Remove node from standby. crmsh # crm node online pcmk-1 pcs-0.9 # pcs cluster unstandby pcmk-1 pcs-0.10 # pcs node unstandby pcmk-1 crm has the ability to set the status on reboot or forever. pcs can apply the change to all the nodes. Use the Pacemaker pcs utility to queue several changes into a file and later push those changes to the Cluster Information Base (CIB) atomically: sudo pcs cluster cib clust_cfg Disable STONITH, because you'll deploy the quorum device later: sudo pcs -f clust_cfg property set stonith-enabled=false Disable the quorum-related settings.
I’m trying to create cluster of two nodes, but it seems to behave a little strange following this guide, but I was unable to do, for example: [[email protected] ~]# pcs property set stonith-enabled=false Error: Unable to update cib Call cib_replace failed (-62): Timer expired only thing I find in logs are continued corosync events: crmsh # crm node standby pcmk-1 pcs-0.9 # pcs cluster standby pcmk-1 pcs-0.10 # pcs node standby pcmk-1 Remove node from standby. crmsh # crm node online pcmk-1 pcs-0.9 # pcs cluster unstandby pcmk-1 pcs-0.10 # pcs node unstandby pcmk-1 crm has the ability to set the status on reboot or forever. pcs can apply the change to all the nodes.[pcmk01]# pcs cluster cib dlm_cfg [pcmk01]# pcs -f dlm_cfg resource create dlm ocf:pacemaker:controld \ op monitor interval=120s on-fail=fence clone interleave=true ordered=true Set up clvmd as a cluster resource. # pcs cluster auth rh7-nodo3.localdomain # pcs cluster node add rh7-nodo3.localdomain On the new node # pcs cluster start # pcs cluster enable Display the configuration in xml style # pcs cluster cib Display the current status # pcs status Display the current cluster status # pcs cluster status Destroy/remove cluster configuration on a node