Hello,
yes, as Digimer mentioned, clufter is the tool you may want to look
at. Do not expect fully automatic miracles from it, though.
It's meant to show the conversion path, but one has to be walk it
very carefully and make adjustments every here and there.
In part because there is not a large overlap between resource agents
of both kinds.
On 22/01/16 17:32 +0530, jaspal singla wrote:
> I desperately need some help in order to migrate my cluster configuration
> from CMAN (RHEL-6.5) to PACEMAKER (RHEL-7.1).
>
> I have tried to explore a lot but couldn't find similarities configuring
> same resources (created in CMAN's cluster.conf file) to Pacemaker.
>
> I'd like to share cluster.conf of RHEL-6.5 and want to achieve the same
> thing through Pacemaker. Any help would be greatly appreciable!!
>
> *Cluster.conf file*
>
> ##
>
[reformatted configuration file below for better readability and added
some comment in-line]
>
^^^
no, this is not the way to increase config version
This seems to be quite frequented mistake; looks like configuration
tools should have strictly refrained from using this XML declaration
in the first place.
>
>
>
>
>
>
(I suppose that other nodes were omitted)
>
>
>
>
>
>restricted="0"/>
TODO: have to check what does it mean when FOD is not saturated
with any cluster node references
>
>
>
General LSB-compliance-assumed commands are currently using a path hack
with lsb:XYZ resource specification. In this very case, it means
the result after the conversion refers to
"lsb:../../..//data/Product/HA/bin/FsCheckAgent.py".
Agreed, there should be a better way to support arbitrary locations
beside /etc/init.d/XYZ.
>name="ORACLE_REPLICATOR"/>
>
>
>
>
>
>
>
>