On Tue, 2018-04-03 at 16:24 +, Sam Gardner wrote:
> "In short, I'd recommend separate constraints :) e.g. start rscA then
> promote rscB, promote rscB then start rscC."
>
> I've fiddled around with my code and gotten it to do this.
>
> Just out of curiosity, is there an upper limit on the
"In short, I'd recommend separate constraints :) e.g. start rscA then
promote rscB, promote rscB then start rscC."
I've fiddled around with my code and gotten it to do this.
Just out of curiosity, is there an upper limit on the number of individual
constraints that we can put in place?
10 or
On Mon, 2018-04-02 at 18:47 +, Sam Gardner wrote:
> Is there any way that I can order the startup of resources A, B, C in
> that order such that if B fails to start for some reason, A and C
> will still start, but the order of operations will always be start A,
> start B, start C?
>
> I've
Is there any way that I can order the startup of resources A, B, C in that
order such that if B fails to start for some reason, A and C will still start,
but the order of operations will always be start A, start B, start C?
I've tried setting it like this:
set rscA rscB.master rscC action=start
