On Jun 15, 2012, at 12:35 AM, David Schmitt wrote:
> No. I'm saying that either you need to manage (outside of puppet) when your
> services restart OR you don't care when your services restart.
I find this odd, since more than 90% of the parameters that puppet provides for
configuration management meet the same basic need that you are saying shouldn't
be done. I could easily rewrite your statement as:
No. I'm saying that either you need to manage (outside of puppet) when your
(resource) are updated OR you don't care when your resources are updated.
--schedules handles this
No. I'm saying that either you need to manage (outside of puppet) when where an
exec is run OR you don't care whether an exec is run.
--onlyif and --unless handle this.
No. I'm saying that either you need to manage (outside of puppet) whether a
resource is updated OR you don't care whether a resource is updated.
--require handles this
I could go on and on and on. What I propose is entirely in line with the
functionality of puppet today.
> In the first case I'd want to run puppet with --noop for consequence-checking
> and only run it "hot" in a maintenance window. In the second case the whole
> discussion is moot anyways.
I find this whole discussion very interesting, in that it shows just how small
of a team most puppet sites are. I can't fathom modifying a template to push
out a change, and being able to prevent that puppet client from picking up the
change before the next maintenance window. It's just not possible in any
reasonably sized site.
I'm thinking of sites where you edit a policy and two seconds later someone on
a different team "kicks" the host for an entirely different reason. And perhaps
they should have used a tag to limit what they kicked, but perhaps they forgot.
Or perhaps their module depends on yours so they so added your module as a tag.
And if you --noop the resource, it can actually prevent anything in their
module from making the changes they are trying to activate.
Puppet schedules do not allow for real maintenance windows. You can't limit
which days of the week, for instance.
I'm being serious here -- what I propose is entirely in line with what puppet
does today, ensure consistency, and what you are proposing is that puppet
shouldn't be involved in maintaining consistency.
--
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.
--
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.
