On Feb 3, 3:08 pm, Michael DeHaan <mich...@reductivelabs.com> wrote: > Actually I think it can be done by leveraging an improved storeconfigs and > the existing language.
I was wondering whether storeconfigs would come up. The problem I see with that is storeconfigs, as I understand them, record the managed resource states each host *should* have, not necessarily those each one *does* have. What happens to my multinode deployment if at some point in the middle, Puppet fails to apply a necessary resource state? > Essentially it says "this step can't continue until this remote action, > reschedule me later". Wouldn't a more Puppetly statement be "this state must not be applied until that remote state is reached, try again later"? The specific words matter, inasmuch as they shape everyone's thinking about how the system works. > Though that's conjecture... it may be quite different... but multi-node > deployment and pushed-based > actions are two seperate things, it is important to realize they are > completely orthogonal. Absolutely so, and that connects back to your earlier comments about message buses. Messaging is the lifeblood of any kind of orchestration technology, but there are a variety of message exchange patterns, message implementations, and messaging options, many combinations of which are viable. Some could reasonably be characterized as "push", but many others couldn't. Any way around, there is a class of messages needed for this that Puppet does not currently have: messages from clients advertising the individual or collective state of their managed resources. The absolute simplest form would be a reply to the Puppetmaster indicating whether a catalog was successfully applied, but finer-grained state messages would be much more flexible. These would address the problem of discrepancy between supposed and actual state. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
