I have a question about configuring a single Enterprise Puppet Master to
support 2 control repos.
There are 2 puppet teams who manage different puppet modules in the
organisation that I currently work for.
1. Infrastructure Team(a.k.a Production Support Team)
- manage the installatio
thanks for the useful inputs,
A solution that seems to work for us is to use a prefix as mentioned
below with R10k.
Puppet Master Enterprise console seems to support a feature called "Node
Groups". It is possible to include a node into 2 node groups, one node
group deploys the standard of
We use Puppet, hiera, r10k with a number of forge modules, roles and
profiles patterns to perform an automated deployment of a Java/NodeJS
Application.
I find r10k to be very useful in fetching all dependent modules from a
Puppetfile. However I am confused with the benefits of the r10k dynamic
I had obtained a similar error on my dev machine CentOS 6.4 with Puppet
3.4.3. Reinstalling Puppet again on my dev machine did not help.
I had noticed that the /tmp directory permissions were changed somehow in
my dev machine. I had to fix it to get puppet agent working again.
Expected :
drwx
We installed *hiera-eyaml* rubygem as the *root* user on the Puppet Master
node to encrypt/decrypt our passwords.
# /opt/puppetlabs/bin/puppetserver gem install hiera-eyaml --no-doc --no-ri
--verbose
# /opt/puppetlabs/puppet/bin/gem install hiera-eyaml --no-doc --no-ri --verbose
*eyaml* comman
We rebooted the PuppetMaster. It did not come up!
The infrastructure team built us a new PuppetMaster VM.
Hiera-Eyaml works fine now.
On Friday, 29 September 2017 14:08:58 UTC+1, vishc...@gmail.com wrote:
>
> We installed *hiera-eyaml* rubygem as the *root* user on the Puppet
> Master no
