Thank you for your input Daniele!
We're currently working to move to Puppet 3 but we've got such a large code
base, so many people committing to the repo, and so much refactoring to do
that it's a very complex and long term project. But I like a challenge! ;-)
On Wednesday, April 16, 2014
Thank you Nan!
On Wednesday, April 16, 2014 10:31:13 AM UTC-6, Nan Liu wrote:
On Mon, Apr 14, 2014 at 12:35 PM, David Danzilio
david.d...@gmail.comjavascript:
wrote:
Unfortunately, and I probably should've mentioned this in the OP, we're
currently stuck on the 2.7 series.
You should
Ah,
Then I'm afraid you're on your own. The instrumentation framework got added
and expanded upon somewhere in the 3.x series, I believe 3.2 was the first
to be able to give some useful information and as of 3.5 the API is
actually public so that others can build on it.
As far as Hiera goes,
On Mon, Apr 14, 2014 at 12:35 PM, David Danzilio
david.danzi...@gmail.comwrote:
Unfortunately, and I probably should've mentioned this in the OP, we're
currently stuck on the 2.7 series.
You should be able to run puppet master --compile certname and time it to
get a coarse measurement of
Hi,
I think a good start would be to turn on profiling, aka profiling=true in
puppet.conf or puppet agent --profile. The output will show up in the
master's logs.
--
Daniele Sluijters
On Friday, 11 April 2014 22:55:45 UTC+2, David Danzilio wrote:
Hi Everybody.
I'm trying to come up with
Unfortunately, and I probably should've mentioned this in the OP, we're
currently stuck on the 2.7 series.
On Monday, April 14, 2014 1:11:36 PM UTC-4, Daniele Sluijters wrote:
Hi,
I think a good start would be to turn on profiling, aka profiling=true in
puppet.conf or puppet agent
