[Puppet Users] Installing and configuring puppetmaster-passenger
So I was trying to install puppetmaster-passenger in the server machine and configure it to communicate with the agent. My server machine and client machine are both running on Ubuntu 11.04. I installed puppetmaster-passenger through apt-get and in /etc/apache2/ sites-available/puppetmaster file, in between the VirtualHost tags put ServerName as ct-vospuppet. In the server machine's apache2/httpd.conf I put a record as ServerName ct-vospuppet. (The hostname of the server is ct-vospuppet) Then I restarted apache. In the puppet.conf file in the agent machine, I put a record server=ct- vospuppet. Then I tried @cd-vgpereravos:~$ sudo puppet agent --server ct-vospuppet --test -- debug and got the following output. debug: Failed to load library 'rubygems' for feature 'rubygems' debug: Failed to load library 'selinux' for feature 'selinux' debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist debug: Puppet::Type::User::ProviderLdap: true value when expecting false debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/ dscl does not exist debug: Puppet::Type::File::ProviderMicrosoft_windows: feature microsoft_windows is missing debug: Failed to load library 'ldap' for feature 'ldap' debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/ var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/public_keys/cd- vgpereravos.domain.com.pem]: Autorequiring File[/var/lib/puppet/ssl/ public_keys] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/ lib/puppet] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/ puppet] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/run/puppet/agent.pid]: Autorequiring File[/var/run/ puppet] debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/ lib/puppet/state] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/certs/cd- vgpereravos.virtusa.com.pem]: Autorequiring File[/var/lib/puppet/ssl/ certs] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/ lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/ var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/private_keys/cd- vgpereravos.domain.com.pem]: Autorequiring File[/var/lib/puppet/ssl/ private_keys] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: Finishing transaction -614035288 debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/ lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/public_keys/cd- vgpereravos.domain.com.pem]: Autorequiring File[/var/lib/puppet/ssl/ public_keys] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/ssl/certs/cd-vgpereravos.domain.com.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/ var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/ var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/private_keys/cd- vgpereravos.domain.com.pem]: Autorequiring File[/var/lib/puppet/ssl/ private_keys] debug: Finishing transaction -614452648 debug: Using cached certificate for ca debug: Using cached certificate for cd-vgpereravos.domain.com debug: Finishing transaction -614639588 debug: Executing '/etc/puppet/etckeeper-commit-pre' debug: Using cached certificate for ca debug: Using cached certificate for cd-vgpereravos.domain.com debug: Using cached certificate_revocation_list for ca debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using pson err: Could not retrieve catalog from remote server: execution expired warning: Not using cache on failed catalog err: Could not retrieve
Re: [Puppet Users] Announce: Puppet Dashboard 1.2.10 Available
Op vrijdag 13 juli 2012 02:05:29 UTC+2 schreef Jo het volgende: Where is the documentation for this feature? How do I invoke it? The maintaining page still just says to create a cron job. the maintaining page also mentions; If you run ‘rake reports:prune’ without any arguments, it will display further usage instructions. Just installed in in our sandbox and it shows; rake reports:prune EXAMPLE: # Prune records upto 1 month old: rake reports:prune upto=1 unit=mon UNITS: Valid units of time are: mon,yr,day,min,wk,hr -- 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/-/-2VsNh8ZsS0J. 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] Announce: Puppet Dashboard 1.2.10 Available
Op vrijdag 13 juli 2012 08:50:07 UTC+2 schreef Stefan Heijmans het volgende: the maintaining page also mentions; If you run ‘rake reports:prune’ without any arguments, it will display further usage instructions. my bad, that's not the one. # rake cron:cleanup ln -sf /usr/share/puppet-dashboard/examples/puppet-dashboard.cleanup_reports.cron /etc/cron.monthly/puppet-dashboard.cleanup_reports.cron It creates a link from the source to the /etc/cron.monthly. One issue, if you have puppet-dashboard installed in a different location the source is not there. # more /etc/cron.monthly/puppet-dashboard.cleanup_reports.cron /etc/cron.monthly/puppet-dashboard.cleanup_reports.cron: No such file or directory # ll /usr/share/puppet-dashboard/examples/puppet-dashboard.cleanup_reports.cron ls: /usr/share/puppet-dashboard/examples/puppet-dashboard.cleanup_reports.cron: No such file or directory # ll /opt/puppet-dashboard/examples/puppet-dashboard.cleanup_reports.cron -rwxr-xr-x 1 puppet-dashboard puppet-dashboard 597 Jul 12 20:50 /opt/puppet-dashboard/examples/puppet-dashboard.cleanup_reports.cron # -- 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/-/NfidyMAbUNsJ. 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.
AW: [Puppet Users] How to use thin_storeconfigs
Brice, Thanks for this hint! Bernd -Ursprüngliche Nachricht- Von: puppet-users@googlegroups.com [mailto:puppet- us...@googlegroups.com] Im Auftrag von Brice Figureau Gesendet: Freitag, 6. Juli 2012 12:01 An: puppet-users@googlegroups.com Betreff: Re: [Puppet Users] How to use thin_storeconfigs On Fri, 2012-07-06 at 09:43 +0200, Bernd Adamowicz wrote: Which is the right way to use thin_storeconfigs? Currently I'm about to try this: storeconfigs = true thin_storeconfigs = true Or should it be only a single line containing the 'thin_storeconfigs' directive without 'storeconfigs=true'? You just need: thin_storeconfigs = true It will automatically enable storeconfigs for you. -- Brice Figureau Follow the latest Puppet Community evolutions on www.planetpuppet.org! -- 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. -- 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.
Re: [Puppet Users] CRAY / BlueGeneQ
Thanks for the answers, If you are using Cray Linux - I believe its based on the SuSE Linux platform (and we do support SLES 11sp1/2) - so if you have trouble I'm sure it wouldn't be hard to adapt, although it isn't a platform we have specifically targeted in the past. Some Facter patches would probably be needed to identify its version and OS - but if it works like SuSE in respect to packaging we already have the code to support zypper packages (if that is indeed what it uses) and other SuSE facilities - it all depends on the variations that Cray have taken. This is exactly the case. Since it's a Linux, I guess you can always compile and run the code, but patches like the ones you mention would be necessary, and knowing that somebody has done this before is good to know, not only in PE (which is good) but also around the community... does any? BlueGene/Q on the other hand is a PPC architecture isn't it? So what OS are you running on it? In most cases when it comes to Puppet - its the OS that matters. Yes, PPC A2 processors, but the distribution is a patched RHEL6. I guess the same as with Cray applies here: you would need patches, and knowing that someone around the community has done this before would be a great relief! Thanks, BR/Pablo -- 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] AW: What is the intention of thin_storeconfigs?
Thanks to all who gave feedback on this topic. I will have a deeper look at this issue throughout the next days and weeks and will share my experience then. Bernd -Ursprüngliche Nachricht- Von: Bernd Adamowicz Gesendet: Donnerstag, 12. Juli 2012 10:29 An: 'puppet-users@googlegroups.com' Betreff: What is the intention of thin_storeconfigs? I started doing some experiments with the configuration option 'thin_storeconfigs=true' by adding this option to one of my Puppet masters. However, I could not determine any change in behavior. I expected to have the resources collected faster, but Puppet still takes some 15min to do the job. So maybe I misunderstood something. Should this option instead be placed in the client's configuration to make them export only the @@-resources? Couldn't find any documentation. So any help is appreciated. Thanks Bernd -- 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] Re: Announce: PuppetDB 0.9.2 Available
Hey, We just got hit with the same problem on Debian Squeeze: java version 1.6.0_18 OpenJDK Runtime Environment (IcedTea6 1.8.13) (6b18-1.8.13-0+squeeze2) OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode) -- Daniele Sluijters -- 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/-/sI_eoEPcH_EJ. 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] What is the intention of thin_storeconfigs?
On 12/07/12 10:29, Bernd Adamowicz wrote: I started doing some experiments with the configuration option 'thin_storeconfigs=true' by adding this option to one of my Puppet masters. However, I could not determine any change in behavior. As others already have explained, with thin_storeconfigs, only exported resources, facts and nodes are persisted to the DB. With regular (thick) storeconfigs every resources are persisted to the database. I expected to have the resources collected faster, but Puppet still takes some 15min to do the job. The thing is that if you had run with regular storeconfigs before activating the thin_storeconfigs option, then your database is already populated with all the resources definitions and parameters. So the first time you run with thin_storeconfigs you end up collecting as if thick was activated, then after the first catalog run (for a given node), puppet should remove all the un-needed resources (ie the non exported ones) from the database. If that doesn't happen, I would suggest you to cleanup the database for your nodes so that only exported resources are persisted and collected. So maybe I misunderstood something. Should this option instead be placed in the client's configuration to make them export only the @@-resources? No, it's a master option. -- Brice Figureau My Blog: http://www.masterzen.fr/ -- 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.
Re: [Puppet Users] Announce: Puppet Dashboard 1.2.10 Available
HI I trying to upgrade for debian squeeze: (Reading database ... 66401 files and directories currently installed.) Preparing to replace librack-ruby 1.1.0-4 (using .../librack-ruby_1.1.0-4_all.deb) ... Unpacking replacement librack-ruby ... Setting up puppet-dashboard (1.2.10-1puppetlabs1) ... Starting Puppet Dashboard:Not starting Puppet Dashboard, disabled via /etc/default/puppet-dashboard ... (warning). . Starting Puppet Dashboard Workers:NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01. Gem::SourceIndex#initialize called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. [39/104900] Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:78. NOTE: Gem::SourceIndex#each is deprecated with no replacement. It will be removed on
Re: [Puppet Users] Announce: Puppet Dashboard 1.2.10 Available
Oh by the way version 1.2.9-1 works like a charm. On Fri, Jul 13, 2012 at 11:16 AM, Antidot SAS antidot...@gmail.com wrote: HI I trying to upgrade for debian squeeze: (Reading database ... 66401 files and directories currently installed.) Preparing to replace librack-ruby 1.1.0-4 (using .../librack-ruby_1.1.0-4_all.deb) ... Unpacking replacement librack-ruby ... Setting up puppet-dashboard (1.2.10-1puppetlabs1) ... Starting Puppet Dashboard:Not starting Puppet Dashboard, disabled via /etc/default/puppet-dashboard ... (warning). . Starting Puppet Dashboard Workers:NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01. Gem::SourceIndex#initialize called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. [39/104900] Gem::SourceIndex#add_spec called from /usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after
[Puppet Users] Creating Subgroups in Puppet Dashboard
Hi All, Is there a feasibility for creating subgroups on the Puppet Dashboard? Basically the requirement is that we have a huge number of VMs running designated services. Some of VMs having the same service may yet have different properties configured on them. We are exploring the feasibility of having these properties managed through puppet. Currently all these VMs are put into a single group on the Puppet Dashboard and have global properties configured on the dashboard. Can I create a subgroup among these, and configure separate properties so that when the Agent contacts the master, based on the subgroup it belongs the corresponding property values are picked up (or else the default entries are retained)??? Thank you, Praveen -- 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/-/5NBHzt379_AJ. 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] Cron Bugs
Hi, this goes mainly to puppetlabs, but I don't feel it's quite fit for the dev list, so here goes. A couple of weeks ago, I updated http://projects.puppetlabs.com/issues/593 with a proposed fix. I only now realized that there is *no* PuppetLabs employee either watching the bug or assigned to handle it. What's the official stance on this sort of thing? What happens to bugs that aren't assigned to a developer? Who should be contacted if such things are noticed, as happened here? Also, has the fixing cron initiative been abandoned for greater goals? Because if that's part of a trend, I'd find that disturbing. Thanks in advance for shedding some light. Best regards, Felix -- 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.
Re: [Puppet Users] Cron Bugs
- Original Message - From: Felix Frank felix.fr...@alumni.tu-berlin.de To: Puppet Users puppet-users@googlegroups.com Sent: Friday, July 13, 2012 10:42:45 AM Subject: [Puppet Users] Cron Bugs Hi, this goes mainly to puppetlabs, but I don't feel it's quite fit for the dev list, so here goes. A couple of weeks ago, I updated http://projects.puppetlabs.com/issues/593 with a proposed fix. I only now realized that there is *no* PuppetLabs employee either watching the bug or assigned to handle it. cant comment on the rest of your questions - but many of us dont specifically follow bugs as we get all bug mails on the projects we work on, not being followed by a PL employee doesn't mean no-one is aware. -- 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] puppet-dashboard http basic auth
Hi： I configure the puppet-dashboard with http basic auth ，but I am failed。 Software info： Dashboard： 1.2.0 Web server ：nginx 1.0.0 Who can give me a configuration case ，includes setting.yml and nginx databoard-vhost？ I'm in the following methods of allocation. ・ HTTP Basic Authentication ― When serving Dashboard via Apache, you can require a username and password to access its URLs by setting authentication rules for / in Dashboard’s vhost configuration: ・ Location / ・ Order allow,deny ・ Allow from 192.168.240.110 # your puppet master's IP ・ Satisfy any ・ AuthName Puppet Dashboard ・ AuthType Basic ・ AuthUserFile /etc/apache2/htpasswd ・ Require valid-user ・ /Location Notice that you need to leave an access exception for your puppet master(s). Although it’s possible to configure Puppet to use a password when connecting to Dashboard (by adding a username and password http://en.wikipedia.org/wiki/URI_scheme#Generic_syntax to Puppet’s reporturl and the URL used by the external_nodes script), this currently requires patching Puppet’s http report handler; see issue 7173 http://projects.puppetlabs.com/issues/7173 for more details. 工作愉快！ --- 刘亚丹 liuyadan | 游戏事业部 运维组 广州华多网络科技有限公司珠海分公司 http://www.duowan.com/ www.Duowan.com 广东珠海高新区软件园路1号A1栋13楼 (邮编 519080) 4th Floor, No. 44 Jianzhong Road, Guangzhou 510660 China T: +86 20 8555 5304 F: +86 20 8553 1397 @: liuya...@chinaduo.com M: 18666913224 QQ:540276873 YY: 909010403 广州Guangzhou | 北京Beijing | 上海Shanghai 多玩游戏 多交朋友 -- 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.
Re: [Puppet Users] Cron Bugs
Hi, On 07/13/2012 11:46 AM, R.I.Pienaar wrote: cant comment on the rest of your questions - but many of us dont specifically follow bugs as we get all bug mails on the projects we work on, not being followed by a PL employee doesn't mean no-one is aware. well, that's certainly reassuring. I guess I jumped to conclusions from the lack of any reactions. Do you suspect it's worthwhile to keep bugging (no pun intended) whomever it may concern via issue updates? Thanks, Felix -- 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.
Re: [Puppet Users] certname doesn't seem to work on the agent
Ah! It works. Thanks a lot for your help. On Friday, 13 July 2012 02:59:29 UTC+2, Pete wrote: You will need to generate the certificate with the name you want to use other wise it will use the fqdn. Try using --certname=name_you_want on the command line when you request the certificate. On 12 July 2012 21:04, Kmbu wrote: There was no current cert. It was a new host. The cert was generated using the FQDN.. On Thursday, 12 July 2012 04:42:51 UTC+2, Pete wrote: Hi, Your config looks about right. Did you drop the current cert and request and sign a new one? On 11 July 2012 19:14, Kmbu wrote: Hi guys, I have a box that needs to identify itself to the puppetmaster as something different from the FQDN. I added certname to the agent configuration before the first run, but it doesn't seem to be sufficient. The certificate was generated for the FQDN, and the host appears in the dashboard as the FQDN, and the node name used to evaluate the manifest is also the FQDN. I would like to set it up so that, for all intents and purposes, the node/agent has a different name. I'm running Puppet 2.7.6 via Apache/Passenger. Here is my agent config: [agent] # Whether log files should always flush to disk. autoflush = true # Reporting setup for Puppet Dashboard report = true # Randomize agent runs to avoid clusters splay = true # The main Puppet configuration directory. The default for this parameter is calculated based on the user. If the process # is running as root or the user that Puppet is supposed to run as, it defaults to a system directory, but if it's running as any other user, # it defaults to being in the user's home directory. # The default value is '/etc/puppet'. confdir = confdir # Where Puppet stores dynamic and growing data. The default for this parameter is calculated specially, like `confdir`_. # The default value is '/var/lib/puppet'. vardir = vardir # Whether to print stack traces on some errors trace = true # How often puppet agent applies the client configuration; in seconds. Note that a runinterval of 0 means run continuously rather than never run. # If you want puppet agent to never run, you should start it with the --no-client option. runinterval = 300 # Whether to use colors when logging to the console. # Valid values are `ansi` (equivalent to `true`), `html` (mostly # used during testing with TextMate), and `false`, which produces # no color. # The default value is 'ansi'. color = ansi # The environment Puppet is running in. For clients # (e.g., `puppet agent`) this determines the environment itself, which # is used to find modules and much more. For servers (i.e., `puppet master`) this provides the default environment for nodes # we know nothing about. # The default value is 'production'. environment = pre # Where to find information about nodes. # The default value is 'plain'. # node_terminus = plain # Where the puppet agent web server logs. # The default value is '$logdir/http.log'. httplog = logpath/http.log # Send the process into the background. This is the default. # The default value is 'true'. daemonize = true # The name to use when handling certificates. Defaults # to the fully qualified domain name. certname = dns-name-here # Where Puppet should look for facts. Multiple directories should # be colon-separated, like normal PATH variables. # The default value is '$vardir/lib/facter:$vardir/facts'. factpath = $vardir/lib/facter:$vardir/facts # From where to retrieve facts. The standard Puppet `file` type # is used for retrieval, so anything that is a valid file source can # be used here. # The default value is 'puppet://$server/facts/'. factsource = puppet://puppetmaster/facts/ # The pid file # The default value is '$rundir/$name.pid'. pidfile = vardir/agent.pid # The user puppet master should run as. # The default value is 'puppet'. user = apache # The group puppet master should run as. # The default value is 'puppet'. group = apache # Wether the master should function as a certificate authority. # The default value is 'true'. ca = true # The search path for modules as a list of directories separated by the ':' character. # The default value is '$confdir/modules:/usr/share/puppet/modules'.
Re: [Puppet Users] Cron Bugs
- Original Message - From: Felix Frank felix.fr...@alumni.tu-berlin.de To: puppet-users@googlegroups.com Sent: Friday, July 13, 2012 1:04:53 PM Subject: Re: [Puppet Users] Cron Bugs Hi, On 07/13/2012 11:46 AM, R.I.Pienaar wrote: cant comment on the rest of your questions - but many of us dont specifically follow bugs as we get all bug mails on the projects we work on, not being followed by a PL employee doesn't mean no-one is aware. well, that's certainly reassuring. I guess I jumped to conclusions from the lack of any reactions. Do you suspect it's worthwhile to keep bugging (no pun intended) whomever it may concern via issue updates? Sure, as you are no doubt aware there are many many bugs and a very long tail of idle bugs thats just out of mind. So commenting on them and asking for updates might ping someone into action or increase their view of importance of the issue, even just people saying they also have the problem and showing some code or logs from recent versions of puppet would be useful. -- 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] about puppet dashboard
Hi: I have a problem, on the same puppetmaster host, how to through the puppet dashboard management three environment: production, development and testing. Because in the puppet.conf file , ENC can only 1 configuration, like： External_nodes = / data/puppet-dashboard/bin/external_node External_node file configuration of the dashboard listen port. If I start the production on port 3000, the development on port 3001,testing on port 3002 。 How should I configuration and make the three environments also can be used。 Thank you in advance。 -- 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] Re: puppet freezes on FUTEX_WAKE_PRIVATE
We have the same problem on Ubuntu 12.04 with kernel 3.2.0-24 and puppet
2.7.11. This occurs just after info: Retrieving plugin and before loading
the facter facts. It occurs every 100th or 200th puppet run. Any hint much
appreciated!
cheers,
Thomas
On Monday, June 25, 2012 10:16:35 AM UTC+2, Ernest Beinrohr wrote:
Hi, i just want to ask whether somebody else has this problem of mine and
if it can be solved.
Many of my ( 30+ ) puppet installation freeze up after some time. The
process is waiting for some private futex, but it stays like that forever.
This is what strace looks like when the problem occures:
[pid 29173] futex(0x3d35ce7a84,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406739, {1340611695,
739433265}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 29173] clock_gettime(CLOCK_REALTIME, {1340611695, 741431552}) = 0
[pid 29173] futex(0x3d35ce7ab0, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 29173] futex(0x3d35ce7a84,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406741, {1340611695,
751431552}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 29173] clock_gettime(CLOCK_REALTIME, {1340611695, 753429831}) = 0
[pid 29173] futex(0x3d35ce7ab0, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 29173] futex(0x3d35ce7a84,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406743, {1340611695,
763429831}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 29173] clock_gettime(CLOCK_REALTIME, {1340611695, 765427460}) = 0
[pid 29173] futex(0x3d35ce7ab0, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 29173] futex(0x3d35ce7a84,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406745, {1340611695,
775427460}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 29173] clock_gettime(CLOCK_REALTIME, {1340611695, 777424282}) = 0
[pid 29173] futex(0x3d35ce7ab0, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 29173] futex(0x3d35ce7a84,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406747, {1340611695,
787424282}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 29173] clock_gettime(CLOCK_REALTIME, {1340611695, 789423203}) = 0
[pid 29173] futex(0x3d35ce7ab0, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 29173] futex(0x3d35ce7a84,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406749, {1340611695,
799423203}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 29173] clock_gettime(CLOCK_REALTIME, {1340611695, 801422477}) = 0
[pid 29173] futex(0x3d35ce7ab0, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 29173] futex(0x3d35ce7a84,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406751, {1340611695,
811422477}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 29173] clock_gettime(CLOCK_REALTIME, {1340611695, 813420142}) = 0
This happens on RHEL6 with puppet from RF (puppet-2.7.9-1.el6.rf,
ruby-1.8.7.352-7.el6_2.x86_64) and also with some mandriva I happen to have
(puppet-2.7.13-1mdv2010.2, ruby-1.8.7.p249-4.2mdv2010.2)
--
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/-/t45TtZY6dPEJ.
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] Cron Bugs
Alternatively, you can buy a support contract and mandate that it be fixed. On Fri, Jul 13, 2012 at 5:56 AM, R.I.Pienaar r...@devco.net wrote: - Original Message - From: Felix Frank felix.fr...@alumni.tu-berlin.de To: puppet-users@googlegroups.com Sent: Friday, July 13, 2012 1:04:53 PM Subject: Re: [Puppet Users] Cron Bugs Hi, On 07/13/2012 11:46 AM, R.I.Pienaar wrote: cant comment on the rest of your questions - but many of us dont specifically follow bugs as we get all bug mails on the projects we work on, not being followed by a PL employee doesn't mean no-one is aware. well, that's certainly reassuring. I guess I jumped to conclusions from the lack of any reactions. Do you suspect it's worthwhile to keep bugging (no pun intended) whomever it may concern via issue updates? Sure, as you are no doubt aware there are many many bugs and a very long tail of idle bugs thats just out of mind. So commenting on them and asking for updates might ping someone into action or increase their view of importance of the issue, even just people saying they also have the problem and showing some code or logs from recent versions of puppet would be useful. -- 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. -- 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.
Re: [Puppet Users] Re: Announce: PuppetDB 0.9.2 Available
On Fri, Jul 13, 2012 at 01:02:30AM -0700, Daniele Sluijters daniele.sluijt...@gmail.com wrote: Hey, We just got hit with the same problem on Debian Squeeze: java version 1.6.0_18 OpenJDK Runtime Environment (IcedTea6 1.8.13) (6b18-1.8.13-0+squeeze2) OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode) Indeed...as all the debian packages contain the same .jar, they'll all be similarly affected. Expect new packages momentarily...I'll notify the list once they're available! deepak -- 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.
Re: [Puppet Users] Cron Bugs
On 07/13/2012 04:14 PM, Brian Gallew wrote: Alternatively, you can buy a support contract and mandate that it be fixed. Of course. But I'm not wearing my disgruntled customer's hat but rather the concerned community member's one ;-) -- 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.
Re: [Puppet Users] CRAY / BlueGeneQ
If you are using Cray Linux - I believe its based on the SuSE Linux platform (and we do support SLES 11sp1/2) - so if you have trouble I'm sure it wouldn't be hard to adapt, although it isn't a platform we have specifically targeted in the past. Some Facter patches would probably be needed to identify its version and OS - but if it works like SuSE in respect to packaging we already have the code to support zypper packages (if that is indeed what it uses) and other SuSE facilities - it all depends on the variations that Cray have taken. This is exactly the case. Since it's a Linux, I guess you can always compile and run the code, but patches like the ones you mention would be necessary, and knowing that somebody has done this before is good to know, not only in PE (which is good) but also around the community... does any? To answer your PE question - no - 'we' (as in the collective Puppetlabs) haven't done anything for PE today and Cray Linux is not specifically supported by us today from a commercial perspective. On the other hand, I would be surprised if you couldn't get Puppet on its own to work on Cray Linux. If you get no other responses from people - I would try getting just the open source parts of Puppet to work, focusing on SuSE instructions and see how far you get, then come back to the list for help. My gut feel would be that the variations would be small enough for you to make it work. I would anticipate perhaps some Facter patches to identify your OS and mark it a SLES variant would be helpful - which is fairly easy to do. Here is an example to give you a feel for at least the Facter patch complexity, in this case we added Ascendos support (a Redhat variant): https://github.com/puppetlabs/facter/commit/c9db305096a8aa95a48bd717e752abccecea6009 Roughly 20 lines of change ... and its probably less these days since we've simplified some parts of the code since that patch. BlueGene/Q on the other hand is a PPC architecture isn't it? So what OS are you running on it? In most cases when it comes to Puppet - its the OS that matters. Yes, PPC A2 processors, but the distribution is a patched RHEL6. I guess the same as with Cray applies here: you would need patches, and knowing that someone around the community has done this before would be a great relief! If its RHEL6, then its probably going to work, I don't believe we ship PPC RPM's today though for architecture specific elements that we bundle with PE. With PE we ship our own Ruby and Apache and these are only i386 and x86_64 today. I do however believe Puppet itself (without-PE) should work, since RHEL features are usually well covered by Puppet. You just need to use all the OS bundled items like Apache and Ruby shipped with RHEL6. ken. -- 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.
Re: [Puppet Users] how to conditionally add users to a virtualized group?
On Thursday, July 12, 2012 6:04:17 PM UTC-5, Jo wrote: On Jul 12, 2012, at 2:26 PM, jcbollinger wrote: I would avoid that variation on this approach if at all possible. You would sidestep multiple pitfalls if you could determine up front, based on node name and facts, which groups are *supposed* to be present, instead of attempting to determine after the fact which were realized. Indeed, you might even find it convenient to use that information to drive group realization. If nothing else, doing so would ensure that users aren't assigned to secondary groups that don't get realized. This is what policy as expressed in the puppet manifests does. I don't see how to avoid the unrealized problem here. What's funny is that you are expressing exactly what puppet does today, but it appears you are suggesting that I need to create another data source and mirror the information out of puppet manifests into that for comparison purposes. Huh? I'm a bit baffled by the fairly constant suggestion by people here that I keep spreading out the places where information is stored. The point is to centralize the data, not provide more sources to grow inconsistent with each other. Relying on a single source of information is *exactly* what what I have suggested you do, specifically by using an up-front group list both to filter users' declared secondary groups and to drive which groups get realized. I have described that three times now, and it's included in the example code I posted earlier. You can populate such a list by whatever means you want and from whatever source you want, and you can store it wherever you want, so long as you produce the entire list before any part of it is needed. So no, I'm not suggesting you mirror information from your puppet manifests. Rather, I am suggesting that you *move* implicit information out of your manifests to someplace more accessible. Study my example if you still don't understand what I mean by that. The someplace where the information lands could be an explicit expression elsewhere in your manifests, or it could be external, as seems best to you. The information implicitly encoded in the structure of your manifests and/or developed during compilation is inherently difficult to use from within the manifests themselves, and if you insist on using it anyway then you're choosing to be stuck in an uncomfortable position. More generally, people recommending various possible data sources to you -- hiera, ENC, etc. -- are not implying that you should spread out your data. That's a function of your own manifest designs and how you use the data. You do a disservice to those volunteering their help to you by criticizing them for deficiencies in *your imagined applications* of their suggestions. John -- 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/-/ldsUjX6CCy0J. 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 conditionally add users to a virtualized group?
On 07/13/2012 05:02 PM, jcbollinger wrote: More generally, people recommending various possible data sources to you -- hiera, ENC, etc. -- are not implying that you should spread out your data. That's a function of your own manifest designs and how you use the data. You do a disservice to those volunteering their help to you by criticizing them for deficiencies in /your imagined applications/ of their suggestions. Though he did put it quite bluntly, I do believe that Jo has a point. The thing is, I generally want my manifests to be clever about some things. When I include my mysql development class, I may want to realize a couple of users and groups as a result (hypothetically speaking - I have no such class nor such requirements, but there are other things in this vein). I would tell hiera to have puppet include the mysql development class, not each single user and group. That would strike me as silly. So there *is* value in constructing information inside the manifest from outside information, or at least that is my firm belief. Configuring roles and other settings of larger granularity is what I want to do in hiera. Picking single user accounts - probably not so much. Cheers, Felix -- 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] Re: ENC questions
On Thursday, July 12, 2012 4:59:51 PM UTC-5, llo...@oreillyauto.com wrote: Our node defs are mostly classes and variables, but they also do some ordering using chaining syntax, because, for an web app server, for example, you need to make sure that Java is installed before Tomcat. I'd generally recommend that you express dependencies directly in your resources or classes, rather than using the chain operators at a higher level. As much as possible, classes and especially modules should be self-contained. A need to express dependencies outside a module (e.g. in a node definition) constitutes a failure of encapsulation, and it makes your classes and modules harder to use. We don't currently make use of Stages, and while I see their benefit, I don't know that we need them with how we are using puppet currently. I don't much care for stages, actually, and I don't see much benefit to them myself, at least as they are currently implemented. There is nothing you can do with them that you cannot do with conventional resource relationships. At best they are syntactic sugar, but in practice they are prone to problems, such as creating dependency cycles and forcing parameterized class declaration syntax even on unparametrized classes. I'd recommend that you avoid them. I'm not sure that we need an ENC either, as using the node defs is working well for us, and we typically only have one person working on a given module or node at any given time, but I want to maximize the benefit we get from puppet while making it easy to maintain and, as needed, reuse bits and pieces. It's very unlikely that you need an ENC for an installation your size. You might nevertheless find Dashboard's or Foreman's ENC features convenient, especially as your site grows. I'm not using either at the moment myself, but I keep flirting with the idea of installing one or the other. John -- 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/-/_taXaw6yQzYJ. 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] Re: puppet freezes on FUTEX_WAKE_PRIVATE
On Fri, Jul 13, 2012 at 06:30:41AM -0700, Thomas Sturm wrote: We have the same problem on Ubuntu 12.04 with kernel 3.2.0-24 and puppet 2.7.11. This occurs just after info: Retrieving plugin and before loading the facter facts. It occurs every 100th or 200th puppet run. Any hint much appreciated! cheers, Thomas Is this a relativly new issue for you? FUTEX_WAIT reminds me of the leap second kernelbug. If that's the case setting the time will fix the issue. http://serverfault.com/questions/407224/java-process-opends-consumes-all-cpu-futex-flood-how-to-debug-futex -Stefan -- 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.
Re: [Puppet Users] Installing and configuring puppetmaster-passenger
Did you put all the passenger configuration, and Listen 8140 in the puppetmaster file? You should post both the config file and your apache error log here. On Jul 12, 2012, at 11:26 PM, kalaniS wrote: So I was trying to install puppetmaster-passenger in the server machine and configure it to communicate with the agent. My server machine and client machine are both running on Ubuntu 11.04. I installed puppetmaster-passenger through apt-get and in /etc/apache2/ sites-available/puppetmaster file, in between the VirtualHost tags put ServerName as ct-vospuppet. In the server machine's apache2/httpd.conf I put a record as ServerName ct-vospuppet. (The hostname of the server is ct-vospuppet) Then I restarted apache. In the puppet.conf file in the agent machine, I put a record server=ct- vospuppet. Then I tried @cd-vgpereravos:~$ sudo puppet agent --server ct-vospuppet --test -- debug and got the following output. debug: Failed to load library 'rubygems' for feature 'rubygems' debug: Failed to load library 'selinux' for feature 'selinux' debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist debug: Puppet::Type::User::ProviderLdap: true value when expecting false debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/ dscl does not exist debug: Puppet::Type::File::ProviderMicrosoft_windows: feature microsoft_windows is missing debug: Failed to load library 'ldap' for feature 'ldap' debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/ var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/public_keys/cd- vgpereravos.domain.com.pem]: Autorequiring File[/var/lib/puppet/ssl/ public_keys] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/ lib/puppet] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/ puppet] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/run/puppet/agent.pid]: Autorequiring File[/var/run/ puppet] debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/ lib/puppet/state] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/certs/cd- vgpereravos.virtusa.com.pem]: Autorequiring File[/var/lib/puppet/ssl/ certs] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/ lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/ var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/private_keys/cd- vgpereravos.domain.com.pem]: Autorequiring File[/var/lib/puppet/ssl/ private_keys] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: Finishing transaction -614035288 debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/ lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/public_keys/cd- vgpereravos.domain.com.pem]: Autorequiring File[/var/lib/puppet/ssl/ public_keys] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/ssl/certs/cd-vgpereravos.domain.com.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/ var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/ var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/private_keys/cd- vgpereravos.domain.com.pem]: Autorequiring File[/var/lib/puppet/ssl/ private_keys] debug: Finishing transaction -614452648 debug: Using cached certificate for ca debug: Using cached certificate for cd-vgpereravos.domain.com debug: Finishing transaction -614639588 debug: Executing '/etc/puppet/etckeeper-commit-pre' debug: Using cached certificate for ca debug: Using cached
Re: [Puppet Users] Announce: Puppet Dashboard 1.2.10 Available
On Jul 12, 2012, at 11:50 PM, Stefan Heijmans wrote: the maintaining page also mentions; If you run ‘rake reports:prune’ without any arguments, it will display further usage instructions. Just installed in in our sandbox and it shows; rake reports:prune EXAMPLE: # Prune records upto 1 month old: rake reports:prune upto=1 unit=mon UNITS: Valid units of time are: mon,yr,day,min,wk,hr Hm, yes. What does that have to do with my question about the new rake job to install a cron script? -- Jo Rhett Net Consonance : net philanthropy to improve open source and internet projects. -- 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.
Re: [Puppet Users] how to conditionally add users to a virtualized group?
On Friday, July 13, 2012 10:17:25 AM UTC-5, Felix.Frank wrote: On 07/13/2012 05:02 PM, jcbollinger wrote: More generally, people recommending various possible data sources to you -- hiera, ENC, etc. -- are not implying that you should spread out your data. That's a function of your own manifest designs and how you use the data. You do a disservice to those volunteering their help to you by criticizing them for deficiencies in /your imagined applications/ of their suggestions. Though he did put it quite bluntly, I do believe that Jo has a point. Do you mean that it would be useful to have a reliable way for manifests to extract information about declarations appearing some unspecified elsewhere? I don't dispute that, but the fact is that Puppet does not have such a mechanism, and I don't see any likelihood that it will have one soon. The point is that that limitation does not create a need for data duplication, despite Jo's assertions to the contrary. The thing is, I generally want my manifests to be clever about some things. When I include my mysql development class, I may want to realize a couple of users and groups as a result (hypothetically speaking - I have no such class nor such requirements, but there are other things in this vein). I don't mean to suggest that Puppet already does the best it is possible to do in this area. Indeed, my comments to Jo are entirely about working within Puppet's current constraints, not about wishlist features. Nevertheless, the essential problem is a hard one: to determine what declarations satisfying certain criteria will have been made by the end of catalog compilation. That's the underlying problem with using defined(), using a hypothetical realized() function, building values cooperatively, and perhaps other potentially useful things. It would be convenient to be able to do those safely and reliably, but solving the key problem would likely require a fundamental change in the manifest compiler's architecture. I would tell hiera to have puppet include the mysql development class, not each single user and group. That would strike me as silly. Sure, but I'm not seeing how that relates. A more parallel situation would be if in addition, some unrelated class wanted to be able to determine which users and groups the mysql development class had declared. As Puppet now stands, the best way would be for the mysql development class to provide that data in class variables, or else to have obtained it from some shared source in the first place. The point is that neither of those options requires that data to be duplicated in the structure of the class. John -- 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/-/OvZbRRPlwpMJ. 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] Puppet 2.7.18 puppetstoredconfigclean.rb
I downloaded the tar.gz for 2.7.18. I noticed that ext/ puppetstoredconfigclean.rb is missing. Can anyone tell me where to get this script? Is it okay to use the script from 2.7.10? 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.
Re: [Puppet Users] Puppet 2.7.18 puppetstoredconfigclean.rb
On Fri, Jul 13, 2012 at 12:41:46PM -0400, Worker Bee wrote: I downloaded the tar.gz for 2.7.18. I noticed that ext/ puppetstoredconfigclean.rb is missing. Can anyone tell me where to get this script? Is it okay to use the script from 2.7.10? Thanks! The script was removed because »puppet node clean« does the same thing, see http://projects.puppetlabs.com/issues/12405 -Stefan -- 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.
Re: [Puppet Users] Puppet 2.7.18 puppetstoredconfigclean.rb
Thank you!! On Fri, Jul 13, 2012 at 1:02 PM, Stefan Schulte stefan.schu...@taunusstein.net wrote: On Fri, Jul 13, 2012 at 12:41:46PM -0400, Worker Bee wrote: I downloaded the tar.gz for 2.7.18. I noticed that ext/ puppetstoredconfigclean.rb is missing. Can anyone tell me where to get this script? Is it okay to use the script from 2.7.10? Thanks! The script was removed because »puppet node clean« does the same thing, see http://projects.puppetlabs.com/issues/12405 -Stefan -- 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. -- 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.
Re: [Puppet Users] Cron Bugs
Felix, since you have a fix (as you noted in the ticket), why don't you open a pull request and change the status of the bug to in topic branch pending review. That will also certainly get the issue noticed. On Fri, Jul 13, 2012 at 7:53 AM, Felix Frank felix.fr...@alumni.tu-berlin.de wrote: On 07/13/2012 04:14 PM, Brian Gallew wrote: Alternatively, you can buy a support contract and mandate that it be fixed. Of course. But I'm not wearing my disgruntled customer's hat but rather the concerned community member's one ;-) -- 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. -- Matthaus Litteken Release Manager, Puppet Labs -- 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.
Re: [Puppet Users] how to conditionally add users to a virtualized group?
On Jul 13, 2012, at 8:02 AM, jcbollinger wrote: Relying on a single source of information is exactly what what I have suggested you do, specifically by using an up-front group list both to filter users' declared secondary groups and to drive which groups get realized. I have described that three times now, and it's included in the example code I posted earlier. You can populate such a list by whatever means you want and from whatever source you want, and you can store it wherever you want, so long as you produce the entire list before any part of it is needed. I did not see that from what you showed. Your example didn't show how to aggregate or use the data at all. I saw six classes that were significantly more complex and appeared to require defining the data in multiple places. There was certainly no obvious way this would reduce my data sources. So no, I'm not suggesting you mirror information from your puppet manifests. Rather, I am suggesting that you move implicit information out of your manifests to someplace more accessible. Study my example if you still don't understand what I mean by that. The someplace where the information lands could be an explicit expression elsewhere in your manifests, or it could be external, as seems best to you. The information implicitly encoded in the structure of your manifests and/or developed during compilation is inherently difficult to use from within the manifests themselves, and if you insist on using it anyway then you're choosing to be stuck in an uncomfortable position. I hear what you are saying, but I really don't see how your example makes this idea clear. I saw multiple sets of classes relying on each other's data in an unreadable manner. I would argue that even if it does do what I meant, the very fact that I couldn't read it to understand this ensures nobody else here has a chance at maintaining it. More complex is not a desired trait here. In general I see ENCs as eventually providing a way to simplify the data input, but that's not what I've seen recommended or demonstrated. The case for ENCs would be made a lot stronger if some good examples of ways to simply via the use of ENCs were posted. More generally, people recommending various possible data sources to you -- hiera, ENC, etc. -- are not implying that you should spread out your data. That's a function of your own manifest designs and how you use the data. You do a disservice to those volunteering their help to you by criticizing them for deficiencies in your imagined applications of their suggestions. I could go back and make a line by line review of every single time people have told me that I should take data from the puppet manifests and reinforce it / control it via data from an ENC. There hasn't been a single situation where someone said what you are suggesting -- hey, pull this all out of puppet and incorporate it this way (x) so that you can get what you want. It has always been how to do half the job in puppet and half the job in something else, and manually manage the dependancies between the two. -- Jo Rhett Net Consonance : net philanthropy to improve open source and internet projects. -- 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] Modeling higher level services
Will Puppet ever enable the modeling of higher level resources (than node). I'd like to model a multi-node application/service or even many applications/services that sometimes connect. I guess I'm thinking something along the lines of cloudformation but in puppet such that the DAG would extend out from the node and be connected as needed. Or, should something like cloudformation, glu, etc always be a separate layer? Also, would it make sense at some point to have node-level changes immediately kick off changes in other nodes (perhaps via MCollective) as opposed to using exported resources and scheduled puppet runs to implement changes? IOW, something like a file resource subscribing to an event such that changes on another node that relate are immediately triggered instead of waiting for a puppet run. Just trying to work out some thoughts floating in my head. :) Kind Regards, Mark -- 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/-/ougYOJKlVS0J. 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] Announce: Puppet Dashboard 1.2.10 Available
Jo, To invoke the new rake task, run `rake cron:cleanup` in /usr/share/puppet-dashboard. The example script that is installed can be viewed in /usr/share/puppet-dashboard/examples. I will be submitting a pull request to the puppet-docs project shortly to update the dashboard documentation. Thanks, -Will On Jul 13, 2012, at 9:36 AM, Jo Rhett wrote: On Jul 12, 2012, at 11:50 PM, Stefan Heijmans wrote: the maintaining page also mentions; If you run ‘rake reports:prune’ without any arguments, it will display further usage instructions. Just installed in in our sandbox and it shows; rake reports:prune EXAMPLE: # Prune records upto 1 month old: rake reports:prune upto=1 unit=mon UNITS: Valid units of time are: mon,yr,day,min,wk,hr Hm, yes. What does that have to do with my question about the new rake job to install a cron script? -- Jo Rhett Net Consonance : net philanthropy to improve open source and internet projects. -- 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. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Puppet Users] Re: How can I list classes available on the puppet master?
Nan, I just assigned https://projects.puppetlabs.com/issues/7079 to
you, it would be awesome if you could let us know in that ticket if
your sample code suffers the same problem of classes with the same
name as a node masking the existence of that node.
On Thu, Jul 12, 2012 at 5:17 PM, Nan Liu n...@puppetlabs.com wrote:
So this is turning it into a small coding contest =). I needed
something similar to this, and there's a pretty easy way to do this
with the puppet resource_type face.
require 'puppet'
require 'puppet/face'
Puppet::Face[:resource_type,:current].search('*').find_all {|x|
x.type==:hostclass}.collect{|x| x.name}.sort
You can do some interesting things, such as get all the classes
parameters as well:
Puppet::Face[:resource_type,:current].search('*').find_all {|x|
x.type==:hostclass}.collect{|x| {x.name=x.arguments.keys}}
Here's an example of classes and parameters it accept:
[{apt::backports=[release, location]},
{apt::debian::testing=[]},
{apt::debian::unstable=[]},
{apt::params=[]},
{apt::release=[release_id]},
{apt::update=[]},
{apt=
[purge_sources_list_d,
purge_sources_list,
always_apt_update,
proxy_host,
proxy_port,
purge_preferences_d,
disable_keys]},
...
Thanks,
Nan
On Thu, Jul 12, 2012 at 9:50 AM, Nick Cammorato nick_cammor...@terc.edu
wrote:
You could do something like this, it's not the cleanest in the world(I
barely ever use sed anymore), but as something quick and dirty:
curl -k -H Accept: yaml https://puppet:8140/mgmt/resource_types/class |
more | grep name: | sed -e 's/^ *name: //;s/id.* //' | sort | uniq
It'll have some bad data you'll have to parse out(built-in classes like
notify, fail, etc.), but should work.
On Thursday, July 12, 2012 11:54:25 AM UTC-4, llo...@oreillyauto.com wrote:
Is there a way to get a list of all the classes available from the puppet
master?
I have 2 goals for this - one is documentation in a human readable form,
and the other is potentially importing that data into dashboard.
I did find some info on the rest API
(http://docs.puppetlabs.com/guides/rest_api.html#resource-types ) but I
can't make any sense of the output from it.
Thanks.
Lee
On Thursday, July 12, 2012 11:54:25 AM UTC-4, llo...@oreillyauto.com wrote:
Is there a way to get a list of all the classes available from the puppet
master?
I have 2 goals for this - one is documentation in a human readable form,
and the other is potentially importing that data into dashboard.
I did find some info on the rest API
(http://docs.puppetlabs.com/guides/rest_api.html#resource-types ) but I
can't make any sense of the output from it.
Thanks.
Lee
On Thursday, July 12, 2012 11:54:25 AM UTC-4, llo...@oreillyauto.com wrote:
Is there a way to get a list of all the classes available from the puppet
master?
I have 2 goals for this - one is documentation in a human readable form,
and the other is potentially importing that data into dashboard.
I did find some info on the rest API
(http://docs.puppetlabs.com/guides/rest_api.html#resource-types ) but I
can't make any sense of the output from it.
Thanks.
Lee
On Thursday, July 12, 2012 11:54:25 AM UTC-4, llo...@oreillyauto.com wrote:
Is there a way to get a list of all the classes available from the puppet
master?
I have 2 goals for this - one is documentation in a human readable form,
and the other is potentially importing that data into dashboard.
I did find some info on the rest API
(http://docs.puppetlabs.com/guides/rest_api.html#resource-types ) but I
can't make any sense of the output from it.
Thanks.
Lee
--
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/-/m4XmKKAYwtkJ.
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.
--
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.
--
Nigel Kersten | http://puppetlabs.com | @nigelkersten
Schedule Meetings at: http://tungle.me/nigelkersten
--
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.
Re: [Puppet Users] Re: Announce: PuppetDB 0.9.2 Available
All, New puppetdb 0.9.2 deb packages are available on apt.puppetlabs.com that should resolve these issues. The package version is 0.9.2-1puppetlabs2. As always, please let us know if you encounter issues. Thanks for your patience while we ironed this out. Cheers, Moses On Fri, Jul 13, 2012 at 7:39 AM, Deepak Giridharagopal dee...@puppetlabs.com wrote: On Fri, Jul 13, 2012 at 01:02:30AM -0700, Daniele Sluijters daniele.sluijt...@gmail.com wrote: Hey, We just got hit with the same problem on Debian Squeeze: java version 1.6.0_18 OpenJDK Runtime Environment (IcedTea6 1.8.13) (6b18-1.8.13-0+squeeze2) OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode) Indeed...as all the debian packages contain the same .jar, they'll all be similarly affected. Expect new packages momentarily...I'll notify the list once they're available! deepak -- 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. -- 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] State of Puppet 3.0 and our commitment to quality
As many of you have doubtless noticed, Puppet 3 and Facter 2 have been sitting in RC (Release Candidate process) for a long time. That's about to change, but they won't be getting released as they currently stand. Puppet 3 and Facter 2 have been pulled out of the RC process after we recognized that the performance needed to be worked on and the reworked pluginsync was not going to solve the problems that we had aimed for it to solve. What this means is the Facter 2.0rc and Puppet 3.0rc branches will be removed, and work will be targeted at the Facter 2.x and Puppet 3.x branches. When they are ready for release we will restart their rc process, continuing from the last rc tag. In order for us to be able to concentrate on getting things right, we are going to concentrate all of our efforts on 3.0 until it is out. After it is out we'll move to an alternating release cadence between the Puppet 2.7/Facter 1.6 series and the Puppet 3.x/Facter 2.x series. At this point Puppet 2.7/Facter 1.6 will be in bug fix only mode, all new features will go into the Puppet 3.x/Facter 2.x series. One reason for the Puppet 3 and Facter 2 (and Hiera 1) releases to to reset our version number system to match SemVer (seehttp://semver.org for more information about what exactly that is, if you are not familiar with it). At the moment it is still a little bit up in the air how we are going to try to focus work on 3.0.y bug fixes and new, backward compatible features for later 3.x versions. We'll keep you posted as we come up with a plan. If you have questions or concerns, please let us know. Mike Stahnke Community Manager -- 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.
Re: [Puppet Users] Announce: Puppet Dashboard 1.2.10 Available
Op vrijdag 13 juli 2012 18:36:41 UTC+2 schreef Jo het volgende: Hm, yes. What does that have to do with my question about the new rake job to install a cron script? absolutely nothing, as stated in my 2nd post about it :) -- 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/-/kotzCbdij7YJ. 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] Re: qualified variables in templates
what is the incantation that would work for iteration?
scope.lookupvar('::varname').each
Produces puppet error: undefined method `each' for :undefined:Symbol
On Tuesday, September 20, 2011 2:53:35 PM UTC-4, Alessandro Franceschi
wrote:
Use something like %= scope.lookupvar('hostname') %
--
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/-/popQN56eqs8J.
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] Modeling higher level services
On Fri, Jul 13, 2012 at 2:18 PM, Mark Roggenkamp mark.roggenk...@gmail.com wrote: Will Puppet ever enable the modeling of higher level resources (than node). I'd like to model a multi-node application/service or even many applications/services that sometimes connect. I guess I'm thinking something along the lines of cloudformation but in puppet such that the DAG would extend out from the node and be connected as needed. Or, should something like cloudformation, glu, etc always be a separate layer? I can't speak for Puppetlabs, but I would imagine that at some point service orchestration is something they should want to tackle, by building something on top of mcollective and puppetdb, but for now, the options I am aware of (In no particular order): 1) Glu http://linkedin.github.com/glu/docs/latest/html/tutorial.html 2) KermIT http://kermit.fr/kermit/ 3) Juju https://juju.ubuntu.com/ 4) Foreman-stacker https://github.com/ohadlevy/stacker (Not sure the status). 5) CloudFormation (AWS specific) 6) http://rundeck.org/ I just saw a talk on Juju, and it looks pretty interesting.. (Interesting enough, that I will be testing it in the lab.) Cheers, Brian Also, would it make sense at some point to have node-level changes immediately kick off changes in other nodes (perhaps via MCollective) as opposed to using exported resources and scheduled puppet runs to implement changes? IOW, something like a file resource subscribing to an event such that changes on another node that relate are immediately triggered instead of waiting for a puppet run. Just trying to work out some thoughts floating in my head. :) Kind Regards, Mark -- 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/-/ougYOJKlVS0J. 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. -- 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.
Re: [Puppet Users] Announce: Puppet Dashboard 1.2.10 Available
All, New puppet-dashboard 1.2.10 deb packages are available on apt.puppetlabs.com that should resolve the issue of the missing configuration file. The package version is 1.2.10-1puppetlabs2. Thanks for your patience while we worked this fix out. Please let us know if you encounter any issues. Thanks, Will signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Puppet Users] Re: How can I list classes available on the puppet master?
It doesn't seem to have the issue:
Puppet::Face[:resource_type,:current].search('*').collect{|x| x.type}
= [:hostclass, :node]
Puppet::Face[:resource_type,:current].search('demo').collect{|x| x.type}
= [:hostclass, :node]
Nan
On Fri, Jul 13, 2012 at 11:41 AM, Nigel Kersten ni...@puppetlabs.com wrote:
Nan, I just assigned https://projects.puppetlabs.com/issues/7079 to
you, it would be awesome if you could let us know in that ticket if
your sample code suffers the same problem of classes with the same
name as a node masking the existence of that node.
On Thu, Jul 12, 2012 at 5:17 PM, Nan Liu n...@puppetlabs.com wrote:
So this is turning it into a small coding contest =). I needed
something similar to this, and there's a pretty easy way to do this
with the puppet resource_type face.
require 'puppet'
require 'puppet/face'
Puppet::Face[:resource_type,:current].search('*').find_all {|x|
x.type==:hostclass}.collect{|x| x.name}.sort
You can do some interesting things, such as get all the classes
parameters as well:
Puppet::Face[:resource_type,:current].search('*').find_all {|x|
x.type==:hostclass}.collect{|x| {x.name=x.arguments.keys}}
Here's an example of classes and parameters it accept:
[{apt::backports=[release, location]},
{apt::debian::testing=[]},
{apt::debian::unstable=[]},
{apt::params=[]},
{apt::release=[release_id]},
{apt::update=[]},
{apt=
[purge_sources_list_d,
purge_sources_list,
always_apt_update,
proxy_host,
proxy_port,
purge_preferences_d,
disable_keys]},
...
Thanks,
Nan
On Thu, Jul 12, 2012 at 9:50 AM, Nick Cammorato nick_cammor...@terc.edu
wrote:
You could do something like this, it's not the cleanest in the world(I
barely ever use sed anymore), but as something quick and dirty:
curl -k -H Accept: yaml https://puppet:8140/mgmt/resource_types/class |
more | grep name: | sed -e 's/^ *name: //;s/id.* //' | sort | uniq
It'll have some bad data you'll have to parse out(built-in classes like
notify, fail, etc.), but should work.
On Thursday, July 12, 2012 11:54:25 AM UTC-4, llo...@oreillyauto.com wrote:
Is there a way to get a list of all the classes available from the puppet
master?
I have 2 goals for this - one is documentation in a human readable form,
and the other is potentially importing that data into dashboard.
I did find some info on the rest API
(http://docs.puppetlabs.com/guides/rest_api.html#resource-types ) but I
can't make any sense of the output from it.
Thanks.
Lee
On Thursday, July 12, 2012 11:54:25 AM UTC-4, llo...@oreillyauto.com wrote:
Is there a way to get a list of all the classes available from the puppet
master?
I have 2 goals for this - one is documentation in a human readable form,
and the other is potentially importing that data into dashboard.
I did find some info on the rest API
(http://docs.puppetlabs.com/guides/rest_api.html#resource-types ) but I
can't make any sense of the output from it.
Thanks.
Lee
On Thursday, July 12, 2012 11:54:25 AM UTC-4, llo...@oreillyauto.com wrote:
Is there a way to get a list of all the classes available from the puppet
master?
I have 2 goals for this - one is documentation in a human readable form,
and the other is potentially importing that data into dashboard.
I did find some info on the rest API
(http://docs.puppetlabs.com/guides/rest_api.html#resource-types ) but I
can't make any sense of the output from it.
Thanks.
Lee
On Thursday, July 12, 2012 11:54:25 AM UTC-4, llo...@oreillyauto.com wrote:
Is there a way to get a list of all the classes available from the puppet
master?
I have 2 goals for this - one is documentation in a human readable form,
and the other is potentially importing that data into dashboard.
I did find some info on the rest API
(http://docs.puppetlabs.com/guides/rest_api.html#resource-types ) but I
can't make any sense of the output from it.
Thanks.
Lee
--
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/-/m4XmKKAYwtkJ.
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.
--
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.
--
Nigel Kersten | http://puppetlabs.com | @nigelkersten
Schedule Meetings at: http://tungle.me/nigelkersten
--
You received this message because you are subscribed to the Google Groups
Puppet Users
[Puppet Users] Anyway to get the $name or $title of the resource being called?
Hi - is there way to get the name of the resource being called when
its inside a class?
For example, if I have something defined as 'my_file' and I call it
like this inside of a class:
my_file {
/etc/bashrc:
;
}
Is there anyway to get the /etc/bashrc part in the definition logic
itself? It used to work (in like the .24 days maybe?) that I could
use $name, but I'm noticing in 2.7 that $name and $title now seem to
point to the class that the definition is called in, which breaks my
definition.
Thanks for your help!
--
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] Re: Anyway to get the $name or $title of the resource being called?
You may be doing something weird, because $name and $title inside a defined
type definition should definitely still refer to the instance's title. In
fact, I just tested it to be sure:
define my_file ($message) {
notify {$title:
message = $message, and the title is still $title,
}
}
class my_class {
my_file {'the title of the resource, not the class':
message = This is the message,
}
}
include my_class
...should get you:
notice: This is the message, and the title is still the title of the
resource, not the class
notice: /Stage[main]/My_class/My_file[the title of the resource, not the
class]/Notify[the title of the resource, not the class]/message: defined
'message' as 'This is the message, and the title is still the title of the
resource, not the class'
notice: Finished catalog run in 0.05 seconds
Show us what you're doing, maybe?
--
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/-/FHhRkovv9fIJ.
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] Crontab overwritten by Puppet
Hi, Thanks for the explanation. It's definitely not [2]. Only one user's crontab is being managed via Puppet, and it's not root. However, there are other jobs there which disappear when this happens. I really need a fix for this! If crontab -l fails, I would rather that Puppet just ignored the cron job configuration. This should be a paramter or something. Now I have to come in to the office every morning wondering if any of my cron jobs have disappeared.. Regards, On Thursday, 12 July 2012 23:30:15 UTC+2, Stefan Schulte wrote: On Mon, Jul 09, 2012 at 06:48:41AM -0700, Kmbu wrote: Hello folks.. I suddenly found the crontab on one of my puppet clients overwritten. It had many entries, including one created by Puppet. Suddenly during one run it was overwritten, keeping only the Puppet entry and removing everything else. Nothing changed between the previous runs and the one that re-created the crontab in terms of configuration. I'm running Puppet 2.7.6. Fri Jul 06 22:00:16 +0200 2012 Puppet (notice): Reopening log files Fri Jul 06 22:03:58 +0200 2012 Puppet (notice): Finished catalog run in 5.34 seconds Fri Jul 06 22:10:15 +0200 2012 Puppet (notice): Reopening log files Fri Jul 06 22:11:18 +0200 2012 Puppet (notice): Finished catalog run in 5.30 seconds Fri Jul 06 22:20:15 +0200 2012 Puppet (notice): Reopening log files Fri Jul 06 22:23:05 +0200 2012 Puppet (notice): Finished catalog run in 5.81 seconds Fri Jul 06 22:30:15 +0200 2012 Puppet (notice): Reopening log files Fri Jul 06 22:35:04 +0200 2012 Puppet (notice): Finished catalog run in 5.92 seconds Fri Jul 06 22:40:15 +0200 2012 Puppet (notice): Reopening log files Fri Jul 06 22:44:35 +0200 2012 /Stage[main]/Cre-base/Cron[puppet-run]/ensure (notice): created Fri Jul 06 22:44:39 +0200 2012 Puppet (notice): Finished catalog run in 5.54 seconds Why would one run suddenly do this? Regards, It looks like prefetching (executing �crontab -l root� to get current cronentries) failed in some way. As a result puppet's in-memory representation of the crontab is empty. When puppet now evaluates your Cron['puppet-run'] resource, it detects it to be out of sync (is absent, should be present), so the in-memory representation now contains only your 'puppet-run' cronjob. If the new crontab is written back to disk, you will loose every other cronentry. Normally I would expect an error message if prefetching failed: Could not prefetch cron provider but that doesn't seem to be the case here. On the other hand there is an outstanding bug about failures beeing silently ignored on solaris [1] So a failure when running �crontab -l root� (do you manage crontabs of other users as well? You may hit [2] in that case) would at least explain the log output but the interesting question now is: Can you think of a situation *why* the command failed? [1] http://projects.puppetlabs.com/issues/14283 [2] http://projects.puppetlabs.com/issues/5752 -- 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/-/9aCdhteKkbQJ. 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] Re: Announce: PuppetDB 0.9.2 Available
Thanks Moses! I shall get those installed when I get back to work and let you know if I have any issues. On 14 July 2012 04:50, Moses Mendoza mo...@puppetlabs.com wrote: All, New puppetdb 0.9.2 deb packages are available on apt.puppetlabs.com that should resolve these issues. The package version is 0.9.2-1puppetlabs2. As always, please let us know if you encounter issues. Thanks for your patience while we ironed this out. Cheers, Moses On Fri, Jul 13, 2012 at 7:39 AM, Deepak Giridharagopal dee...@puppetlabs.com wrote: On Fri, Jul 13, 2012 at 01:02:30AM -0700, Daniele Sluijters daniele.sluijt...@gmail.com wrote: Hey, We just got hit with the same problem on Debian Squeeze: java version 1.6.0_18 OpenJDK Runtime Environment (IcedTea6 1.8.13) (6b18-1.8.13-0+squeeze2) OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode) Indeed...as all the debian packages contain the same .jar, they'll all be similarly affected. Expect new packages momentarily...I'll notify the list once they're available! deepak -- 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. -- 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. -- 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.
