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.
I'm fairly new to Puppet, and had been under the impression (based on the way VCS gets referenced in several docs) that it was natively supported. Since it appears that isn't the case, would it make sense to have the puppet client which runs on the puppet master be responsible for doing the svn update on the manifest directory, and have it do a shutdown on puppetmaster right before doing the update? I'd be surprised if someone hadn't already at least tried this, if not implemented it in production somewhere. -- 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.
