On 13/04/18 11:07 +0200, Nicolas Huillard wrote:
Hello all,

One of my resources is a pppd process, which is started with the
heartbeat/anything RA. That RA just spawn the pppd process with the
correct parameters and return OCF_SUCCESS if the process started.
The problem is that the service provided by pppd is only available
after some time (a few seconds to 30s), ie. when it have successfully
negotiated a connection. At this time, the interface it creates is UP.

The issue here is that other resources that depend on this connection
are started by Pacemaker just after it starts pppd, thus before the
interface is UP. This creates various problems.

I figured that fixing this would require to add a monitor call inside
the start operation, and wait for a successful monitor before returning
OCF_SUCCESS, within the start timeout.

Is it a correct approach?
Are there some other standard way to fix this, like a "wait for
condition" Resource Agent?
You could try using the monitor_hook parameter to check the status, or
use the Delay agent between the anything resource and the other
resources.

Using Pacemaker 1.1.16 on Debian stretch.

--
Nicolas Huillard
_______________________________________________
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
_______________________________________________
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Reply via email to