I think a combination of the two makes sense, and that's what we do. Our
production masters have many environment to segregate systems. We also have a
test master with isolated CA, mcollective, PuppetDB and Foreman to test changes
to those systems.
Our test environment uses a dedicated puppet
Yup, I had noted and discussed that with my colleagues. It's got to be a
big boon. A broken Puppet that ruled them all, could cause big havoc. In
fact, I seem to remember this causing big havoc in a previous workplace,
where someone decided to "just upgrade Puppet" because the current version
w
Option (2) allows you to test upgrades to the puppet infrastructure itself,
which changes not infrequently.
On Wed, Oct 11, 2017 at 3:15 PM, Antony Gelberg
wrote:
> I've asked a similar question on the Terraform mailing-list but on
> reflection, I think it's more appropriate here.
>
> Let's say
I've asked a similar question on the Terraform mailing-list but on
reflection, I think it's more appropriate here.
Let's say I need several environments, and I'm using AWS, with each
environment in a separate VPC. I'm going to configure instances with Puppet
(and deploy with Jenkins). I see two
