similar to: PC EU feedback: exported resource syntax is too magical, hard to read

Displaying 20 results from an estimated 9000 matches similar to: "PC EU feedback: exported resource syntax is too magical, hard to read"

2008 Mar 22
6
pass Resources to a define or unsetting notify
Hi i''m trying to pass Resources (single or in an array) to a resource, so I can pass this to a notify or require. However I have some problems, when no resource should be passed. Maybe somebody can help me? thanks define gentoo::etcconfd ( $require = '''', $notify = '''' ){ file { "/etc/conf.d/${name}": owner =>
2007 Nov 13
7
Exported resources & exec ?
Hi, I''m sorry if that''s a FAQ, I also know exported resources are a still experimental. So my problem might well be a design limitation of how exported resources are working. My issue: I''m trying to export a file resource that is created by an exec block. The file is exported fine and collected fine but it is always empty on the other host. The puppet snippet: class
2009 Jun 25
2
Ensure overriden service after exec has run
Hi, How do I force my Service declaration (with is defined elsewhere and inherited) is run after an exec has run? The code; class autofs_nis::services inherits services::base { Service[''ypbind''] { ensure => running, enable=> true, } ..... } class autofs_nis::exec inherits services::base { exec { "setdomainname": command
2007 Nov 23
7
Modules design patterns ?
Hi, I''m writing puppet modules since a couple of weeks now, so I''m still considering myself as a new comer in this field. It seems that modules I can find on the web or the recipe page on the wiki almost all use a design pattern where the module is shipped in one or several class(es) whose configuration are determined by "global" or nodes variables ala: module: class
2010 Oct 26
7
puppetdoc and wrong comparison
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, at the moment I fight with puppetdoc and end in a ruby confusion. To the problem: > puppetdoc --debug --trace --mode rdoc --all manifests/site.pp info: scanning: ["manifests/site.pp"] /usr/lib/ruby/1.8/puppet/util/rdoc.rb:82:in `output_resource_doc'' /usr/lib/ruby/1.8/puppet/util/rdoc.rb:82:in `sort''
2010 Jun 24
3
puppet random errors
Hi, I thing this issue has been mentioned several times in this list but I can''t see any conclusion. In about 10% of all runs Puppet randomly fails on some (random) File resource either with this error: Thu Jun 24 02:40:03 +0000 2010 //<random module>/File[<random file>] (err): Failed to generate additional resources using ''eval_generate'': or this error:
2007 Nov 10
2
Array of files and other questions...
Hi I''m quite new to the art of writing puppet manifest, but the more I see, the more I like it :-) I''m trying to write a djbdns dnscache module. dnscache configuration is spread in several files, for instance the ip addresses allowed to query the cache each have a file in dnscache/root/ip/ whose filename is the address. I''m trying to automate the creations of those
2011 Oct 25
6
Regenerating puppet master certificate
Hi all, Is there a more elegant way to regenerate the Puppet master certificate than what''s described in the CVE-2011-3872 toolkit? > If you can maintain a secondary shell session to the puppet master server, you can start a WEBrick master with puppet master --no-daemonize --verbose and stop it with ctrl-C. > If you prefer to only maintain one shell session, you can start a
2010 Apr 27
7
Puppetmaster with stored configs leaks file descriptors on CentOS 5
Hi folks, When I enabled stored configs on my puppet master, it began keeping lots of open connections to the MySQL server (as far as I understand it opened one connection for each client run and never closed them). I set up the server to close idle connections after 5 minutes. Now the database server does close the connections but the puppet master keeps them in CLOSE_WAIT state and eventually
2011 Dec 19
4
Learn from MY Mistake: "false" != false
Sharing my stoopid mistake in the hopes of saving someone else the same grief: I had a boolean toggle that was not performing as expected. Long story short: I had put quotes around the word "false" class { ''foo'' : boolFlag => "false" } was coming up TRUE To fix it, lose the quotes class { ''foo'' : boolFlag => false } “Sometimes I
2009 Nov 04
22
Any ideas about this error with upgrading to 0.25.1?
Hi I''m getting this error with a 0.25.1 puppetmaster and 0.25.1 node. Nov 4 14:43:35 devcentos5 puppetd[26099]: (//network-config::base/File [hosts]) Failed to retrieve current state of resource: Error 400 on SERVER: Not authorized to call find on /file_metadata/network-config/ hosts/hosts.devcentos5 Could not retrieve file metadata for puppet:///network-config/hosts/hosts.devcentos5:
2011 May 20
3
PC EU feedback: ability to remove all unmanaged resources
http://projects.puppetlabs.com/issues/7600 I call this the "agent orange" option :) This works, purging all unmanaged hosts entries: resources { ''host'': purge => true, noop => true, } We should have a similar property for all (most?) types. Please comment on the ticket or reply here, whichever you prefer. Thanks! r P.S. This is in
2007 Nov 12
2
How to keep several puppetd in sync at the same time ?
Hi, I''m still writing my djbdns module, I came to the following design issue with master and slave tinydns. Normally there is no such master and slave distinction in djbdns: all tinydns instance are equal. Usually one instance on one host is considered the master on, which the RR are changed, and when you need to propagate them, you rsync the datas to the other hosts, where they will be
2008 Aug 04
18
puppetd daemon vs. cron
Hi, I''m running multiple vservers and have some aspects managed via puppet. I noticed that puppetd consumes from 20 to 60 mb RAM and the longer the process runs, the more RAM it takes. It looks like 60MB is the top what I measured. Having a couple of vservers (11 in my case) this can already take up to 500MB just for puppet! I''m wondering if there''s any downside in
2007 Nov 21
6
mod_proxy_balancer under heavy load.
So I''m still working on a ''perfect'' setup so I can document it on the wiki, and will submit some puppet patches against 0.23.2 next week, but here''s what I''ve done that has made a big difference to stability here. in puppetmasterd at line 261, I''ve modified the Mongrel instantiation from: server = Mongrel::HttpServer.new(addr,
2011 Dec 16
12
Seperate CA's/Master behind load balancer
Hello, Attempting to setup a CA primary/standby as well as seperate puppetmaster servers (all running Apache/Passenger) behind another Apache/Passenger type load balancer. Clients are not getting certs:- err: Could not request certificate: Could not intern from s: nested asn1 error Clearly an SSL issue but not something I know a great deal about. loadbalancer.conf # Puppet Load Balancing
2006 Apr 11
1
Postfix dovecot SASL and LDAP not working...
Hi, I'm trying to setup a new mail server where postfix 2.3-20060405 would use Dovecot's SASL and users located in LDAP. It's with dovecot-1.0-beta5. On the postfix side, I followed the SASL_README and have the following in main.cf: smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes On the dovecot side I have the following related to auth:
2010 Mar 12
23
Puppet 100% CPU usage
Hi, I''ve been experimenting with Puppet for a few days now, and I really like it. But! I''m having real CPU usage problems. Puppet is still happily eating away 100% CPU for almost an hour at a time, with no apparent things happening. (puppetd -tv --trace --debug, but nothing appearing in the console during this.) I believe the following resource is to blame: file {
2009 Aug 13
6
Mongrel Memory Usage
All, I''m trying to figure out the best way to estimate the amount of memory usage that will be taken up by Mongrel and I''m hoping that you have some estimates that can help me. I''m currently estimating the following: Memory Required = Number of running puppetmasters * size of manifests * number of clients managed The mongrel model doesn''t seem to *ever*
2012 Apr 09
14
Taking github noise away from puppet-dev list
Since our move to github for pull requests and patches, the usefulness of puppet-dev has declined significantly. puppet-dev used to be a great list for development discussion of puppet and the ecosystem around it. With the information and pull request emails from github, unless everybody has finely-tuned their email clients, the puppet-dev list has turned into mostly noise. We have a goal to