+1 for this setup for your scenario.
I ended removing all of the ca functionality from all of the dev severs, it
makes things much simplified.
additionally you need to sign only in one place, which makes it easy to
automate it with a common build infrastructure.
Cheers,
Ohad
On Sat, Nov 7, 2009
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
I just thought I'd mention - as I do periodically - some of the
places you can get help with Puppet and Facter.
The first is this mailing list (and for development related
questions - the puppet-dev list too -
http://groups.google.com/group/p
I'm sorry.
It has become a same deal even if the host's management is made
site.pp and it executes it.
Is the setting of puppetrun amusing somewhere?
# puppetrun --host client1.devel.local -t hosts
server side
/etc/puppet/puppet.conf
[main]
vardir = /var/lib/puppet
logdir = /var/log/pup
Hello.
Puppet-0.25.1 is used and the server and the client (both CentOS5.3)
are used.
The host's management uses openldap-2.4.16.
The problem of happening,
1. The manifest is applied when starting without putting the option of
--listen and --no-client on puppetd.
2. When it starts putting the opt
