Replace bootstrap_nodeid with SERVICE_short_bootstrap_node_name
This solves the problem that bootstrap_nodeid, which is set to the
first node in each role via t-h-t, can match potentially more than
one node - e.g in the event that a service is deployed such that it
spans more than one role.
The SERVICE_short_bootstrap_node_name is automatically generated
based on the composable service template service_name, and this
considers all roles where the service is enabled, e.g it should
only evaluate true once regardles off the roles where the service
is enabled.
Reviewed: https:/ /review. openstack. org/605728 /git.openstack. org/cgit/ openstack/ puppet- tripleo/ commit/ ?id=9cde9139c4f 2a59e6fca765e87 ffce42cf7da696
Committed: https:/
Submitter: Zuul
Branch: master
commit 9cde9139c4f2a59 e6fca765e87ffce 42cf7da696
Author: Steven Hardy <email address hidden>
Date: Thu Sep 27 14:57:23 2018 +0100
Replace bootstrap_nodeid with SERVICE_ short_bootstrap _node_name
This solves the problem that bootstrap_nodeid, which is set to the
first node in each role via t-h-t, can match potentially more than
one node - e.g in the event that a service is deployed such that it
spans more than one role.
The SERVICE_ short_bootstrap _node_name is automatically generated
based on the composable service template service_name, and this
considers all roles where the service is enabled, e.g it should
only evaluate true once regardles off the roles where the service
is enabled.
Change-Id: I48ec4549552910 f3cb8db960b0ff1 0a6c61b4bb9
Partial-Bug: #1792613