the implementation dosen't modify the opensafd script to lock and unlock the
clm node, instead fm checks via IMM the saClmNodeIsMember attribute, if member
is true, fencing will be performed. Changing clm admin state requires modifying
start and stop functions in opensafd script, but e.g. immfind, immadm et.al
commands may not yet be installed when opensafd start runs.
---
** [tickets:#2160] fm: Add support for differentiating a hung node versus a
stopped node **
**Status:** review
**Milestone:** 5.2.FC
**Created:** Wed Nov 02, 2016 11:37 AM UTC by Hans Nordebäck
**Last Updated:** Fri Nov 04, 2016 01:06 PM UTC
**Owner:** Hans Nordebäck
At opensafd stop, OpenSAF don't differentiate between a hung node and a stopped
node.
This ticket will implement the suggestion by AndersW from ticket [#2094], to:
1). modify the opensafd script to lock the node using CLM. The CLM lock admin
operation will remove the node from cluster membership.
2).fm_main will then be able to differentiate between a hung node and a stopped
node by checking the node for CLM cluster membership.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
