Remove NO_SIGNAL from Controller|ObjectSwiftDeployment
authorSteven Hardy <shardy@redhat.com>
Thu, 14 May 2015 12:27:06 +0000 (08:27 -0400)
committerGiulio Fidente <gfidente@redhat.com>
Wed, 3 Jun 2015 14:31:29 +0000 (16:31 +0200)
We want to know this deployment succeeded, again the
ControllerAllNodesPostDeployment depends_on this, which implies
it should actually be done before doing the PostDeployment stuff,
which is impossible to determine with NO_SIGNAL.

Change-Id: I46d23bce8762ac414e4de82cf42193694aebb763

overcloud-without-mergepy.yaml

index 80e6b98..3acadf7 100644 (file)
@@ -816,14 +816,12 @@ resources:
     properties:
       config: {get_attr: [SwiftDevicesAndProxyConfig, config_id]}
       servers: {get_attr: [Controller, attributes, nova_server_resource]}
-      signal_transport: NO_SIGNAL
 
   ObjectStorageSwiftDeployment:
     type: OS::Heat::StructuredDeployments
     properties:
       config: {get_attr: [SwiftDevicesAndProxyConfig, config_id]}
       servers: {get_attr: [ObjectStorage, attributes, nova_server_resource]}
-      signal_transport: NO_SIGNAL
 
   SwiftDevicesAndProxyConfig:
     type: OS::TripleO::SwiftDevicesAndProxy::SoftwareConfig