Etzion Bar-Noy

I have suggested a patch (see here my pull request: https://github.com/ClusterLabs/resource-agents/pull/1427) which will ignore this directive if the portal is not defined for 0.0.0.0 (all interfaces). This way - the...

> Can you also add the agents to doc/man/Makefile.am, so manpages are generated automatically? Done.

Fixed oraacfs permissions, so Travis can complete checks.

> Regarding the lack of stop-action. Doesnt the node get fenced when you disable the resource and monitor still reports it as running? It did not happen for me. However,...

First - I agree with you. This is a peculiar situation. I have derived this agent (and also - its name) from another agent called 'oraasm' which starts Oracle cluster,...

I do not have this testing environment anymore. I have performed start/stop operations repeatedly, and, following a very thorough test I have performed, had a production-ready environment. I cannot perform...

> It still concerns me that a monitor failure of this resource will lead to pacemaker attempting to restart it, which won't accomplish anything, and that it's not possible to...

I have had a 'clash' with PCS recently where it has detected resources to be alive, when they were not called. The 'monitor' command was buggy in that particular agent....

I know for a fact that fuser will not report a defined NFS share on an existing mount, when they are defined. The device will be in use and cannot...

Following initial tests, RHEL 7 PCS fails with several error messages, which are caused by these two problems. I've fixed them and now the resource is working fine. Thanks