On Fri, Apr 22, 2011 at 10:20, Arm Adam <[email protected]> wrote:
> How does puppet kick work in a scenario where a puppet master is > managing puppet masters who manage puppet masters who manage agents? Kick targets the client – agent – directly, and the agent will pull configuration. So, if you want the leaf PA in your tree to have up to date content you probably do need to kick the intermediate nodes to get them updated. (...for values of kick that mean "do whatever will sync the sub-master", which may not be done inside the puppet universe.) > Do I have to kick from the immediate Master of the agent I want to > kick? Do I first have to wait for a deployed module at the top level > puppet master to trickle down to agent's immediate puppet master or > will a puppet master look upstream if it doesn't have a module that an > agent is configured to receive (via LDAP)? So, we don't really have a built-in model for this stuff. The sub-masters are not in any way a proxy, though, and our usual model is that the sub-PMs just use the same back-end version control repository to update their local checkout. You might get other answers over on puppet-users and all, though, where some of our users have done things like this. Daniel -- ⎋ Puppet Labs Developer – http://puppetlabs.com ✉ Daniel Pittman <[email protected]> ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 ♲ Made with 100 percent post-consumer electrons -- 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.
