This error is printed from the client - e.g. the client doesn't trust the
server..
It is possible to make it work with your setup, however I would not
recommend to work this way, either have an external CA that signs for all
puppetmasters, or use certificate chain, it simplifies the setup and
trou
On 1/12/09 1:03 PM, Joe McDonagh wrote:
> I'm sure people are doing this, possibly even in significant numbers
> because it doesn't seem too complicated. What do you see (if anything)
> as being hurdles?
Environments of modules are your friend :)
Cheers,
Ryan
--~--~-~--~~---
Oops. Replying to my own post, after re-reading one of the messages in
this group a few more times (http://groups.google.com/group/puppet-
users/msg/559819ffc956337e) while waiting for my experiments to run I
finally realised that it's relevant to my too.
It turned out that the $fileserver and $u
You could easily do the setup you mentioned. Or, if all the dispersed
nodes can access a single server, then you could even simplify with a
single puppet master. Puppet's updates are client initiated.
-adam
--~--~-~--~~~---~--~~
You received this message because y
Hello,
We are installing some Xen guests using puppet 0.24.5-1.el5 (from
http://people.redhat.com/dlutter/yum/rhel/5/x86_64/) on CentOS 5. The
Xen host is also a CentOS 5 running the same version for a puppet
master.
We have two such identical Xen hosts (running puppet master each). The
first on
On Jan 13, 4:32 pm, Luke Kanies wrote:
> > I poked around a bit on the Puppet wiki and was hoping someone could
> > add it to the list:
> >http://reductivelabs.com/trac/puppet/wiki/ManagedByPuppet
>
> You can easily make your own account and add it to the list. :)
Done!
--~--~-~--~~
On Jan 13, 2009, at 4:20 PM, Matt Ray wrote:
>
> Just thought I'd followup with the mailing list to let you know that a
> Zenoss community member has written a new Puppet module for
> automatically adding servers managed by Puppet to Zenoss. The new
> module can be found here:
> http://github.co
On Jan 13, 2009, at 2:45 PM, James Bellenger wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ohad Levy wrote:
>> How do people benchmark? anyone has a good way to simulate load?
>
> I've written up some notes on setting up a load-testing/benchmarking
> environment for puppet using
On Jan 12, 2009, at 7:14 PM, chakkerz wrote:
>
> Hello again
>
> My yaml file for puppetslave contains the fact:
> [r...@puppetbeta manifests]# grep deploysudoers /var/lib/puppet/yaml/
> facts/puppetslave.its.uq.edu.au.yaml
> deploysudoers: "false"
>
> which i note is a string (quotes), not a tr
Just thought I'd followup with the mailing list to let you know that a
Zenoss community member has written a new Puppet module for
automatically adding servers managed by Puppet to Zenoss. The new
module can be found here:
http://github.com/mamba/puppet-zenoss
I poked around a bit on the P
On Tue, 13 Jan 2009 09:42:50 -0500
Joe McDonagh wrote:
Hi,
> Is the service already running before you run it by hand?
no.
> Can you run a ps aux | grep puppet to see if puppetmasterd does
> indeed go to the background?
[r...@gridinstall ~]# !ps
ps -ef|grep puppet
root 27312 27281 0 22:51
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ohad Levy wrote:
> How do people benchmark? anyone has a good way to simulate load?
I've written up some notes on setting up a load-testing/benchmarking
environment for puppet using JMeter. I've found that it's been pretty
handy in simulating puppet
I'm sure people are doing this, possibly even in significant numbers
because it doesn't seem too complicated. What do you see (if anything)
as being hurdles?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet
Hello everybody.
I have a module (module A) with a single configuration file that i
need to populate with text depending on what other modules i am
including i a particular node. My favorite scenario would be just
including the modules i need and let them extend the configuration
file by referenc
Is the service already running before you run it by hand?
Can you run a ps aux | grep puppet to see if puppetmasterd does indeed
go to the background?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users"
That got it! Thanks Guys... My Ruby is slowly improving...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from
I created the bug, #1863
http://projects.reductivelabs.com/issues/show/1863. Thanks again for the
help.
--
Matt Marshall
-Original Message-
From: puppet-users@googlegroups.com
[mailto:puppet-us...@googlegroups.com] On Behalf Of Luke Kanies
Sent: Monday, January 12, 2009 5:38 PM
To: puppet
Hi all,
I'm with
# rpm -qa|grep puppet
puppet-server-0.24.6-1.el5
puppet-0.24.6-1.el5
Instaled from epel 5 repos.
When trying puppet with debug option with or without --no-daemonize,
puppetmasterd still goes to background:
[r...@gridinstall modules]# /usr/sbin/puppetmasterd --debug --no-
On Mon, 12 Jan 2009 17:41:11 -0600
Luke Kanies wrote:
> I'll update the FAQ; trac is being phased out, and the current
> buglist is on redmine:
>
> http://reductivelabs.com/redmine/
Thank you.
Cheers,
Arnau
--~--~-~--~~~---~--~~
You received this message because
On Mon, 2009-01-12 at 18:37 -0600, Luke Kanies wrote:
> On Jan 12, 2009, at 6:05 PM, Matt Marshall wrote:
>
> > Luke,
> > Thanks for helping with this, I believe I found out what the problem
> > is,
> > it looks like the editor I was using (eclipse) decided to use windows
> > style end of line
Hi Blake and others,
I got it running with the following gems:
actionmailer (2.0.2)
actionpack (2.0.2)
activerecord (2.0.2)
activeresource (2.0.2)
activesupport (2.0.2)
daemons (1.0.10)
gem_plugin (0.2.3)
hobofields (0.7.5)
hobosupport (0.8.5)
rails (2.0.2)
rake (0.8.3)
It only needs the hobofi
21 matches
Mail list logo
