Hello
To debug this slowness, try the following command:
time puppet agent -t --noop --evaltrace --summarize
And look for which part is slow in the summary and possibly which
resource evaluation take too much time.
Aurélien
Le 01/12/2015 17:13, Lauro Silveira a écrit :
Hi,
Until yester
rent from undef.
Thanks anyway
On Tue, Oct 27, 2015 at 10:03:19AM +0100, DEGREMONT Aurelien wrote:
Hello
When using class parameters I often face the same issue regarding undef
usage.
Let's say I got this simple class:
class foo (
$service_ensure = 'running',
) {
service
Hello
When using class parameters I often face the same issue regarding undef
usage.
Let's say I got this simple class:
class foo (
$service_ensure = 'running',
) {
service { 'foo':
ensure => $service_ensure;
}
}
include foo # will set the service running
class { 'foo':
servic
Le 07/01/2014 02:09, rsreeniva...@gopivotal.com a écrit :
Hi
I am trying to wrap my head around how best to implement the following
functionality:
* Get information about puppet agent runs as soon as they complete
* Some kind of a callback mechanism would be ideal
Could this be done by c
Le 26/10/2013 16:18, Jason Antman a écrit :
Aurélien,
I'm a fan of the params.pp pattern, as is used in a lot of puppetlabs'
own modules. Most of the current modules use parameterized classes, so
if you're using a less-capable ENC (like the current Puppet Dashboard /
Console, ironically) you'll
Le 24/10/2013 13:23, Puppet List a écrit :
Hello
Putting the os specifics into a subclass would make locating it easy.
OK
Moving the what is supported into hiera would make that site wide and
clearer
Each os subclass could lookup and see if it is supported and if not fail
I do not see
Hello all,
As said in the subject, I did not find in puppet doc the official
recommendation in how multi-os should be handled in module manifests.
Let's say I want my module foo having classes that could be used on
Debian, RHEL6 and Fedora 10 to 18.
What would be the recommended way to manage
Le 27/06/2013 03:38, Nigel Kersten a écrit :
On Wed, Jun 26, 2013 at 9:41 AM, Nan Liu <mailto:nan@gmail.com>> wrote:
On Wed, Jun 26, 2013 at 1:33 AM, DEGREMONT Aurelien
mailto:aurelien.degrem...@cea.fr>> wrote:
It is difficult to find what's insi
Hello
It is difficult to find what's inside Puppet Enterprise (which puppet
version, etc...).
I'm particularly interested to understand what was changed to have such
gain in performances.
Thanks
Aurélien
Le 25/06/2013 15:37, Nigel Kersten a écrit :
Hello puppet-users,
Puppet Enterprise 3
R.I.Pienaar a écrit :
I wrote https://github.com/ripienaar/puppet-parselocalconfig some time
ago that can do this on the node - I am not sure if it still works with
latest puppet version but worth a try
We are using a modified version of this script and it is mandatory for us.
I do not know
Nigel Kersten a écrit :
All puppet changes are applied with explicit and manual "puppetd -t"
All interactions with puppet are manual and CLI based. Admin should manual
valid that changes that are being applied are ok.
This is the kind of use of puppet that I think it rarely speak about here ;)
Nigel Kersten a écrit :
On Mon, Jan 24, 2011 at 12:27 AM, DEGREMONT Aurelien
wrote:
Please take care that, for my site, and I think other ones,
puppetd -t
is *the* way to run puppet.
We never use puppetd in daemonized mode, and manual runs puppet when needed
with -t option.
You
Nigel Kersten a écrit :
On Sun, Jan 23, 2011 at 4:53 PM, James Louis wrote:
exactly. to what purpose?
To trigger an immediate run on a client with the common options used
when testing a real run, not a noop run.
If there was a clear word that described this functionality, we
probably
13 matches
Mail list logo
