Re: [devel] [PATCH 1/1] osaf: Isolate the node in the opensaf_reboot [#2833]

2018-04-16 Thread Anders Widell
Ok. Ack with the comment that I think you should keep the pkill -STOP commands. regards, Anders Widell On 04/16/2018 11:41 AM, Ravi Sekhar Reddy Konda wrote: HI Anders, In the opensaf_reboot script we added these commands as safe mechanism, so that we won't see issues like AMF taking

Re: [devel] [PATCH 1/1] osaf: Isolate the node in the opensaf_reboot [#2833]

2018-04-16 Thread Ravi Sekhar Reddy Konda
Hi Hans,   As I said earlier this patch is for the cases where Remote fencing is not enabled. Stonith is valid only when Remote fencing is enabled.   Also the ideal solution in this scenario is CLM taking complete responsibility of fencing the node and AMF should depend on CLM Notification

Re: [devel] [PATCH 1/1] osaf: Isolate the node in the opensaf_reboot [#2833]

2018-04-16 Thread Ravi Sekhar Reddy Konda
HI Anders, In the opensaf_reboot script we added these commands as safe mechanism, so that we won't see issues like AMF taking Active role and start assigning. But as part of this patch we are bringing down the communication mechanism, prior to killing these core saf services. So I thought

Re: [devel] [PATCH 1/1] osaf: Isolate the node in the opensaf_reboot [#2833]

2018-04-13 Thread Anders Widell
A question: why did you remove the "pkill -STOP osafamfwd" etc commands? regards, Anders Widell On 04/12/2018 03:29 PM, ravi-sekhar wrote: --- scripts/opensaf_reboot | 19 +-- 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/scripts/opensaf_reboot

Re: [devel] [PATCH 1/1] osaf: Isolate the node in the opensaf_reboot [#2833]

2018-04-13 Thread Hans Nordebäck
Hi Ravi, stonith is not only valid for virutalized environment, I assume stonith supports other e.g. ipmi in a legacy environment. The probability for "flickering" may be higher in a virtualized environment, but for redundancy there should be two interfaces configured, which is the normal

Re: [devel] [PATCH 1/1] osaf: Isolate the node in the opensaf_reboot [#2833]

2018-04-13 Thread Ravi Sekhar Reddy Konda
HI Hans,   The use case that we are addressing here is link flickering  when remote fencing is not enabled, Also remote fencing using Stonith is valid only in Virtualization environments. I have not tested using Stonith enabled as the use case is in the case where remote fencing is disabled.

Re: [devel] [PATCH 1/1] osaf: Isolate the node in the opensaf_reboot [#2833]

2018-04-12 Thread Hans Nordebäck
Hi Ravi, I think stonith, implemented in ticket #1859, handles this case. This "flickering" was one the (manual) tests verifying the added stonith support. It is important to have a separate interface for stonith, to be able to perform the remote fencing, similar to use a back plane. Have

[devel] [PATCH 1/1] osaf: Isolate the node in the opensaf_reboot [#2833]

2018-04-12 Thread ravi-sekhar
--- scripts/opensaf_reboot | 19 +-- 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/scripts/opensaf_reboot b/scripts/opensaf_reboot index df65c26..b219c39 100644 --- a/scripts/opensaf_reboot +++ b/scripts/opensaf_reboot @@ -37,6 +37,9 @@ export