I'd like to model a multi-node application/service or even many
applications/services that sometimes connect. I guess I'm thinking
something along the lines of cloudformation but in puppet such that the DAG
would extend out from the node and be connected as needed. Or, should
something like cloudformation, glu, etc always be a separate layer?
Also, would it make sense at some point to have node-level changes
immediately kick off changes in other nodes (perhaps via MCollective) as
opposed to using exported resources and scheduled puppet runs to implement
changes? IOW, something like a file resource subscribing to an event such
that changes on another node that relate are immediately triggered instead
of waiting for a puppet run.
Just trying to work out some thoughts floating in my head. :)
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/ougYOJKlVS0J.
To post to this group, send email to firstname.lastname@example.org.
To unsubscribe from this group, send email to email@example.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.