Previously the completion signal was just based on the first run of
os-refresh-config. But in this case, we actually need to wait until it
runs successfully with all hosts computed. That way we can know that
services aren't in an unstable state while that configuration rolls out.
Change-Id: I3b965c19c92b366df3069cb8e1daffa18252c884
Closes-Bug: #
1337230
DependsOn: [controller0Deployment]
Type: OS::Heat::StructuredDeployment
Properties:
+ signal_transport: NO_SIGNAL
config: {Ref: NovaComputeConfig}
server: {Ref: NovaCompute0}
input_values:
Properties:
config: {Ref: AllNodesConfig}
server: {Ref: NovaCompute0}
- signal_transport: NO_SIGNAL
NovaCompute0Passthrough:
Type: OS::Heat::StructuredDeployment
Properties:
Properties:
group: os-apply-config
config:
- completion-signal: {get_input: deploy_signal_id}
admin-password:
Ref: AdminPassword
admin-token:
Properties:
config: {Ref: allNodesConfig}
server: {Ref: controller0}
- signal_transport: NO_SIGNAL
controller0Deployment:
Type: OS::Heat::StructuredDeployment
Properties:
+ signal_transport: NO_SIGNAL
config: {Ref: controllerConfig}
server: {Ref: controller0}
input_values:
Type: OS::Heat::StructuredConfig
Properties:
config:
+ completion-signal: {get_input: deploy_signal_id}
hosts:
Fn::Join:
- "\n"