Good Afternoon Puppet List,
I'm investigating the possibility of using puppet to take over an already
existing cluster of servers. Ordinarily this doesn't sound like anything out
the ordinary, but I've had my hands tied by the cluster owner saying he doesn't
want anything to break/fail while I'm wrestling the cluster to be under my
control.
Ordinarily, I'd say lets upgrade your working practices while we're at it, and
properly manage your whole workflow, manage access and manage who can make
changes. Lets start by rebuilding your boxes to specification, and migrating
your existing data over. Sounds great, "Client says no" huh? - Now I need to
rethink my strategy.
I was planning on using my current manifests, but I think I'll end up over
writing some config file that had a critical setting in it, or change a
password somewhere. Usually, I'm not too worried about that, but it did occur
to me that I don't have any real sanity checks in my modules.
• Are there any recommended ways of using puppet to take over a
production environment?
• How can I ensure that when I'm spreading my manifests across the
globe, I mean cluster, that any changes can be reverted?
• I understand that every file puppet changes, gets backed up?
Where? (embarrassed he doesn't know!)
• Finally, can I force puppet to replace changed files, or is this a
manual process?
Thanks,
-- Mister Guru
--
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.
