On Feb 5, 2009, at 10:53 AM, Nigel Kersten wrote: > > So we've been tossing around the idea of rsyncing our puppet manifests > onto our laptop clients and always running puppet locally. > > This is primarily due to having conditional puppet manifests that > depend upon facts that may change when the clients are offline, so the > compiled catalog doesn't change until the clients can connect to the > puppetmaster(s) again. > > On the assumption that exposing the puppet manifests themselves to the > clients doesn't create any security issues, I'm interested in people's > thoughts on the advantages of having a puppetmaster for a laptop > client base.
Setting aside the security implications, I suppose there aren't significant advantages. Well, not functional disadvantages - you obviously have another step in your deployment process, and it can be surprising how difficult it is to mentally map this step. Not that I expect you to have problems there, per se, just that I found it a real disadvantage with Cfengine, especially when doing iterative testing. If your clients will run disconnected, then you'll currently lose some reports, as they aren't queued for later delivery. -- Everything that is really great and inspiring is created by the individual who can labor in freedom. -- Albert Einstein --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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 -~----------~----~----~----~------~----~------~--~---
