RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 456897 - Provide conversion to Pacemaker configuration file format
Summary: Provide conversion to Pacemaker configuration file format
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pacemaker
Version: 6.0
Hardware: All
OS: Linux
high
low
Target Milestone: rc
: ---
Assignee: Lon Hohberger
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On: 493474 727643 729827
Blocks: 456895 756082
TreeView+ depends on / blocked
 
Reported: 2008-07-28 14:42 UTC by Lon Hohberger
Modified: 2016-04-26 14:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Technology Preview
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-11 21:12:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Lon Hohberger 2008-07-28 14:42:46 UTC 
Description of problem:

Rgmanager's configuration (part of cluster.conf) is very different from
Pacemaker's configuration.  In order to preserve rolling upgrade between Red Hat
Enterprise Linux 5 and Red Hat Enterprise Linux 6 from a cluster service
perspective, we will need a translation utility which will give Pacemaker
configuration data in a way Pacemaker would understand it.
Comment 15 Lon Hohberger 2011-08-10 19:02:29 UTC 
I have this working for limited sets of resources and STONITH configurations.  The following is known to work:

  * single-instance STONITH devices for a host
    * All parameters must be in the <fencedevice> tag
  * multiple-instance STONITH devices with or without hostlist support
    * caveat: you must only have 'port="X"' in the <device> tag; no other 
      options from the <device> tag are handled; they must be in the 
      <fencedevice> tag
  * IP address resources
  * script resources

I tested:

1) Services running under rgmanager; both cluster nodes online

2) Run ccs2cib

[root@snap ccs2cib]# ./ccs2cib -d -o cib.xml -R
debug: adding . to /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
debug: using ./cluconf2cib.xsl
debug: using /usr/share/java/saxon.jar
 * Converting configuration
 * Calling crm_verify to validate the configuration.
 * Disabling rgmanager in /etc/cluster/cluster.conf
 * Calling cman_tool to update cluster.conf
 * Proposed cib stored in cib.xml
[root@snap ccs2cib]#

3) Wait for rgmanager to finish exiting on both hosts

4) Start pacemaker on both hosts

5) cibadmin --replace --xml-file cib.xml
   NOTE: I had to do this twice; I am not sure why.

Check crm_mon:

[root@snap ccs2cib]# crm_mon -1
============
Last updated: Wed Aug 10 15:00:17 2011
Stack: cman
Current DC: crackle - partition with quorum
Version: 1.1.5-5.el6-01e86afaaa6d4a8c4836f68df80ababd6ca3902f
3 Nodes configured, unknown expected votes
4 Resources configured.
============

Online: [ snap crackle ]
OFFLINE: [ /dev/block/8:1 ]

 Resource Group: service_1
     ip_192_168_122_201 (ocf::redhat:ip.sh):    Started crackle
 Resource Group: service_dang
     script_uhoh        (ocf::redhat:script.sh):        Started snap
 st_virt        (stonith:fence_xvm):    Started crackle

6) Kill 'snap' with 'reboot -fn'

7) Check crm_mon on 'crackle':

============
Last updated: Wed Aug 10 15:01:16 2011
Stack: cman
Current DC: crackle - partition with quorum
Version: 1.1.5-5.el6-01e86afaaa6d4a8c4836f68df80ababd6ca3902f
3 Nodes configured, unknown expected votes
4 Resources configured.
============

Online: [ crackle ]
OFFLINE: [ snap /dev/block/8:1 ]

 Resource Group: service_1
     ip_192_168_122_201 (ocf::redhat:ip.sh):    Started crackle
 Resource Group: service_dang
     script_uhoh        (ocf::redhat:script.sh):        Started crackle
st_virt (stonith:fence_xvm):    Started crackle

Failed actions:
    vm_foo_monitor_0 (node=crackle, call=4, rc=5, status=complete): not installe
d
Comment 16 Lon Hohberger 2011-08-10 19:03:32 UTC 
Oops -- the vm_foo_monitor_0 action was present in the crm_mon on snap, too, but it's a dummy resource and can be ignored.
Comment 17 Lon Hohberger 2011-08-10 19:48:41 UTC 
I have tagged ccs2cib v0.5; this can be pulled in to other projects as needed.  It still needs a bit more polish and testing, which will be performed in the mainline / master branch for now.

https://github.com/lhh/ccs2cib/tree/v0.5
Note You need to log in before you can comment on or make changes to this bug.