Comments for Masterzen's Blog

Comment on Puppet Extension Points – part 2 by Criando types e providers no Puppet - Gustavo Soares

Criando types e providers no Puppet - Gustavo Soares — Thu, 01 Dec 2011 18:45:19 +0000

[...] James Turnbull e do Jeff McCune. Pesquisando mais um pouco (aka, Google), cheguei no excelente link http://www.masterzen.fr/2011/11/02/puppet-extension-point-part-2 que resolvi compartilhar com vocês. tecnologias, todos [...]

Comment on The definitive recipe for WordPress Gengo to WPML conversion by Solai Luke

Solai Luke — Wed, 30 Nov 2011 23:23:11 +0000

It is a interesting article! Thanks for the idea! Along with best regards Luke aka couchgool.

Comment on Puppet Extension Points – part 1 by jacky xiao

jacky xiao — Sun, 06 Nov 2011 10:56:19 +0000

Thanks for your episode of puppet extending.
I am waiting for the “catalog evaluation” explanation.

best wishes!

Comment on Puppet Extension Points – part 1 by Puppet Extension Point – part 2

Puppet Extension Point – part 2 — Wed, 02 Nov 2011 20:01:04 +0000

[...] Nov After the first part in this series of article on Puppet extensions points, I’m proud to deliver a new episode focusing on Types [...]

Comment on Puppet Extension Points – part 1 by MarcF

MarcF — Mon, 31 Oct 2011 08:46:59 +0000

Hey, thanks for taking the time to blog about these topics !

I would be very interested about the indirector. I have always considered it black magic…

Cheers

Comment on Puppet Extension Points – part 1 by FRLinux

FRLinux — Sat, 29 Oct 2011 15:52:38 +0000

Nice seeing some new entry in there, keep it up man and welcome back

Comment on Puppet SSL explained by Puppet Extension Points – part 1

Puppet Extension Points – part 1 — Sat, 29 Oct 2011 11:17:31 +0000

[...] Oct It’s been a long time since my last blog post, almost a year. Not that I stopped hacking on Puppet or other things (even though I’m not as [...]

Comment on Benchmarking puppetmaster stacks by TomDV

TomDV — Thu, 13 Oct 2011 13:50:10 +0000

I’m running into the following error:

# ./puppet-load.rb –debug –node node1.domain –server master.domain –cert /var/lib/puppet/ssl//var/lib/puppet/ssl/certificate_requests/puppet-load.domain.pem –key /var/lib/puppet/ssl/certificate_requests/puppet-load.domain.pem –facts /etc/mcollective/facts.yaml –concurrency 1 –repeat 2
debug: reading facts from: /etc/mcollective/facts.yaml
./puppet-load.rb:235:in `[]=’: can’t convert String into Integer (TypeError)
from ./puppet-load.rb:235
from ./puppet-load.rb:230:in `each’
from ./puppet-load.rb:230

# head /etc/mcollective/facts.yaml
—
mcollective: 1
architecture: amd64
domain: domain
facterversion: 1.5.7
fqdn: node1.domain
hardwareisa: unknown
hardwaremodel: x86_64
hostname: node1
id: root

Line 235 refers to fact.values["fqdn"] = node. That won’t be converted to an integer, quite obviously.

I’m using the current version (commit 25213bfcd0
) found on https://raw.github.com/puppetlabs/puppet/master/ext/puppet-load.rb.

Any idea how to prevent this error?

Comment on Puppet SSL explained by eric sorenson

eric sorenson — Tue, 30 Aug 2011 23:24:34 +0000

Regarding the single-client-cert deployment, you need to set a few more things, including client-side changes. See https://gist.github.com/1182243

Comment on Puppet SSL explained by Andreas Koenig

Andreas Koenig — Mon, 29 Aug 2011 13:57:13 +0000

By default a client tries to connect to the “puppet” host (this can be changed with –server which I don’t recommend and is usually the source of most SSL trouble).

This sounds like you’re saying that puppet has bugs w.r.t. the server option. There is an option, so why recommend not using it? Or is the option a misfeature? Cannot be, as soon as you need two puppet masters in one domain, you’re dependent on the option.