====== Cluster ======

===== DRBD =====

  * [[https://linbit.com/drbd-user-guide/users-guide-drbd-8-4/|DRBD 8.4 Official Manual]]
  * [[https://neutrollized.blogspot.com/2018/11/force-full-drbd-re-sync.html|Full sync DRBD]]

  * [[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/online_storage_reconfiguration_guide/persistent_naming#doc-wrapper|Persistent Naming]]

===== Blog post =====

  * [[https://www.digitalocean.com/community/tutorials/how-to-create-a-high-availability-setup-with-corosync-pacemaker-and-reserved-ips-on-ubuntu-14-04|DigitalOcean tutorial - How To Create a High Availability Setup with Corosync, Pacemaker, and Reserved IPs on Ubuntu 14.04]]
  * [[https://www.howtoforge.com/tutorial/how-to-set-up-nginx-high-availability-with-pacemaker-corosync-and-crmsh-on-ubuntu-1604/|HowToForge - How to Set up Nginx High Availability with Pacemaker, Corosync, and Crmsh on Ubuntu 16.04]]
  * [[https://geekpeek.net/linux-cluster-nodes/|Linux Cluster Part 3]] - Centos 6 **OLD**
  * [[https://www.golinuxcloud.com/setup-high-availability-cluster-centos-8/|Setup high availability cluster CentOS 8]]
  * [[https://www.admin-magazine.com/Archive/2023/75/Detect-failures-and-ensure-high-availability/(offset)/6|Detect failures and ensure high availability - Installing and Configuring Corosync/Pacemaker]]
  * [[https://houseofbrick.com/blog/active-passive-cluster-for-near-ha-using-pacemaker-drbd-corosync-and-mysql/|Active-Passive Cluster for Near HA Using Pacemaker, DRBD, Corosync and MySQL]] - **No sirve**: ''pcs resource master'' -> ''pcs resource promotable''
  * [[https://kevwells.com/it-knowledge-base/pacemaker-corosync-cluster-commands-cheat-sheet/|Pacemaker & Corosync Cluster Commands Cheat Sheet]]

==== Stack Overflow ====

  * [[https://serverfault.com/questions/908434/corosync-ha-preventing-split-brain-scenario|Corosync HA preventing split-brain scenario]]
  * [[https://stackoverflow.com/questions/61838575/how-to-know-the-replication-states-in-drbd|DRBD replication states]]

==== Task ====

  * [[https://redhatlinux.guru/2018/09/07/pacemaker-remove-constraints/|Pacemaker Remove Constraints]]


===== Man Pages =====

  * [[https://manpages.debian.org/stretch/drbd-utils/drbdadm.8.en.html|drbdadm (Debian)]]
  * [[https://manpages.debian.org/testing/drbd-utils/drbdsetup-9.0.8.en.html|drbdsetup (Debian)]]
  * [[https://manpages.debian.org/unstable/drbd-utils/drbd.conf-9.0.5.en.html|drbd.conf (Debian)]]
  * [[https://manpages.debian.org/unstable/corosync/corosync.conf.5.en.html|corosync.conf (Debian)]]
  * [[https://crmsh.github.io/man-2.0/|crm - Man Page]]
  * [[https://www.mankier.com/8/pcs|pcs - Man Page]]
  * [[https://manpages.debian.org/testing/pcs/pcsd.8.en.html|pcsd (Debian)]]
  * [[https://manpages.debian.org/testing/pcs/pcs.8.en.html|pcs (Debian)]]

==== Resource Agents ====

  * [[https://manpages.debian.org/testing/drbd-utils/ocf_linbit_drbd.7.en.html|ocf_linbit_drbd]]
  * [[https://manpages.debian.org/testing/resource-agents/ocf_heartbeat_lxc.7.en.html|ocf_heartbeat_lxc]]
  * [[https://manpages.debian.org/testing/pacemaker-resource-agents/ocf_pacemaker_ping.7.en.html|ocf_pacemaker_ping]]
  * [[https://manpages.debian.org/testing/resource-agents/ocf_heartbeat_MailTo.7.en.html|ocf_heartbeat_MailTo]]
    * [[https://www.lisenet.com/2019/high-availability-pacemaker-cluster-monitoring/|High Availability Pacemaker Cluster Monitoring]]

===== Official documentation =====

  * [[https://documentation.suse.com/sle-ha/12-SP4/html/SLE-HA-all/book-sleha.html|SUSE Linux Enterprise High Availability 12 SP4
Administration Guide]]
  * [[https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Explained/singlehtml/|Pacemaker Explained]]
  * [[https://clusterlabs.org/pacemaker/doc/deprecated/en-US/Pacemaker/2.0/html/Clusters_from_Scratch/index.html|Clusters from Scratch - Pacemaker 2.0]]
  * [[https://clusterlabs.org/pacemaker/doc/|Clusterlabs - Pacemarker documentation]]
  * [[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/high_availability_add-on_reference/s1-moving_resources_due_to_connectivity_changes-haar|Redhat - Moving Resources Due to Connectivity Changes]]
  * [[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/high_availability_add-on_reference/index|Redhat - High Availability Add-On Reference]]

===== Tools =====

  * [[https://github.com/jnpkrn/clufter|clufter - Tool/library for transforming/analyzing cluster configuration formats]]


  Finished drbd.service - DRBD -- please disable. Unless you are NOT using a cluster manager..


[[docs:servicios:cluster:cheatsheet|docs:servicios:cluster:cheatsheet]]
====== primitive ======

El comando ''primitive'' describe un recurso. Se puede hacer referencia a él solo una vez en objetos de group, clone o master-slave. Si no se hace referencia a él, se coloca como un recurso único en el CIB.

Las operaciones podrán especificarse de forma anónima, grupal o por referencia:

"Anónimo", como una lista de especificaciones de ''op''. Utilice este método si no necesita hacer referencia al conjunto de operaciones en otro lugar. Esta es la forma más común de definir operaciones.

Si desea reutilizar conjuntos de ''operations'', utilice la palabra clave de ''operations'' junto con una identificación para darle un nombre al conjunto de operaciones. Utilice la palabra clave ''operations'' y un valor id-ref establecido en la identificación de otro conjunto de operaciones para aplicar el mismo conjunto de operaciones a esta primitiva.

Los atributos de operación que no se reconocen se guardan como atributos de instancia de esa operación. Un ejemplo típico es ''OCF_CHECK_LEVEL''.

Para recursos multiestado, los roles se especifican como ''role=<role>''.

Se puede definir una plantilla para recursos que sean del mismo tipo y que compartan la mayor parte de la configuración. Consulte ''rsc_template'' para obtener más información.

Los atributos que contienen valores de tiempo, como el atributo de ''interval'' en las operaciones, se configuran como un número simple, que se interpreta como un tiempo en segundos, o utilizando uno de los siguientes sufijos:

  s, sec - time in seconds (same as no suffix)
  
  ms, msec - time in milliseconds
  
  us, usec - time in microseconds
  
  m, min - time in minutes
  
  h, hr - time in hours

Usage:

  primitive <rsc> {[<class>:[<provider>:]]<type>|@<template>}
    [description=<description>]
    [[params] attr_list]
    [meta attr_list]
    [utilization attr_list]
    [operations id_spec]
      [op op_type [<attribute>=<value>...] ...]
  
  attr_list :: [$id=<id>] [<score>:] [rule...]
             <attr>=<val> [<attr>=<val>...]] | $id-ref=<id>
  id_spec :: $id=<id> | $id-ref=<id>
  op_type :: start | stop | monitor

Example:

  primitive apcfence stonith:apcsmart \
    params ttydev=/dev/ttyS0 hostlist="node1 node2" \
    op start timeout=60s \
    op monitor interval=30m timeout=60s

  primitive www8 apache \
    configfile=/etc/apache/www8.conf \
    operations $id-ref=apache_ops

  primitive db0 mysql \
    params config=/etc/mysql/db0.conf \
    op monitor interval=60s \
    op monitor interval=300s OCF_CHECK_LEVEL=10

  primitive r0 ocf:linbit:drbd \
    params drbd_resource=r0 \
    op monitor role=Master interval=60s \
    op monitor role=Slave interval=300s

  primitive xen0 @vm_scheme1 xmfile=/etc/xen/vm/xen0

  primitive mySpecialRsc Special \
    params 3: rule #uname eq node1 interface=eth1 \
    params 2: rule #uname eq node2 interface=eth2 port=8888 \
    params 1: interface=eth0 port=9999


====== group ======

The ''group'' command creates a group of resources. This can be useful when resources depend on other resources and require that those resources start in order on the same node. A common use of resource groups is to ensure that a server and a virtual IP are located together, and that the virtual IP is started before the server.

Grouped resources are started in the order they appear in the group, and stopped in the reverse order. If a resource in the group cannot run anywhere, resources following it in the group will not start.

group can be passed the "container" meta attribute, to indicate that it is to be used to group VM resources monitored using Nagios. The resource referred to by the container attribute must be of type ''ocf:heartbeat:Xen'', ''ocf:heartbeat:VirtualDomain'' or ''ocf:heartbeat:lxc''.

Usage:

  group <name> <rsc> [<rsc>...]
    [description=<description>]
    [meta attr_list]
    [params attr_list]
  
  attr_list :: [$id=<id>] <attr>=<val> [<attr>=<val>...] | $id-ref=<id>

Example:

  group internal_www disk0 fs0 internal_ip apache \
    meta target_role=stopped

  group vm-and-services vm vm-sshd meta container="vm"

====== ms (master) ======

The ''ms'' command creates a master/slave resource type. It may contain a single primitive resource or one group of resources.

Usage:

  ms <name> <rsc>
    [description=<description>]
    [meta attr_list]
    [params attr_list]
  
  attr_list :: [$id=<id>] <attr>=<val> [<attr>=<val>...] | $id-ref=<id>

Example:

  ms disk1 drbd1 \
    meta notify=true globally-unique=false