Alan Bishop d646c75790 Etcd: Update cluster membership when replacing a node ... Add the ability to replace an overcloud node that's running the etcd service by updating the etcd cluster's membership to delete the old node (the one being replaced) with the new replacement node. etcd maintains its cluster membership using each node's name and it's cluster peer address on the internal_api network. This data typically changes when replacing an overcloud node. The cluster membership is updated using a shell script that's triggered to run after etcd is deployed on the new node. A new EtcdInitialClusterState parameter is introduced. It defaults to "new," and only needs to be set to "existing" when the cluster membership changes. NOTE(stable/victoria): The backport dealt with conflicts due to these changes that were introduced in wallaby: - https://review.opendev.org/c/openstack/tripleo-heat-templates/+/771832 - https://review.opendev.org/c/openstack/tripleo-heat-templates/+/820111 Change-Id: I8daa5500e7ee722eef64808306dc2aa5ca027a15 (cherry picked from commit d3d20bb442) (cherry picked from commit ba22896c62) (cherry picked from commit a9a4d54232) (cherry picked from commit 13015dba81)		2022-03-28 11:24:56 -07:00
..
etcd-container-puppet.yaml	Etcd: Update cluster membership when replacing a node	2022-03-28 11:24:56 -07:00