Hi,
I've inherited an environment that is using Puppet 2.7. We're migrating
from one datacenter to another, but we're still running out of the old
datacenter. Some of our hardware there is reaching EOL, and it's creating a
situation that I, with my limited Puppet experience, am not really sure
Hi Roger,
Yes you can copy the critical node configuration into the spare node's.
However, it really does depend on what that critical node does and any special
requirements it has. It may have services that might need to be managed across
one by one. Or it may require one node to be shutdown
Hi David,
I've seen a setup that has an exec which fires apt-get update. This exec
has refreshonly = true. All Apt::Source resources are instantiated via a
profile class kicking off create_resources. All Apt::Source resources
notify the apt-get update exec.
I think something similar to that