[Pacemaker] Migrating from Heartbeat Fedora 17 to Fedora 18 Pacemaker

[Andrew Beekhof]

Pasting my reply from the linux-ha list:


On 16/04/2013, at 12:05 AM, Guilsson Guilsson <guilsson at gmail.com> wrote:

> Is there a way to continue using my cfg files in Fedora 18 pacemaker ?

No. Sorry.

> If not, Is there a straightforward (and simple) conversion between my cfg
> files to new format ?

There was one, but its honestly much simpler to start from scratch.
Happily we have a step-by-step worked example:
   http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Clusters_from_Scratch/index.html

> Although it seams pacemaker has more features, is it become more
> complicated ?

On the surface it seems like it, but CLIs like pcs and crmsh make it reasonably accessible.
I'd highly recommend this:
  http://blog.clusterlabs.org/blog/2009/configuring-heartbeat-v1-was-so-simple/


On 16/04/2013, at 10:13 AM, Guilsson Guilsson <guilsson at gmail.com> wrote:

> Dear all
> 
> I've been using HA for several years. It's a quite simple setup to create an use. I'm using HA between 2 firewalls machines.
> It's almost the same configuration for years: ha.cf / haresources / authkeys.
> 
> In previous instalations (Fedora 10/11/12/13/14/15/16/17) I simply issue on both firewalls:
> 
> # yum -y install heartbeat (so all dependencies are installed)
> # cp /root/backup/{ha.cf,haresources/authkeys} /etc/ha.d/
> # chkconfig hearbeat on (or systemctl enable hearbeat.service)
> # service heartbeat start (of systemctl start heartbeat.service)
> # /usr/share/heartbeat/hb_standby all|foreign/failback (sometimes to manage nodes)
> 
> and everythng has been working fine (for years).
> Current working scenario in Fedora 17:
>  # rpm -q heartbeat resource-agents
> heartbeat-3.0.4-1.fc17.2.i686
> resource-agents-3.9.2-2.fc17.1.i686
> 
> 
> My problems started when I re-installed the firewalls using Fedora 18.
> At first "yum -y install heartbeat" install "pacemaker" instead.
> After copying my files and tried to start the services nothing happened.
> In fact, It seams EVERYTHING CHANGED A LOT: PCS, Corosync, Pacemaker, cib, etc
> 
> My cfg files:
> 
> ha.cf
> --------------------------------------------------------------------------------------------
> debugfile /var/log/ha-debug
> logfile /var/log/ha-log
> logfacility local0
> keepalive 2
> deadtime 15
> warntime 5
> initdead 45
> bcast eth1
> auto_failback on
> node gw1.gs.local
> node gw2.gs.local
> ping_group topsites 200.160.0.10 200.189.40.10 200.192.232.10 200.219.154.10 200.229.248.10 200.219.159.10
> respawn hacluster /usr/lib/heartbeat/ipfail
> --------------------------------------------------------------------------------------------
> 
> haresources
> --------------------------------------------------------------------------------------------
> gw1.gs.local 10.10.10.10/24/eth1
> gw2.gs.local 10.10.10.20/24/eth1
> --------------------------------------------------------------------------------------------
> 
> authkeys
> --------------------------------------------------------------------------------------------
> auth 1
> 1 md5 Super!@#$#%SecreT
> --------------------------------------------------------------------------------------------
> 
> I prefer to stick on Fedora 18, so:
> 
> Is there a way to continue using my cfg files in Fedora 18 pacemaker ?
> If not, Is there a straightforward (and simple) conversion between my cfg files to new format ?  
> Although it seams pacemaker has more features, is it become more complicated ?
>  
> Thanks in advance,
> -Guilsson _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org