-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Someone might give you a better answer, but try:
<% if tags.index('httpd') && has_variable?('httpd::open_firewall') %>
This *may not* work due to file parsing order, but I *think* that it will.
Trevor
Dick Davies wrote:
> I'm using a primitive tem
Sorry everyone. Intermittent connectivity weirdness.
On 6/10/09, Asif Iqbal wrote:
>
> In my puppet client I have
> puppet.conf defined puppet server as mypuppet
>
> server = mypuppet.example.net
>
> Not sure why the puppet client puppet-test is still sending these
> noises to the syslog
>
> Jun
I'm using a primitive template to build my iptables rulesets.
It's all in a branch on my github repo at
http://github.com/rasputnik/babysteps-puppet/tree/templated-iptables
template that looks like:
<% if has_variable?('httpd::open_firewall') %>
-A RH-Firewall-1-INPUT -m state --state NEW -m tc
On 6/10/09, Asif Iqbal wrote:
>
> In my puppet client I have
> puppet.conf defined puppet server as mypuppet
>
> server = mypuppet.example.net
>
> Not sure why the puppet client puppet-test is still sending these
> noises to the syslog
>
> Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911 da
On 6/10/09, Asif Iqbal wrote:
>
> In my puppet client I have
> puppet.conf defined puppet server as mypuppet
>
> server = mypuppet.example.net
>
> Not sure why the puppet client puppet-test is still sending these
> noises to the syslog
>
> Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911 da
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt wrote:
> A few things from the top of my head:
>
> 1) What people have done in regard to node management, as well as
> dealing with nodes that do not have static DNS names such as when
> using Ec2.
Actually I'd love to see someone do a whole sp
Thanks James.
Actually it's the same fundamental issue as
http://projects.reductivelabs.com/issues/2067
so i've amended that ticket.
I won't send a patch just yet, but at least I can pick through the code
now when I get a spare hour :) Thanks for the pointers.
On Wed, Jun 10, 2009 at 1:25
Turns out this is a bug in facter which is fixed in 1.5.5. The rpm is
available in epel-testing.
On Jun 10, 11:18 am, Christopher
wrote:
> I'm having the same exact problem here on quite a few el4 machines.
> Those that don't work are running puppet 0.24.8 whereas I do have one
> el4 that works
On Wed, Jun 10, 2009 at 9:16 AM, Jason Antman wrote:
>
> Unfortunately I haven't been able to find anything in the docs...
>
> I just built a new puppetmaster to replace my testing install on an old
> box. The hostname is different, and obviously the master certificates
> are different. What need
Very nice solution.
Thanks a lot.
BR Rene
On Jun 10, 6:08 pm, paul matthews
wrote:
> An alternate, non Puppet method is to add a pam_mkhomedir module to
> /etc/pam.d/system-auth (on a RedHat machine at least) by including the
> following line:-
>
> session required /lib/security/$IS
In my puppet client I have
puppet.conf defined puppet server as mypuppet
server = mypuppet.example.net
Not sure why the puppet client puppet-test is still sending these
noises to the syslog
Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911 daemon.error]
Could not find server : getaddrinfo:
On Wed, Jun 10, 2009 at 12:16 PM, Jason Antman wrote:
>
> Unfortunately I haven't been able to find anything in the docs...
>
> I just built a new puppetmaster to replace my testing install on an old
> box. The hostname is different, and obviously the master certificates
> are different. What need
On Wed, Jun 10, 2009 at 12:08 PM, paul matthews <
paulsmatth...@googlemail.com> wrote:
> An alternate, non Puppet method is to add a pam_mkhomedir module to
> /etc/pam.d/system-auth (on a RedHat machine at least) by including the
> following line:-
>
> session required /lib/security/$IS
Hello,
In order to celebrate our move to Portland and to help kick off Open
Source Bridge, we are hosting a Puppet get together at the Webtrends
facility on Tuesday June 16th, 2009. Both Luke Kanies and James
Turnbull will attending. This an informal get together. We will be
providing beer and
Unfortunately I haven't been able to find anything in the docs...
I just built a new puppetmaster to replace my testing install on an old
box. The hostname is different, and obviously the master certificates
are different. What needs to be done to the clients to get them to play
nice with the new
I'm having the same exact problem here on quite a few el4 machines.
Those that don't work are running puppet 0.24.8 whereas I do have one
el4 that works and it's running 0.23.0.
It doesn't seem to be puppet directly, though. I've tried downgrading
puppet to 0.22.4 (can't find the 0.23 rpm anymore
An alternate, non Puppet method is to add a pam_mkhomedir module to
/etc/pam.d/system-auth (on a RedHat machine at least) by including the
following line:-
session required /lib/security/$ISA/pam_mkhomedir.so skel=/etc/skel
umask=0022
This has the effect of creating a homedir if one do
A few things from the top of my head:
1) What people have done in regard to node management, as well as
dealing with nodes that do not have static DNS names such as when
using Ec2.
2) Success/failures on scaling puppet out to n clients
3) How it's been incorporated in to development, operations,
The agenda didn't change.
This would be in the spirit of a BarCamp or OpenSpaces conference, with some
workshops and presentations.
I think I can convince Luke to do a workshop. ;)
I was planning to send another open invitation to present to the mailing
list.
I want to keep the prepared presen
On Wed, Jun 10, 2009 at 9:15 AM, Bryan Kearney wrote:
>
> lance dillon wrote:
> > O
> >>
> >> That doesn't quite work either:
> >
> > ### print /files/etc/modprobe.conf
> > ...
> > /files/etc/modprobe.conf/alias[5] = "usb-storage"
> > /files/etc/modprobe.conf/alias[5]/modulename = "off"
> > augt
Rene wrote:
> In our environment, we have a non standard /etc/skel directory. The
> content of that directory is managed via puppet. How do I guarantee,
> that the content of that directory is on the system before a user is
> created. Do I need a require attribute on every user creation
> statement
In our environment, we have a non standard /etc/skel directory. The
content of that directory is managed via puppet. How do I guarantee,
that the content of that directory is on the system before a user is
created. Do I need a require attribute on every user creation
statement in every puppet modu
Hi,
It seems like one of the barriers to the puppet production rollout that I am
working towards will be user adoption. For this purpose, I want to manage
all common tasks with UIs that autogenerate the puppet code, so that the
admins only have to go through the full build process for custom code
lance dillon wrote:
> O
>>
>> That doesn't quite work either:
>
> ### print /files/etc/modprobe.conf
> ...
> /files/etc/modprobe.conf/alias[5] = "usb-storage"
> /files/etc/modprobe.conf/alias[5]/modulename = "off"
> augtool> match /files/etc/modprobe.conf/alias[='usb-storage']
> (error matchin
On Wed, 10 Jun 2009 05:53:44 -0700 (PDT)
Hui Hui wrote:
>
> Just to confirm the third option of sharing ca.pem among
> puppetmasters, it does work with webrick and allow clients to connect
> to any puppetmaster without further cert errors if combined with
> autosign. Very useful for cluster set
Just to confirm the third option of sharing ca.pem among
puppetmasters, it does work with webrick and allow clients to connect
to any puppetmaster without further cert errors if combined with
autosign. Very useful for cluster setups.
Cheers,
H
On Jun 9, 10:03 am, Arnau Bria wrote:
> Hi,
>
> I
On Tue, Jun 9, 2009 at 6:54 PM, David Lutterkort wrote:
>
> On Tue, 2009-06-09 at 11:57 -0400, Bryan Kearney wrote:
> > Ok.. lets try this (lutter knows this voodoo better)
>
> It's not voodoo, it's XPath ;)
>
> > "match *[alias ='usb-storage'] size = 0 "
>
> That almost works, though shouldn't t
On Wed, 10 Jun 2009 11:10:25 +0200
Arnau Bria wrote:
Hi
[...]
I've upgraded, set splay value to true and testes again (against old
server, 2 cpus, 2 GB of RAM and 8 puppetmasterd with mongrel).
My test consists of running puppet complet conf and adding a test file
(tmp/dummy). I remove the file
On Wed, 10 Jun 2009 09:47:26 +0200
David Schmitt wrote:
Hi David,
[...]
> This error means that the client timed out when waiting for the
> configuration from the puppetmasterd, marked as "Request to apply the
> configuration" in the diagram and "Configuration Transport" in the
> text.
yep,
Hi,
Can you come up with an agenda? That could help to clarify who is
paying for the trip and than I could answer the original question :)
Thanks,
Ohad
On 6/10/09, Andrew Shafer wrote:
> The best combination of location, price and facilities appears to be San
> Francisco State University.
>
>
Arnau Bria schrieb:
> My current conf splits 188 clients execution in one hour, and puppet
> runs as a cron job. My server (2cpu 2 GB RAM) runs with mongrel (with 8
> puppetmasterd) and this conf works fine.
>
> We'd like puppet to run clients all at same time (force a change, i.e.),
> so we're t
Peter Meier schrieb:
> Hi
>
> the following exec fails with the trace added:
>
> exec{"create_gitosis_git":
> command => "gitosis-init < initial_admin_pubkey.puppet",
> cwd => "/home/git",
> unless => "test -d /home/git/repositories",
> user => git,
>
32 matches
Mail list logo
