[Pacemaker] A demand for the expected votes indication and a question.

[renayama19661014 at ybb.ne.jp]

Hi Andrew,

> crm_mon shouldn't really display expected votes for heartbeat
> clusters... they're not used in any way when heartbeat is in use.
> expected votes is only relevant for ver: 0 of the pacemaker/corosync plugin.
> in the future pacemaker will obtain quorum information directly from
> corosync, but at the time (openais 0.80) we didn't have that available
> to us.

All right.
There seems to have been an error in my recognition.

> > Can I judge it from a command if it cannot display expected votes in Heartbeat?
> > For example, I make use of cibadmin and crm_node and can calculate?
> 
> I dont think so, the ccm doesn't expose that information.

This is not to manage the number of the total cluster constitution that ccm is last. 
If it is the specifications of ccm in itself, there is not a way.

Best Regards,
Hideo Yamauchi.


--- Andrew Beekhof <andrew at beekhof.net> wrote:

> On Fri, Aug 6, 2010 at 7:25 AM,  <renayama19661014 at ybb.ne.jp> wrote:
> > Hi,
> >
> > Our user uses corosync and Pacemaker.
> >
> > ============
> > Last updated: Fri Aug �6 13:25:37 2010
> > Stack: openais
> > Current DC: srv01 - partition with quorum
> > Version: 1.1.2-230655711dc7b8579747ddeafc6f39247f8e87fc
> > 3 Nodes configured, 3 expected votes
> > 1 Resources configured.
> > ============
> >
> > Online: [ srv01 srv02 ]
> > OFFLINE: [ srv03 ]
> >
> >
> > This user will use Heartbeat3 and Pacemaker this time.
> >
> > When use Heartbeat, expected votes displayed by a crm_mon command is displayed in unknown.
> 
> crm_mon shouldn't really display expected votes for heartbeat
> clusters... they're not used in any way when heartbeat is in use.
> expected votes is only relevant for ver: 0 of the pacemaker/corosync plugin.
> in the future pacemaker will obtain quorum information directly from
> corosync, but at the time (openais 0.80) we didn't have that available
> to us.
> 
> >
> > ============
> > Last updated: Fri Aug �6 14:16:33 2010
> > Stack: Heartbeat
> > Current DC: srv01 (e6b19673-4e1d-42d8-a459-219342ee9bf8) - partition with quorum
> > Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b
> > 2 Nodes configured, unknown expected votes
> > 0 Resources configured.
> > ============
> >
> > Online: [ srv01 ]
> > OFFLINE: [ srv02 ]
> >
> >
> > Cannot display it in the same way as time when it combined corosync with expected votes?
> > Is this a very difficult change?
> > �* But...I know that it is PCMK service to calculate expected votes.
> > �* And I know that Heartbeat does not have similar processing.
> >
> >
> > Can I judge it from a command if it cannot display expected votes in Heartbeat?
> > For example, I make use of cibadmin and crm_node and can calculate?
> 
> I dont think so, the ccm doesn't expose that information.
> 
> >
> > Best Regards,
> > Hideo Yamauchi.
> >
> >
> >
> > _______________________________________________
> > 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
> >
> 
> _______________________________________________
> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>