[Linux-ha-dev] "Hot Failover" status/plans
G'day, I'm currently reviewing technology in the high availability area for applicability to replace an existing proprietary system. Linux HA looks to have come a long way since I last reviewed it, which would have been around 2005. This might just be an improvement in the documentation, as opposed to code changes. The brief of the existing software is to provide n-way redundancy for applications/resources that need to be highly available, with hot failover. The existing system takes a fairly simple approach. It requires prior configuration of exactly where all resources will be running. It runs all replicas all the time, and tells one replica to be the controller while others are told not to be the controller. I read in "The Evolution of the Linux-HA project"[1] that the community is interested in hot failover. Is this still the case? I believe this is still different to what you are calling "hot standby". Is that right? Is there an established mechanism or approach to providing hot failover using existing LinuxHA technology? If not, what do the plans towards this goal look like? For example, is there a clear idea as to how resources managed in this way are told about decision of control? I have a few other queries that may already be addressed in the documentation: Is it possible to set up some sort of "mega cluster" with Linux HA? By this I mean that a resource is shared across multiple geographical locations, each with a mini-cluster. Each mini-cluster would elect a leader, which exchanges heartbeat messages with the leader of the other cluster. Within each mini-cluster, heartbeats can be exchanged n-ways. The general idea of this approach is that resources could be redundant across geographical boundaries without saturating the WAN link with redundant heartbeat communications. Thanks in advance for any responses you can offer. Benjamin. [1] http://www.linux-ha.org/_cache/TechnicalPapers__HBevolution.pdf___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
[Linux-ha-dev] [PATCH] Remove autoconf and friends on make distclean
I'm not sure what the intention of the symlinks to autoconf, autoheader and automake added by 2d04e4dd3a90857e280e3036f297b91ab0355138 are, but it seems reasonable to remove them on make distclean as they aren't present in a dist tarball. This actually fixes a problem when building debian packages. Basically if ./ConfigureMe is run for any reason when updating a debian package, say to effect a change to a Makefile.am, then these symlinks are created, and the debian packaging system can't cope with this. If this change is not acceptable I can just push it into debian/rules, but I think that generally its nicer not to push things into packaging specific portions of the build system. I'm am looking this patch being included post 2.1.1.1 Signed-off-by: Simon Horman <[EMAIL PROTECTED]> Index: heartbeat/Makefile.am === --- heartbeat.orig/Makefile.am 2007-07-27 12:25:03.0 +0900 +++ heartbeat/Makefile.am 2007-07-27 12:25:38.0 +0900 @@ -109,6 +109,9 @@ install-exec-local: -chmod 700 $(DESTDIR)$(coredir)/$(hauser) -cd $(DESTDIR)@HA_LIBHBDIR@; for file in `ls $(SHAREDIR)`; do rm -f $$file; ln -s $(SHAREDIR)/$$file .; done +distclean-local: + rm -f autoconf automake autoheader + # "pkg" format for Solaris etc. pkg: (cd pkg && $(MAKE) PWD=`pwd` pkg) ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
[Linux-ha-dev] [PATCH] Remove autoconf and friends on make distclean
I'm not sure what the intention of the symlinks to autoconf, autoheader and automake added by 2d04e4dd3a90857e280e3036f297b91ab0355138 are, but it seems reasonable to remove them on make distclean as they aren't present in a dist tarball. This actually fixes a problem when building debian packages. Basically if ./ConfigureMe is run for any reason when updating a debian package, say to effect a change to a Makefile.am, then these symlinks are created, and the debian packaging system can't cope with this. If this change is not acceptable I can just push it into debian/rules, but I think that generally its nicer not to push things into packaging specific portions of the build system. I'm am looking this patch being included post 2.1.1.1 Signed-off-by: Simon Horman <[EMAIL PROTECTED]> Index: dev/Makefile.am === --- dev.orig/Makefile.am2007-07-27 12:08:18.0 +0900 +++ /dev/null 1970-01-01 00:00:00.0 + @@ -1,136 +0,0 @@ -# -# linux-ha: Linux-HA code -# -# Copyright (C) 2002 Alan Robertson -# -# This program is free software; you can redistribute it and/or -# modify it under the terms of the GNU General Public License -# as published by the Free Software Foundation; either version 2 -# of the License, or (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program; if not, write to the Free Software -# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. -# - -##auxdir = @ac_aux_dir@ -##AUX_DIST= $(auxdir)/install-sh $(auxdir)/missing \ -##$(auxdir)/mkinstalldirs -##AUX_DIST_EXTRA = $(auxdir)/readline.m4 $(auxdir)/sys_errlist.m4 \ -##$(auxdir)/sys_siglist.m4 -EXTRA_DIST = bootstrap rc.config.heartbeat\ - heartbeat.spec.in heartbeat.spec\ - ConfigureMe README.in libltdl.tar - -RPMREL = @RPMREL@ -RPM= @RPM@ -RPMFLAGS = -ta --nodeps -TARFILE= @TARFILE@ -AM_TAR = tar -RPMDIR=$(HOME)/rpms -WEBDIR=/home/alanr/ha-web/download -HBWEBDIR=/home/alanr/ha-web/heartbeat -RPMSRC=$(DESTDIR)$(RPMDIR)/SRPMS/$(PACKAGE)-$(VERSION)-$(RPMREL).src.rpm -RPM386=$(DESTDIR)$(RPMDIR)/RPMS/i586/$(PACKAGE)-$(VERSION)-$(RPMREL).i586.rpm -RPMstonith=$(DESTDIR)$(RPMDIR)/RPMS/i586/$(PACKAGE)-stonith-$(VERSION)-$(RPMREL).i586.rpm -RPMpils=$(DESTDIR)$(RPMDIR)/RPMS/i586/$(PACKAGE)-pils-$(VERSION)-$(RPMREL).i586.rpm -RPMldir=$(DESTDIR)$(RPMDIR)/RPMS/i586/$(PACKAGE)-ldirectord-$(VERSION)-$(RPMREL).i586.rpm - -ALL_RPMS = $(RPMSRC) $(RPM386) $(RPMstonith) $(RPMldir) $(RPMpils) - -AUTOMAKE_OPTIONS = foreign -##ACLOCAL = aclocal -I $(auxdir) - -MAINTAINERCLEANFILES= Makefile.in aclocal.m4 configure DRF/config-h.in \ -DRF/stamp-h.in libtool.m4 ltdl.m4 libltdl.tar -coredir = @HA_COREDIR@ -hauser = @HA_CCMUSER@ - -## proc-ha is left out from SUBDIRS (completely obsolete) - -if SNMP_SUBAGENT_BUILD -SNMP_SUBAGENT_DIR = snmp_subagent -endif - -if MGMT_BUILD -MGMT_DIR = mgmt -endif - -if CIM_PROVIDER_BUILD -CIM_PROVIDER_DIR = cim -endif - -if TSA_PLUGIN_BUILD -TSA_PLUGIN_DIR = tsa_plugin -endif - -if LDIRECTORD_BUILD -LDIRECTORD_DIR = ldirectord -endif - -SUBDIRS= $(LIBLTDL_DIR) debian pkg port replace include lib \ - heartbeat membership telecom contrib resources lrm $(CRM_DIR) \ - fencing logd $(SNMP_SUBAGENT_DIR) tools doc cts $(MGMT_DIR)\ - $(CIM_PROVIDER_DIR) $(LDIRECTORD_DIR) config $(TSA_PLUGIN_DIR) - -HANDY_DOCS = doc/ChangeLog doc/GettingStarted.html doc/DirectoryMap.txt -HBDOCS = doc/heartbeat_api.html - -# Pass these to configure when running "make distcheck" -DISTCHECK_CONFIGURE_FLAGS = --with-initdir=prefix - -rpm: dist - $(RPM) --nodeps $(RPMFLAGS) $(TARFILE) http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
Re: [Linux-ha-dev] Dynamic Modify the timeout values
On 2007-07-26T15:52:00, Horms <[EMAIL PROTECTED]> wrote: > There really are systems out there running linux-ha that don't have > bash. For instance, some Debian systems have dash installed not bash. > > It is true that bash's kill allows SIGRTMAX while /bin/kill does > not. But I think we should look for another solution. Here > are some ideas that I have. Simply add a requirement for bash to the heartbeat package and be done with this. A number of RAs require bash as well. ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
[Linux-ha-dev] 2.1.1 has installation problems
It has come to our attention that 2.1.1 has some installation issues. If you have not yet installed it, please wait for an updated version. If you wish to help test the forthcoming 2.1.1 replacement, the source for the corrected version can be found here: http://hg.linux-ha.org/test/archive/tip.tar.gz These oversights in installation in no way affect stability, and were strictly due to an error on my part. The release was thoroughly stability-tested, and is very stable - so if you have already installed it, and have it working, it's perfectly fine for you to continue using it. We will conduct a postmortem analysis of how this happened and how we can design a process which will make such errors less likely. My sincere apologies to all concerned. -- Alan Robertson <[EMAIL PROTECTED]> "Openness is the foundation and preservative of friendship... Let me claim from you at all times your undisguised opinions." - William Wilberforce ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
