Hi Sunil,
yes I know about ocfs2.pcmk, but it was absolutely not working
in previous releases, so :
- is this stack ocfs2 for pacemaker maintained , supported ?
- is it really used on some customers clusters ?
Thanks
Regards
Alain
Sunil Mushran a e'crit:
On 02/08/2011 01:32 AM, Alain.Moulle wrote:
OK but what I wonder now is :
is OCFS2 really capable of fencing an adjacent node ?
or is it only capable of "node self-fencing" ?
I thought that ocfs2 was only capable of "node self-fencing" because
there is no configuration of any fencing device (i.e. ipmi ,etc.) in the
ocfs2 configuration, so a node can't fence another node as in a HA
software (like Cluster Suite, Pacemaker, etc.)
So only "node self-fencing" possibility , right ?
So, in case of linkcom breakdown, you seem to tell me that
only the slave node will self-fence , and we can't really know
which one of both nodes will self-fence as we can't know which
one is the slave when the linkcom breakdown happens , right ?
Note that while ocfs2 comes with a default cluster stack called o2cb
it can also be configured to work with pacemaker and cman.
The previous answers were all relating to o2cb. And o2cb does not
support configurable fencing agents.
For that you'll have to use pcmk/cman. sles11, opensuse, fedora,
debian, ubuntu ship ocfs2 with pcmk/cman.
_______________________________________________
Ocfs2-users mailing list
Ocfs2-users@oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-users
_______________________________________________
Ocfs2-users mailing list
Ocfs2-users@oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-users
