On Thu, Aug 12, 2010 at 03:56:09PM -0500, Dimitri Maziuk wrote:
> On Thursday 12 August 2010 15:08, Dejan Muhamedagic wrote:
> 
> > On the plus side, there are more people available creating the mess.
> 
> Right. So forking off another heartbeat looks like just the ticket.

Thought that irony would be obvious.

> What I'd like is a document that says
> 1. Corosync is the comms component. Install 1.2.3 rpm from this repo here.
>     Here's how you configure it for bcast (unicast) over a crossover cable.

Sorry, no unicast in Corosync. But you can keep Heartbeat if
that's what you're used to.

> 2. Pacemaker is the resource manager component. Install 2.1.0 rpm from that 
> repo there. Here's how you configure it to do active/passive apache on top of 
> #1. Here's how you set up drbd resource. Here's how you configure 
> active/passive nfs. (Note that pacemaker does resource health monitoring, so 
> you don't need mon anymore -- here's how you tell it to check the status of 
> your rpc.statd and initiate failover it it's sick.) 
> 
> That's all I need.

There's this Clusters from scratch document at clusterlabs.org.
It's advertised very prominently I believe. If you skip the
Fedora installation part, perhaps it would suffice. Did you give
it a try?

Thanks,

Dejan

> Dima
> -- 
> Dimitri Maziuk
> Programmer/sysadmin
> BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to