Bug 487806 - provide better distinction for clustering via openais and clustering via cman/openais
Summary: provide better distinction for clustering via openais and clustering via cman...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Messaging_Programming_Reference
Version: 1.1
Hardware: All
OS: Linux
high
medium
Target Milestone: 1.3
: ---
Assignee: Alison Young
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-27 22:47 UTC by Subhendu Ghosh
Modified: 2016-10-04 04:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-16 05:24:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Subhendu Ghosh 2009-02-27 22:47:40 UTC 
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.1/html/Messaging_User_Guide/chap-Messaging_User_Guide-Clustering_and_federation.html

This section defines 2 different methods of clustering qpid without sufficient delineation between the two.

Case 1:
qpid + openais configured via openais.conf

Features: active/active broker clusters
          support for redundant ring protocol
          does not support split-brain

Case 2:
qpid + cman configured openais via cluster.conf

Features: HW nodes are clustered using ClusterSuite (from RHEL AP)
          qpid --cluster-cman option required
          openais.conf is not needed (??)
          cluster split-brian is supported
Comment 1 Jonathan Robie 2009-09-23 14:50:11 UTC 
Fixed in the 1.2 clustering docs. 

I have not yet verified whether openais.conf is optional when using cman. Email out on that question.
Comment 3 Steven Dake 2010-03-03 08:30:22 UTC 
openais.conf is not used when aisexec is started via cman.
Comment 5 Alison Young 2011-03-16 05:24:06 UTC 
(In reply to comment #1)
> Fixed in the 1.2 clustering docs. 
> 
> I have not yet verified whether openais.conf is optional when using cman. Email
> out on that question.

Closed as fix already implemented
Note You need to log in before you can comment on or make changes to this bug.