Comment 3 for bug 1505430
Revision history for this message
| Steve Baker (steve-stevebaker) wrote Re: [Bug 1505430] Re: Triggering puppet runs with config_identifier is error prone and complicates templates | #3 |
On 13/10/15 22:03, Steven Hardy wrote:
> So, yeah, as the person responsible for the current interface I agree
> it's not ideal, and I did consider something similar to what you
> described when I did it.
>
>> if the sha256sum has changed, delete any /var/run/heat-
> config/
>
> This is the problem - you have a bunch of deployment resources which are
> e.g CREATE_COMPLETE, then some hieradata changes, and we have to ensure
> all the deployments go e.g UPDATE_IN_PROGRESS, or it's impossible to
> detect any failure.
>
> So, if we go with the checksum approach, we have to take that output and
> somehow wire it in to all the puppet-applying deployments, otherwise we
> have no failure path when the puppet re-apply happens.
>
hmm, good point. I'll have a think about coupling a deployment with an
orc script that signals when hieradata changes.