-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I thought I'd toss this idea out here to get pointed and laughed at before I Redmine'd it.
I ran into the fun situation recently where I needed puppet to be more atomic. Basically: (A) Update file -> (B) Restart Service But...for some reason puppet got interrupted precisely between A and B! So, the next time puppet ran, my system wasn't in the state that I had described, instead the file had been updated but the service had not been triggered. This got me thinking about the concept of atomic puppet updates. It shouldn't be too difficult to write to disk/register the state of the operations as they happen and to be able to pick back up by default if a run is interrupted. I say this, of course, completely tongue-in-cheek as the last graph discussion I jumped into went on for tons of messages! Thanks! Trevor - -- Trevor Vaughan Vice President, Onyx Point, Inc. email: [email protected] phone: 410-541-ONYX (6699) pgp: 0x6C701E94 - -- This account not approved for unencrypted sensitive information -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvzOgQACgkQyWMIJmxwHpSOxgCeKq1RCKrVbVrfucnMSJCETjQ1 eGwAoKJtS4ahaoIVFMuQGyS+VwwDogQZ =ttv5 -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
<<attachment: tvaughan.vcf>>
