relation between heartbeat,openais,corosync

Question

This might just be a styling choice, but in case I have misunderstood something fundamental about cakePHP (or possibly all PHP frameworks) I will ask. Cakephp has many functions that take arrays of options and return them in the correct format. One example is HtmlHelper's style() function which works like so:

echo $this->Html->style(array('margin' => '10px', 'padding' => '10px'), true);

// creates
'margin:10px;padding:10px;'

When creating views should stick to these provided functions, or just write the HTML. It seems clearer and more concise to write the markup, but am I then missing out on some of the functionally gifted by the framework.

Solution

well i reached answer on myself! clustering include two part:

1.cluster resource management

2.infrastructure with massaging layer

legacy heartbeat is broken into heartbeat message layer and pacemaker so pacemaker is CRM.

and we have two option on message layer:heartbeat,openais. openais/corosync is preferred as: http://comments.gmane.org/gmane.linux.highavailability.user/32355

There are, however, features in Pacemaker that require OpenAIS which will work only with Corosync, not Heartbeat. Those features are concerned with the distributed lock managers used by cLVM (but not regular LVM), GFS/GFS2, and OCFS2. If you need that functionality, you must select OpenAIS/Corosync. If you do not, you're free to choose.

as: http://www.clusterlabs.org/wiki/FAQ

Originally Corosync and OpenAIS were the same thing. Then they split into two parts... the core messaging and membership capabilities are now called Corosync, and OpenAIS retained the layer containing the implementation of the AIS standard.

Pacemaker itself only needs the Corosync piece in order to function, however some of the applications it can manage (such as OCFS2 and GFS2) require the OpenAIS layer as well.

so i went to openais/corosync and integrate it with pacemaker.

Comments

[Admin]

We have less than a tenth of the user base of stack overflow and a much larger remit in terms of products covered by them - sounding annoyed that nobody answered your question in two days makes you sound rather spoiled and childish. As for the downvote, well it wasn't me that gave it but your question isn't very well written and a number of SF users have asked for it to be closed as it's subjective and argumentative. Coming back to SF whining won't do you any favours at all.

[floriank]

Would you mind to provide me a list of the "many" functions you think that are never needed?

[Josh Taylor]

Thank you for your answer. I can assure you I'd never write inline CSS. I referred to the style method only as simple helper function that appeared to not make things any easier. Cheers.

[floriank]

I think the reason for the style() method is that you can build custom helpers that use an array instead of a string for styles. The advantage here is that you can have a set of defaults and merge or override the passed options as needed. However, I never used it. Would you mind to provide me a list of the "many" functions you think that are never needed?