Code Review / apex-tripleo-heat-templates.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: ce34efd) | patch
Remove NO_SIGNAL from ControllerBootstrapNodeDeployment
authorSteven Hardy <shardy@redhat.com>
Thu, 14 May 2015 11:05:34 +0000 (07:05 -0400)
committerGiulio Fidente <gfidente@redhat.com>
Wed, 3 Jun 2015 14:30:53 +0000 (16:30 +0200)
commitb1ae63bb11ce92a584d5dbff4e3dc94564f5cb04
treebe88492468d06ac87a35554e52520487bec07c42tree | snapshot
parentce34efda2fa11dd4dc5f46877fd78a784b1b5f56commit | diff
Remove NO_SIGNAL from ControllerBootstrapNodeDeployment

We need to be sure the boostrap node data has been propagated to the
cluster before proceeding with configuration, because
ControllerNodesPostDeployment consumes the data put in place by this
and depends_on for serialization, which is essentially meaningless when
combined with NO_SIGNAL.

Change-Id: I73a1e5a2cda4c79f457bfbd9ce2836dc5c1902cc
bootstrap-config.yaml diff | blob | history
overcloud-without-mergepy.yaml diff | blob | history
puppet/bootstrap-config.yaml diff | blob | history