3 ms·

You still have to get, and keep, things running on boxes though. HA does not magically remove that need.

by stock_toaster 14y ago

contingencies 14y ago
Pacemaker/Corosync functionally replace all of the alternatives discussed.
- stock_toaster 14y ago
  How so? Is pacemaker/corosync not more of a replacement for things like keepalived/heartbeatd (often used in conjunction with stonith, drbd), and as a way to run clusters of services? You still need to launch and run the services themselves with something. (sysV init scripts, etc) Even a cursory review of the docs seems to imply the same. http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pacemaker_Explained/_systemd.html http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pa... http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pacemaker_Explained/_upstart.html http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pa... http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pacemaker_Explained/s-resource-supported.html http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pa... I do see a reference to: > Version 1 of Heartbeat came with its own style of resource > agents and it is highly likely that many people have > written their own agents based on its conventions. > Although deprecated with the release of Heartbeat v2, > they were supported by Pacemaker up until the release > of 1.1.8 to enable administrators to continue to use > these agents. ...so maybe that is what you were talking about.
  - contingencies 14y ago
    Usually there is a resource agent script that replaces the init script. If not, you just write one. This is a barrier to low-level users, but is not an issue for experienced admins/programmers/devops. The primary community library of such lives here: https://github.com/ClusterLabs/resource-agents/ https://github.com/ClusterLabs/resource-agents/ Resource agent scripts can support master/slave style services (including promotion/demotion) in addition to enabling the cluster to self-manage nontrivial overall system state transitions on a multi-host basis. You define the target running state with a declarative syntax that is replicated to across all nodes. Heartbeat is an earlier platform that has now been functionally replaced by corosync.

You still have to get, and keep, things running on boxes though. HA does not magically remove that need.

contingencies 14y ago

Pacemaker/Corosync functionally replace all of the alternatives discussed.

stock_toaster 14y ago
How so? Is pacemaker/corosync not more of a replacement for things like keepalived/heartbeatd (often used in conjunction with stonith, drbd), and as a way to run clusters of services? You still need to launch and run the services themselves with something. (sysV init scripts, etc) Even a cursory review of the docs seems to imply the same. http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pacemaker_Explained/_systemd.html http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pa... http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pacemaker_Explained/_upstart.html http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pa... http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pacemaker_Explained/s-resource-supported.html http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pa... I do see a reference to: > Version 1 of Heartbeat came with its own style of resource > agents and it is highly likely that many people have > written their own agents based on its conventions. > Although deprecated with the release of Heartbeat v2, > they were supported by Pacemaker up until the release > of 1.1.8 to enable administrators to continue to use > these agents. ...so maybe that is what you were talking about.
- contingencies 14y ago
  Usually there is a resource agent script that replaces the init script. If not, you just write one. This is a barrier to low-level users, but is not an issue for experienced admins/programmers/devops. The primary community library of such lives here: https://github.com/ClusterLabs/resource-agents/ https://github.com/ClusterLabs/resource-agents/ Resource agent scripts can support master/slave style services (including promotion/demotion) in addition to enabling the cluster to self-manage nontrivial overall system state transitions on a multi-host basis. You define the target running state with a declarative syntax that is replicated to across all nodes. Heartbeat is an earlier platform that has now been functionally replaced by corosync.