The better solution would be deploying with explicit 'ignore' policy and setting it to 'stop' at post deployment orchestration stage. That would allow to scale corosync cluster w/o issues as well.
The better solution would be deploying with explicit 'ignore' policy and setting it to 'stop' at post deployment orchestration stage.
That would allow to scale corosync cluster w/o issues as well.