Running Razor provisioning
PE Master: Ubuntu 14.04, puppet 4.5.2
Razor on Centos 7
Razor Server version: 1.3.0.0
Razor Client version: 1.2.0
Configured the dnsmasq DHCP and TFTP and stocked /var/lib/tftpboot with the
2 files
[root@razor tftpboot]# ls -la
total 76
drw-r-xr-x. 2
"If your environment is simple enough...such as a single app with dev,
staging, and production operational environments, then equating a Puppet
environment to an operational environment is that much of an issue."
that should read *isn't* that much of an issue".
On Saturday, August 20, 2016 at
As Rob Nelson mentioned above, you can differentiate between operational
environments in Hiera as long as you have the appropriate facts available.
If you differentiate Puppet environments and operational environments, then
it's easier to address staged rollouts in each appropriate context.
On 20 August 2016 at 22:50, Chadwick Banning wrote:
> This is an issue I run into pretty regularly. If your Puppet infrastructure
> is even moderately complex, I'd recommend NOT equating a Puppet environment
> to an operational environment, operational environment being
Can you explain more? When you say "Having a common environment for the
common modules" that sounds like you would need to apply multiple puppet
environments to a node to get the full config...one "common" environment
and one with "non-common" configuration...and I don't think this is
currently
Lots about hiera data in this thread, how about modules? Having a common
environment for the common modules and using basemodulepath helps some, but
it's not everything.
On Sat, Aug 20, 2016 at 05:50:12AM -0700, Chadwick Banning wrote:
>This is an issue I run into pretty regularly. If your
This is an issue I run into pretty regularly. If your Puppet infrastructure
is even moderately complex, I'd recommend NOT equating a Puppet environment
to an operational environment, operational environment being the groups of
machines known as dev, qa, staging, etc.
For instance, in my