[Pacemaker] moving from corosync.conf to cluster.conf

[Parveen Jain]

Hi All,

  Following was my problem:

1)     
My RHEL 6.3 is using CRM shell and
corosync.conf.

2)     
Wanted to move to RHEL6.5 and hence the
underlying cluster. Also wanted to move to recommended way of using cluster
with CMAN using “cluster.conf”.
(Before executing this document I first upgraded my O/S to RHEL6.5.)

To solve this problem , found following link:

http://floriancrouzat.net/2013/04/rhel-6-4-pacemaker-1-1-8-adding-cman-support-and-getting-rid-of-the-plugin/

(Also got another link which has more or less same thing
explain in a documented way:

http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html/Clusters_from_Scratch/_configuring_cman.html)


This document is written well and I could execute all of the
commands successfully without disturbing my cluster, but I found some issue
after executing this last line:

crm configure property maintenance-mode=false

After executing this command, I lost my VIP. I need to
execute this upgrade on my production environment and can’t afford to go “offline”
in this way.


Few are my questions to execute this upgrade in a more convenient
way:

1)     
What can be the reason of this VIP removal (if
someone has already tested with this approach)?

2)     
Is it right approach, if I do directly assign my
VIP (after moving my cluster to maintenance mode) to one of my Ethernet interface
and then run the commands given in this document.

3)     
Is not there some command line option to upgrade
from corosync.conf to cluster.conf directly(ideally I felt that we should be
able to generate an ).

4)     
How will I move to the usage of “pcs commands”. This
article is given with using “ccs” commands. Shall I assume that once I finish
with “ccs”, I can do rest of my configuration using “pcs” commands.
Regards,Parveen Jain 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140224/782c8902/attachment-0002.html>