On Fri, Oct 8, 2010 at 4:56 PM, Forrie <for...@gmail.com> wrote:
> That's more of what we're looking to do. I think it would be a bad
> idea to have puppet automatically updating clients. This would need
> to be a one-off, scheduled item you would trigger from the puppet
> master server, under the default {} node, I would presume;
I don't think it's a matter of working on it on the server side of puppet.
> Perhaps having the puppet (and facter) gem reside in a puppet://files/
> URL
rpm, dpkg or gems, it doesn't really change the risk, nor the
complication. You need something that says:
- stop the service
- run command X (with no calls to elements of the package itself) --
rollback if it fails
- start the service
Hard to do right.
cheers,
m
--
martin.langh...@gmail.com
mar...@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.
