Re: [Puppet Users] Re: Solaris processor count facts - bug or feature?
On Friday, December 7, 2012 9:05:32 PM UTC+11, Andrew Beresford wrote: How about creating a processorcorecount and processorthreadcount with correct meanings? That then leaves the option to deprecate processorcount. I've realised that at some point in the past I have created a processorthreadcount fact because I needed a consistent source of this information on both Solaris and Linux. I'm not sure - certainly I'd agree those would be good names for the facts if we were starting again (and should the 'processorX' facts be renamed as well)? I think for the moment I'm just going to implement the HP-UX facts to work the same way as the linux facts and create a thread on the puppet developers list to see what others think should be done about this cores vs threads connundrum. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/xUqTLQbfJwUJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] How to group hosts?
Serving facts to nodes via puppet... That means you already know those facts in puppet so you don't need to serve them to the nodes anymore :-) On Sun, Dec 9, 2012 at 1:31 AM, Jakov Sosic jso...@srce.hr wrote: On 12/06/2012 06:44 PM, Stefan Goethals wrote: Hi, You could use facter-dot-d to set a fact on those servers specifying the name of a storagegroup or a webcluster and then use that fact in your hiera hierarchy so you could have /etc/facter/facts.d/**servertype.yaml with content Thank you, I didn't know about that. I will write a class that serves /etc/puppet/private/%H/facts.**yaml into that dir, or if that file does not exist it will serve empty yaml from modules/foo/files/facts.yaml I think I will have to move to ENC very soon because this solution somehow doesn't feel good :-/ -- Jakov Sosic www.srce.unizg.hr -- 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 this group, send email to puppet-users+unsubscribe@** googlegroups.com puppet-users%2bunsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/** group/puppet-users?hl=enhttp://groups.google.com/group/puppet-users?hl=en . -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppetlabs nginx module
https://github.com/puppetlabs/puppetlabs-nginx Looking through the puppet labs nginx module and I noticed on of the first lines is: class { 'stdlib': } Isn't this pretty bad because other module that may include stdlib would cause an error? Thanks -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Working with puppet and RVM
Has anyone found an elegant solution for working with puppet and rvm? Im using the following module: https://github.com/blt04/puppet-rvm and I keep finding myself having to prefix all of my Exec resources with 'su root -c source /etc/profile.d/rvm.sh something. Any ideas? - M -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Catalog compile times 40s - Puppet 2.7.18
I am finding that the puppetlabs-apache module is somehow adding 30-60 seconds onto a host's catalog compile time when the puppetmaster has no other hosts contacting or generating catalogs. The Puppetmaster is setup to use Puppet-2.7.18 - Apache Passenger. RIght now only 2 hosts are even configured to use this new PM, the PM itself and a Foreman host. With neither hosts contacting the PM, and disabling the include apache and require apache::mod::dev in puppetlabs-passenger, I get Config retrieval: 2.45. Catalogs had hostnames replaced, puppetmaster.tld is the CNAME for Puppet master and puppetmaster-host.tld is the actual hostname. Catalog: http://pastebin.com/V29JmB8J # puppet agent --{summarize,test,debug,evaltrace,noop} | perl -pe 's/^/localtime().: /e' snip Sun Dec 9 13:05:35 2012: notice: Finished catalog run in 2.43 seconds Sun Dec 9 13:05:35 2012: Changes: Sun Dec 9 13:05:35 2012: Events: Sun Dec 9 13:05:35 2012: Total: 1 Sun Dec 9 13:05:35 2012: Noop: 1 Sun Dec 9 13:05:35 2012: Resources: Sun Dec 9 13:05:35 2012: Out of sync: 1 Sun Dec 9 13:05:35 2012: Total: 22 Sun Dec 9 13:05:35 2012: Skipped: 6 Sun Dec 9 13:05:35 2012: Time: Sun Dec 9 13:05:35 2012: Resources: 0.00 Sun Dec 9 13:05:35 2012:Filebucket: 0.00 Sun Dec 9 13:05:35 2012: Package: 0.00 Sun Dec 9 13:05:35 2012: File: 0.00 Sun Dec 9 13:05:35 2012: Firewall: 0.01 Sun Dec 9 13:05:35 2012: Exec: 0.14 Sun Dec 9 13:05:35 2012: Last run: 1355079935 Sun Dec 9 13:05:35 2012:Config retrieval: 2.45 Sun Dec 9 13:05:35 2012: Total: 2.61 Sun Dec 9 13:05:35 2012: Version: Sun Dec 9 13:05:35 2012:Config: 1355077701 Sun Dec 9 13:05:35 2012:Puppet: 2.7.18 Uncommenting include apache and require apache::mod::dev in puppetlabs-passenger about 40 seconds are added to the compile time. I went through disabled all modules and parameters, and found that enabling the passenger module alone with Apache included caused the huge delay. Catalog: http://pastebin.com/wwcKgX5b # puppet agent --{summarize,test,debug,evaltrace,noop} | perl -pe 's/^/localtime().: /e' snip Sun Dec 9 13:13:08 2012: notice: Finished catalog run in 2.23 seconds Sun Dec 9 13:13:08 2012: Changes: Sun Dec 9 13:13:08 2012: Events: Sun Dec 9 13:13:08 2012: Total: 4 Sun Dec 9 13:13:08 2012: Noop: 4 Sun Dec 9 13:13:08 2012: Resources: Sun Dec 9 13:13:08 2012: Out of sync: 4 Sun Dec 9 13:13:08 2012: Skipped: 6 Sun Dec 9 13:13:08 2012: Total: 80 Sun Dec 9 13:13:08 2012: Time: Sun Dec 9 13:13:08 2012:Filebucket: 0.00 Sun Dec 9 13:13:08 2012: Resources: 0.00 Sun Dec 9 13:13:08 2012: Package: 0.00 Sun Dec 9 13:13:08 2012: Firewall: 0.01 Sun Dec 9 13:13:08 2012: File: 0.01 Sun Dec 9 13:13:08 2012: A2mod: 0.03 Sun Dec 9 13:13:08 2012: Service: 0.07 Sun Dec 9 13:13:08 2012: Exec: 0.14 Sun Dec 9 13:13:08 2012: Last run: 1355080388 Sun Dec 9 13:13:08 2012:Config retrieval: 42.79 Sun Dec 9 13:13:08 2012: Total: 43.06 Sun Dec 9 13:13:08 2012: Version: Sun Dec 9 13:13:08 2012:Config: 1355080261 Sun Dec 9 13:13:08 2012:Puppet: 2.7.18 The install is via RPM. I'm using the Fedora SRPMs rebuilt for CentOS 6. The Puppet master has two environments, development and production with this as the puppet.conf # cat /etc/puppet/puppet.conf --- [main] server= puppetmaster.tld logdir= /var/log/puppet vardir= /var/lib/puppet ssldir= /var/lib/puppet/ssl rundir= /var/run/puppet factpath = $vardir/lib/facter pluginsync= true templatedir = $confdir/templates [agent] report = true environment = production preferred_serialization_format = yaml [master] modulepath= /etc/puppet/environments/$environment/modules:/etc/puppet/modules manifest = /etc/puppet/manifests/site.pp environment = production autosign = false ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY certname = puppetmaster.tld dns_alt_names = puppetmaster.tld,puppetmaster-host.tld report= true reports = store #reports = store, foreman [production] manifest = /etc/puppet/manifests/site.pp Has anyone run into this issue with puppetlabs-apache or know why my compile times are so long? I have a Puppet 2.6.17 server (Also Apache+Passenger) that has one host, for example, with 524 resources , and only a 21.36 second catalog compile time. Thanks - Trey -- You
Re: [Puppet Users] Does facter 2.x need cfengine key support?
On 8 December 2012 04:34, Peter Meier peter.me...@immerda.ch wrote: And why shouldn't it? Nagios is being removedhttps://groups.google.com/forum/?fromgroups=#!topic/puppet-users/qNxc2xZnRdM from core http://projects.puppetlabs.com/issues/4146. Cfengine isn't core, and falls under the same logic -- 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 this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Failed to load external library dir
I am deploying puppet/rbenv in our environment, when compiling gem via bundler, a customised library path has to be included, where can I include /etc/puppet/staging/modules/rbenv/lib ? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/yqDVKGFFUSYJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.