[Pacemaker] Why CIB is client of CCM?

[Javen Wu]

Thanks Beekhof for answering my question.
I don't mean it matters. I just feel confuse why the function seems
redundant when I tried to understand the code of pacemaker ;)

I understand the CIB should be workable without CRMD around. But is CRMD
dependant on the CIB? I think the answer is "yes".
Since CRMD must work with CIB, as long as CIB is aware of the memberhsip
change when CCM report new membership, CRMD would get notified by CIB
eventually. Am I right? I still don't understand if only CIB register to be
the client of CCM, would the pacemaker still work normally?

Thanks
Javen

2010/1/4 Andrew Beekhof <andrew at beekhof.net>

> It allows the CIB to function without the CRMD around.
> Why do you think it matters?
>
> On Tue, Dec 22, 2009 at 4:30 PM, Javen Wu <wu.javen at gmail.com> wrote:
> > Hi Beekhof & Lars,
> >
> > I found actually both Pacemaker CRMD and CIB are all clients of Heartbeat
> > CCM.  And I think CRMD would update the crm_node information once ccm
> > membership status change which reflect to CIB update eventually.
> >
> > Why CIB register itself as client still? Seems what
> cib_ccm_msg_callback()
> > does same thing as crmd_ccm_msg_callback()->do_ccm_update_cache().
> > Do I miss anything? Looking forward to your guidance.
> >
> > Thanks
> > --
> > Javen Wu
> >
>



-- 
Javen Wu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100105/31c2099a/attachment-0001.html>