On Wednesday, May 15, 2013 9:20:37 PM UTC-5, Alex Harvey wrote: > > > I was actually thinking of doing something similar to what Stephen Gran > suggested above; let rsync can take care of ensuring that all puppet > masters always have the same copy of the same code tree. So in that > situation there is no need for the puppet masters to have access to the > revision control system. Indeed, I am not even sure that this > configuration will be any more troublesome than having the puppet masters > contact the git repositories using git pulls. > > What do you think? >
I think it's workable. Implications to consider include: - the model only makes sense if you have multiple independent contributors updating the central git repo. If there were only one, then you would probably be better off to cut out the middleman and just have that one perform the rsync. - Git still may not be the best source-control system for this purpose, as you still need action on the side of the central repo to incorporate changes pushed by remote clients. From time to time you will probably need to resolve conflicts there, as well. (As opposed to some other systems, in which conflicts are resolved by committers.) - Masters may not always be working with the most up to date manifests, and at any given time, different masters may be working with different manifest sets. None of those seem like deal-breakers to me. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
