On 03/13/2014 02:16 PM, Brian Pitts wrote:
Puppet is great, for sure. In this specific case, I'm not sure it would
have helped. It's still easy to have drift of packages versions in a
Puppetized environment if you aren't methodical about rolling out
updates. This is especially true for packages like the kernel, which
require intervention for the update to take effect. To solve this within
puppet, I suppose you could have it ensure that only a specific kernel
version was installed, or have it manage your GRUB configuration and
specify a specific kernel version to boot. It may be smarter to solve
the problem at the repository level.
Kent does not have to run very fast to convince me about a configuration
management system. We kinda, sorta have a home-grown set of scripts
that take the configuration management role. We do need to migrate to
one of the packages. Resources? bwahahahaha...
Brian is correct. If we build and ship five or ten a week, the time
spent on configuration management pays for itself quickly. Once a
month, the recipe has to be re-qualified every time.
Howard
--
--
You received this message because you are subscribed to the Google Groups
"NLUG" 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/nlug-talk?hl=en
---
You received this message because you are subscribed to the Google Groups "NLUG" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
