On Wed, 2010-08-11 at 14:49 -0400, Marc Zampetti wrote: > Thanks all for the suggestions so far. A little more info to make it > clear what I'm trying to do. > > Basically, I don't want to stop Puppet from running and managing the > rest of the system, I just don't want it changing the state of the > service itself. For example, an Apache http server is in maintenance > mode because someone is troubleshooting an issue or something like > that. I want to be able to have apache running, or not, but I don't > want apache to be started or stopped while I'm working on it. For > example, debugging some dynamic pages or something like that. I know I > can turn off puppet, and in some cases that is the better way to go. > But for some things, like say a dev or qa server, where I have other > things running that need to be kept up to date, I want the option of > controlling the service itself. Once out of maintenance, I want Puppet > to resume controlling the running state.
Check out mcollective - R.I.'s written quite a few agents that will push you in this direction already: http://code.google.com/p/mcollective/ http://www.devco.net/archives/2010/08/05/rapid_puppet_runs_with_mcollective.php http://www.devco.net/archives/2010/03/17/scheduling_puppet_with_mcollective.php Hope that's of some use, Matt -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
