[ClusterLabs] Order constraint with a timeout?

[Ken Gaillot]

On Mon, 2022-03-28 at 14:03 -0400, john tillman wrote:
> Greetings all,
> 
> Is it possible to have an order constraint with a timeout?  I can't
> find
> one but perhaps I am using the wrong keywords in google.
> 
> I have several Filesystem resource and one nfs service resource.  If
> I
> create 3 order constraints:
>    pcs constraint order start fsRsc1 then start myNfsServiceRsc
>    pcs constraint order start fsRsc2 then start myNfsServiceRsc
>    pcs constraint order start fsRsc3 then start myNfsServiceRsc
> 
> I would like to make sure that the nfs service will be started even
> if one
> of the Filesystem resources fails to start.  Is there a timeout that
> could
> be used?
> 
> There is the "kind=Optional" parameter but that looks like it will
> immediately start the second resource if the first failed to
> start.  There
> is no timeout option.
> 
> Best regards,
> -John
> 

How do you envision the timeout working?

You can add a timeout for the ordering itself using rules, where the
ordering no longer applies after a certain date/time, but it doesn't
sound like that's what you want.
-- 
Ken Gaillot <kgaillot at redhat.com>