Status Updates From Managing Infrastructure wit...

Managing Infrastructure with Puppet: Configuration Management at Scale Managing Infrastructure with Puppet: Configuration Management at Scale
by


Status Updates Showing 1-8 of 8

order by

Ragheed
Ragheed is on page 15 of 56
Jun 28, 2014 06:32AM Add a comment
Managing Infrastructure with Puppet: Configuration Management at Scale

Ivan
Ivan is on page 11 of 56
May 26, 2012 01:07PM Add a comment
Managing Infrastructure with Puppet: Configuration Management at Scale

Ivan
Ivan is on page 11 of 56
You can define client node names in the /etc/puppet/autosign.conf file in
the format agenthost.example.com or even *.example.com. Names
matching these patterns will be signed automatically by the master.
May 26, 2012 01:07PM Add a comment
Managing Infrastructure with Puppet: Configuration Management at Scale

Ivan
Ivan is on page 11 of 56
When I declare a capitalized file resource with no title, the parameters I specify
for it will become the default for that resource type
May 26, 2012 01:01PM Add a comment
Managing Infrastructure with Puppet: Configuration Management at Scale

Ivan
Ivan is on page 11 of 56
The Puppet Master and agent communicate over tcp port 8140.
May 26, 2012 12:36PM Add a comment
Managing Infrastructure with Puppet: Configuration Management at Scale

Ivan
Ivan is on page 2 of 56
"In its default
configuration, the agents work in a polling mode and check in for catalog updates every
30 minutes." - wow, I've already discovered push model via 'puppet kick'
May 26, 2012 11:59AM Add a comment
Managing Infrastructure with Puppet: Configuration Management at Scale

Alex
Alex is on page 9 of 56
Jul 20, 2011 07:25PM Add a comment
Managing Infrastructure with Puppet: Configuration Management at Scale