It has been quite a while since I last worked on this, and I’m not familiar with any recent developments however my primary observation is that (last time I looked at it) you needed OpenAIS if you want Corosync because there are a few components in OpenAIS that Corosync needs. They used to be the same thing, but were then split into two.
I can’t say that authoritatively, but it’s what I would do.

Also, it sounds silly but I want to make sure that you have actually installed the cluster-glue and resource agents packages into the system before building corosync and you havent only built them but not yet installed them. Easy mistake to make.

Other than that my best recommendation is that you head to the IRC channel to see if they can point you in the right direction: #linux-ha on FreeNode.

I’ve just discovered this blog and I felt down immediatly.

I’ trying to compile the whole HA suite under Slackware64 (13.1) and I’m working hard since few weeks. I fully agree with you when you say that « …Setting up the pacemaker stack is the hardest thing I have yet had to do in my professional career… ».

Well I’m now blocked at the Pacemaker ./config because it claims for the Hartbeat utility libraries.

======
configure: error: in `/usr/src/Pacemaker-1-0-Pacemaker-1.0.10′:
configure: error: Core Heartbeat utility libraries not found: no
======

I tryed the 1.0.10, 1.0.5 versions and the last tip release downladed from Clusterlabs with the same exit error.

I installed in the order you show:

1) Cluster Glue
2) Cluster Resource Agents
3) Corosync

avoiding openAIS because they say it’s only needed with multi-access filesystems (that I’m not planning to use).

Can you suggest me where I have to modify this f*** autoconf?

thanks in advance

marco

It’s a shame that the development group instead of building on top of the original architecture managed to split heartbeat in 1000 pieces,
the new functionality should be designed as add-on functionality and not canceling all the documentation and effort made up to the point that heartbeat was USEFUL for MANY people.

Currently it is good only for its developers.. it’s a pity..

If it weren’t for people like the author of this article that would loose days or weeks from their lives to understand and try to share their work in a human way, the BEST alternative would be to use OLD heartbeat and hope you don’t meet bugs..

There are a number of reasons:
1. I personally find Solaris to be a vile and hateful operating system.
2. There was nothing keeping me on Solaris, there was no benefit whatsoever in retaining it.
3. The only reason it was in use in the first place was my predecessors’ dependence upon ridiculously over-priced Sun hardware and the ubiquitous hardware and software support contracts that come with them.
4. Slackware is beautiful, secure, stable and simple (don’t get me evangelising) and the rest of the core network services have been running it for years.

(Sorry I keep modifying this comment, I can’t make up my mind how I want to say it.)