On Jan 4, 12:39 pm, Daniel Pittman <dan...@rimspace.net> wrote: > That doesn't solve the problem: if the puppet master is half way through a > compilation run and you switch the repo under it, you will still see it use > mixed versions - because loading the catalog is not atomic either, and > neither is file serving. > > You actually do need to shut down the puppet master (or have it natively > support the VCS like it presently does disk) for this to be truely atomic.
Based on the way subversion and git get mentioned in much of the introductory documentation for puppet, I'd assumed they were both natively supported. I guess not. Given that's the case, wouldn't it make sense to have the puppet client that runs on the puppetmaster server be responsible for regularly updating the manifest directory from the VCS, and have that update process stop puppetmaster first, and restart it after? -- 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.
