2 ms·
Amazed to see so many simple responses in this thread given that the single-system paradigm is sort-of heading out of date now (manual Unix systems administrati
by contingencies 14y ago
Amazed to see so many simple responses in this thread given that the single-system paradigm is sort-of heading out of date now (manual Unix systems administration is arguably a dying horse). For any serious (ie. highly available) systems, a major option that should be under discussion is Pacemaker/Corosync. http://clusterlabs.org/ http://clusterlabs.org/
It's a pain to learn, easy to screw up, non-trivial to test exhaustively, but provides highly flexible daemon migration and monitoring functionality you aren't likely to find anywhere else, for free, and for any imaginable service. (Actually you can monitor anything with it, including hardware. Check it out.)
- stock_toaster 14y agoYou still have to get, and keep, things running on boxes though. HA does not magically remove that need.
- contingencies 14y agoPacemaker/Corosync functionally replace all of the alternatives discussed.
- stock_toaster 14y agoHow 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 agoUsually 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.
- eikenberry 14y agoThese projects seem to do a very poor job of presenting themselves. I spent a good deal of time reading about each and have yet to have a really good grasp of what they are for. They seem to be about maintaining a cluster of hardware servers to run arbitrary services with configuration and fail over. Do you know of some decent article, blog post, video, whatever that presents these products, what they are good for and a typical use case?
- contingencies 14y agoI agree wholeheartedly about the failure to communicate clearly. At least one contributing factor to the present situation is the lucrative consulting that exists around these solution types and helps to fund their development. Simply put, if it was that easy, everyone would be doing it (and we'd be out of a job). However, to be fair, things change fast and there does exist a lot of good documentation - just not necessarily perfectly up to date for your scenario. Your assumption is perfectly correct. Have a look at http://www.linbit.com/en/downloads/tech-guides http://www.linbit.com/en/downloads/tech-guides or http://clusterlabs.org/doc/ http://clusterlabs.org/doc/ or try #linux-ha or #linux-cluster on freenode.