Issue #2093 has been reported by pete. ---------------------------------------- Feature #2093: Disable / Enable via puppetrun http://projects.reductivelabs.com/issues/2093
Author: pete Status: Unreviewed Priority: Normal Assigned to: Category: Target version: Complexity: Unknown Affected version: 0.24.7 Keywords: I am beginning to use Puppet to control rolling upgrades across the datacenter. My plan is to disable puppet on all of the targeted machines, change the configuration, and then for each set of boxes that I want to roll, re-enable puppet and force a run. I'm not sure how others are doing it (so perhaps there's a much better way), but this currently requires sshing into each box and running puppetd --disable, and then sshing again when I want to enable them in batches. I think it would be a handy feature to be able to do this from the puppetserver: puppetrun --host=foo --host=bar --disable This would put puppetd on foo and bar so that they would still listen for puppetrun commands but would not act on any request to update, and would only act on a --disable or --enable command. Pete ---------------------------------------- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
