Improvements and simplification of the cluster scaling process. #290
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Playbook
add_pgnode.yml
Previously, you had to add a new node yourself to the pg_hba.conf file on all nodes of existing cluster before adding a new node to the cluster. Now it will be done automatically.
Previously, it was necessary to add a new node (which you want to add to existing cluster) in the [replica] group and at the same time remove other nodes from the replica group from inventory in order to add_pgnode.yml playbook was executed specifically for the new server.
Now you do not need to do this, you just need to specify the variable
new_node=true
for the server that you are adding to the cluster and the playbook will be executed only on this server.Playbook
add_balancer.yml
new_node=true
for the balancer server that you are adding to the cluster and the playbook will be executed only on this server.