Re: [Puppet Users] inherited roles
http://blog.brattyredhead.com/blog/2011/11/19/puppet-for-chef-users-part-2-when-is-a-node-a/ may help. Perhaps the choice of words was wrong. The issue is how a node inherits multiple roles. I would assume from basic class syntax one could just do a::b::c etc to pull stuff in from subclassing and roll it up to the equivalent of chef roles. But it looks clumsy. Comments? On Jun 04, 2014, at 04:19 PM, Robin Bowes wrote: What do you mean by "inherited roles"? R. On 4 June 2014 23:02, Stuart Cracraft wrote: What's the best way to do inherited roles for servers? chef seems to excel at this whereas in Puppet it is wordy (at best). -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/8ab0a1d7-a53d-4217-8fc1-bfa280fecafb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups "Puppet Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/p6BqZHcczWU/unsubscribe. To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAJGKfwDm8xOehK%3Dsn5FB7OYHtKXpAFotOmy0k_1r9ahWBeChww%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5ffb8c13-bded-4eb8-8a94-e7ba3e615c50%40me.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] inherited roles
What's the best way to do inherited roles for servers? chef seems to excel at this whereas in Puppet it is wordy (at best). -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/8ab0a1d7-a53d-4217-8fc1-bfa280fecafb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] dashed by dashboard
Thanks Sam. > On Jan 7, 2014, at 1:58 AM, Sam Kottler wrote: > > > > >> On Mon, Jan 6, 2014 at 8:51 PM, Stuart Cracraft wrote: >> Okay, took care of that. Thanks. >> >> Now, when doing per page 170 in chapter 7 (chapter puppet consoles) in Pro >> Puppet >> by Krum et al, I have: >> >> ruby /usr/share/foreman-installer/generate_answers.rb > > We changed the installation process as part of a pretty large overhaul in the > Foreman installer that was released in 1.3. > > You can see the up-to-date installation guide here: > http://theforeman.org/manuals/1.3/quickstart_guide.html > >> >> but it does not have a file generate_answers.rb anywhere in the >> /usr/share/foreman-installer tree. >> >> Has anyone else encountered the above? >> >> >>> On Monday, January 6, 2014 10:46:57 AM UTC-8, Jose Luis Ledesma wrote: >> >>> You hace to enable both epel and optional repositories. >>> Regards, >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/d41f912e-2ed0-4efd-9354-a3f1d78c084c%40googlegroups.com. >> >> For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/XYf9pNGRVmY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CAPO4y0SGQBMxdGe5YwPnSy2ePcnhnqNsZx%2BvJWg3AUzutFCX2g%40mail.gmail.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/F3A65763-68A9-4F60-9DE5-1EC18CC6A68F%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] "the Foreman" in Pro Puppet, 2nd edition
Have subscribed and posted. On Monday, January 6, 2014 1:05:58 PM UTC-8, jmslagle wrote: > Maybe try the foreman mailing list? > > Thanks, > > Jason > > On 01/06/2014 04:02 PM, Stuart Cracraft wrote: > > Chapter 7 explains after installing Foreman that to start the installer: > > > > ruby /usr/share/foreman-installer/generate_answers.rb > > > > is necessary. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/4877ce8c-81d0-40ad-99bb-e353821c938b%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] "the Foreman" in Pro Puppet, 2nd edition
Chapter 7 explains after installing Foreman that to start the installer: ruby /usr/share/foreman-installer/generate_answers.rb is necessary. But the generate_answers.rb file isn't there. yum list | grep foreman | head -2 shows foreman-installer.noarch 1:1.3.1-1.el6 @foreman foreman-release.noarch 1.3.2-1.el6 @/foreman-release generate_answers.rb, in fact, exists no where on the system. Stuart -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6e970dad-1950-40e0-a160-d9d97000d063%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] dashed by dashboard
Okay, took care of that. Thanks. Now, when doing per page 170 in chapter 7 (chapter puppet consoles) in Pro Puppet by Krum et al, I have: ruby /usr/share/foreman-installer/generate_answers.rb but it does not have a file generate_answers.rb anywhere in the /usr/share/foreman-installer tree. Has anyone else encountered the above? On Monday, January 6, 2014 10:46:57 AM UTC-8, Jose Luis Ledesma wrote: > You hace to enable both epel and optional repositories. > > Regards, > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d41f912e-2ed0-4efd-9354-a3f1d78c084c%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] dashed by dashboard
So I have decided to give Foreman a try. Yet, the following occurred when I tried to install It. Ruby enthusiasts, any thoughts? The rest-client installed is 1.6.7 but the foreman installer install doesn't see it. # gem list | grep rest rest-client (1.6.7) # yum -y install foreman-installer Loaded plugins: product-id, rhnplugin, security, subscription-manager, : versionlock This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. This system is receiving updates from RHN Classic or RHN Satellite. Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package foreman-installer.noarch 1:1.3.1-1.el6 will be installed --> Processing Dependency: rubygem-foreman_api >= 0.1.4 for package: 1:foreman-installer-1.3.1-1.el6.noarch --> Processing Dependency: rubygem-kafo for package: 1:foreman-installer-1.3.1-1.el6.noarch --> Processing Dependency: rubygem-highline for package: 1:foreman-installer-1.3.1-1.el6.noarch --> Running transaction check ---> Package rubygem-foreman_api.noarch 0:0.1.9-1.el6 will be installed --> Processing Dependency: rubygem(rest-client) >= 1.6.1 for package: rubygem-foreman_api-0.1.9-1.el6.noarch --> Processing Dependency: rubygem(oauth) for package: rubygem-foreman_api-0.1.9-1.el6.noarch ---> Package rubygem-highline.noarch 0:1.4.0-2.el6 will be installed ---> Package rubygem-kafo.noarch 0:0.2.2-1.el6 will be installed --> Processing Dependency: rubygem(rdoc) for package: rubygem-kafo-0.2.2-1.el6.noarch --> Processing Dependency: rubygem(powerbar) for package: rubygem-kafo-0.2.2-1.el6.noarch --> Processing Dependency: rubygem(logging) for package: rubygem-kafo-0.2.2-1.el6.noarch --> Processing Dependency: rubygem(clamp) for package: rubygem-kafo-0.2.2-1.el6.noarch --> Running transaction check ---> Package rubygem-clamp.noarch 0:0.6.1-9.el6 will be installed ---> Package rubygem-foreman_api.noarch 0:0.1.9-1.el6 will be installed --> Processing Dependency: rubygem(rest-client) >= 1.6.1 for package: rubygem-foreman_api-0.1.9-1.el6.noarch ---> Package rubygem-logging.noarch 0:1.8.1-25.el6 will be installed --> Processing Dependency: rubygem(multi_json) >= 1.3.6 for package: rubygem-logging-1.8.1-25.el6.noarch --> Processing Dependency: rubygem(little-plugger) >= 1.1.3 for package: rubygem-logging-1.8.1-25.el6.noarch ---> Package rubygem-oauth.noarch 0:0.4.7-5.el6 will be installed ---> Package rubygem-powerbar.noarch 0:1.0.11-7.el6 will be installed --> Processing Dependency: rubygem(hashie) >= 1.1.0 for package: rubygem-powerbar-1.0.11-7.el6.noarch --> Processing Dependency: rubygem(ansi) >= 1.4.0 for package: rubygem-powerbar-1.0.11-7.el6.noarch ---> Package rubygem-rdoc.x86_64 0:3.12-12.el6 will be installed --> Running transaction check ---> Package rubygem-ansi.noarch 0:1.4.3-0.el6 will be installed ---> Package rubygem-foreman_api.noarch 0:0.1.9-1.el6 will be installed --> Processing Dependency: rubygem(rest-client) >= 1.6.1 for package: rubygem-foreman_api-0.1.9-1.el6.noarch ---> Package rubygem-hashie.noarch 0:2.0.5-0.el6 will be installed ---> Package rubygem-little-plugger.noarch 0:1.1.3-17.el6 will be installed ---> Package rubygem-multi_json.noarch 0:1.3.6-11.el6 will be installed --> Finished Dependency Resolution Error: Package: rubygem-foreman_api-0.1.9-1.el6.noarch (foreman) Requires: rubygem(rest-client) >= 1.6.1 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest # On Monday, December 30, 2013 3:22:07 PM UTC-8, Stuart Cracraft wrote: > I would take any reasonable console > as long as it has a very visual operation and is trivial to install. > > Dashboard definitely is not the latter > in my 'umble opinion. > > On Dec 30, 2013, at 3:17 PM, Felix Frank > wrote: > > >>> 3. What can you rule out as possible causes by now? > >> > >> ++ While I appreciate this approach, I don't think it will help. I > followed as much > >> ++ as possible with: > >> > >> http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html > >> > >> but it blows up at Preparing Schema. > > > > That sounds like useful info. I hope someone can help you from there - > > never played with dashboard myself. > > > >>> There may be other aspects that don't spring to my mind right now. I > >>> recommend reviewing the community guideline. > >> > >> ++ Be glad to. Where is it posted? > > > > http://docs.puppetlabs.com/community/community_guidelines.html > > > > Regards > > > > -- > >
Re: [Puppet Users] external node classifier with a back-end
Great Jason - I'll take a look (have done a ton of Python.) Happy new year. On Dec 31, 2013, at 4:06 AM, Jason Antman wrote: > Stuart, > > I know this took a while, but there were some bureaucratic hoops to be jumped > through first. > > Our Python/Django (Postgres-backed) ENC, or what exists of it so far, is now > at https://github.com/coxmediagroup/nodemeister > > Be advised this is horribly Alpha, doesn't really have any tests yet, and > relies on an internal python module. In other words, for the time being, it's > really there as code to look at only, I wouldn't expect you to get it > installed and running without some serious Python knowledge. > > -Jason > > On 12/06/2013 12:59 PM, Stuart Cracraft wrote: >> HI Jason, >> >> No I have no hesitations at all and yes, I would enjoy seeing your Postgres >> code >> and learning from it and can share back. >> >> So the thought here is to have all the configuration data, client data, node >> data, in >> a Postgres database (the one on the Puppet Master) and used downline by all >> the various >> Linux apps which need it, including Puppet. >> >> I take it (hopefully) this is not too unusual and bizarre in the world of >> Puppet. >> >> >> On Thursday, December 5, 2013 4:16:10 AM UTC-8, Jason Antman wrote: >> PuppetDB isn't an ENC. PuppetDB does, however, use Postgres (unless you use >> the embedded database, which you shouldn't). Puppet Dashboard is an ENC, but >> ironically, uses MySQL not Postgres. >> >> Stuart, >> >> Starting *another* ENC thread a day later isn't likely to get you many more >> responses than the two to your last question. I assumed, given your lack of >> response to my reply, that you're not terribly interested in sharing what >> you need an ENC to do... As I mentioned, I'm working on getting a >> Python/Django (Postgres-backed) ENC ready for release... if you want to see >> the current code, that could be arranged, though it's not really up to the >> "just run this puppet module and it installs the ENC" stage yet. >> >> -jantman >> >> On 12/04/2013 05:10 PM, Stuart Cracraft wrote: >>> Hi Ygor/Dan, >>> >>> Postgres has better DR. >>> >>> We like Postgres. >>> >>> Stuart >>> >>> On Wednesday, December 4, 2013 2:03:10 PM UTC-8, Ygor wrote: >>> Isn't that what PuppetDB is ? >>> >>> �Sometimes I think the surest sign that intelligent life exists elsewhere >>> in the universe is that none of it has tried to contact us.� >>> Bill Waterson (Calvin & Hobbes) >>> >>> From: "Stuart Cracraft" >>> To: puppet...@googlegroups.com >>> Sent: Wednesday, December 4, 2013 4:33:51 PM >>> Subject: [Puppet Users] external node classifier with a back-end >>> >>> >>> Hi everybody! >>> >>> Anyone have a back-ended external node classifier to a Postgres database >>> they could throw my way? >>> >>> Stuart >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Puppet Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to puppet-users...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/puppet-users/7781bed3-7e5a-46e2-8949-e00bfac0fbd0%40googlegroups.com. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Puppet Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to puppet-users...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/puppet-users/c642f1be-1121-4ab9-b56a-29b54809140f%40googlegroups.com. >>> For more options, visit https://groups.google.com/groups/opt_out. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/1909c6a8-9dc8-48bf-a397-f975a82749ac%40googlegroups.com.
Re: [Puppet Users] dashed by dashboard
I would take any reasonable console as long as it has a very visual operation and is trivial to install. Dashboard definitely is not the latter in my 'umble opinion. On Dec 30, 2013, at 3:17 PM, Felix Frank wrote: >>> 3. What can you rule out as possible causes by now? >> >> ++ While I appreciate this approach, I don't think it will help. I followed >> as much >> ++ as possible with: >> >> http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html >> >> but it blows up at Preparing Schema. > > That sounds like useful info. I hope someone can help you from there - > never played with dashboard myself. > >>> There may be other aspects that don't spring to my mind right now. I >>> recommend reviewing the community guideline. >> >> ++ Be glad to. Where is it posted? > > http://docs.puppetlabs.com/community/community_guidelines.html > > Regards > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/XYf9pNGRVmY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52C1FF22.8000308%40Alumni.TU-Berlin.de. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/FBEF4900-8ED9-47AF-B929-6E5D0F425053%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppet 3.3.2 with ruby 2.1.0
Cool. > On Dec 27, 2013, at 3:34 PM, Matthaus Owens wrote: > > Stuart, > The rpms will install puppet into the load path of the system ruby for > your platform. If you've installed a different ruby, then that new > ruby won't be able to load libraries from your system ruby load path. > For custom ruby use, the 3 main options are install from source, > install from a gem, or roll your own native package with the correct > pathing for the updated ruby's load path. > >> On Fri, Dec 27, 2013 at 3:12 PM, Stuart Cracraft >> wrote: >> Normal - via PL repo yum install. >> >> I haven't reinstalled Puppet master and Puppet client for each Ruby >> upgrade/downgrade. >> >> >>> On Friday, December 27, 2013 3:03:04 PM UTC-8, Matthaus Litteken wrote: >>> >>> Stuart, >>> How have you installed puppet? Have you installed it for each ruby >>> you're trying out? >>> >>> On Fri, Dec 27, 2013 at 2:59 PM, Stuart Cracraft >>> wrote: >>>> Tried ruby 2.0.0 but same: >>>> >>>> # /etc/init.d/puppetmaster start >>>> >>>> Starting puppetmaster: >>>> /usr/local/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in >>>> `require': cannot load such file -- pupp\ >>>> >>>> et/util/command_line (LoadError) >>>> >>>>from >>>> /usr/local/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in >>>> `require' >>>> >>>>from /usr/bin/puppet:3:in `' >>>> >>>> FAILED >>>> >>>> # >>>> >>>> >>>> As Robert Burns said: >>>> >>>> “O, wad some Power the giftie gie us >>>> To see oursels as others see us! >>>> It wad frae monie a blunder free us, >>>> An' foolish notion.” >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups >>>> "Puppet Users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an >>>> email to puppet-users...@googlegroups.com. >>>> To view this discussion on the web visit >>>> >>>> https://groups.google.com/d/msgid/puppet-users/ef45e361-9e64-4a87-b3f2-725162ab7e85%40googlegroups.com. >>>> >>>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >>> -- >>> Matthaus Owens >>> Release Manager, Puppet Labs >>> >>> Join us at PuppetConf 2014, September 23-24 in San Francisco >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/6e983dbb-fc50-441a-9770-dcbc44f74d17%40googlegroups.com. >> >> For more options, visit https://groups.google.com/groups/opt_out. > > > > -- > Matthaus Owens > Release Manager, Puppet Labs > > Join us at PuppetConf 2014, September 23-24 in San Francisco > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/nJQzPsnFqZ0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CACD%3DwAekqzVZJVk8VmhFq75KsrNs%2Bm2y%3DJ_8HaxV4Fg1Hy1hOQ%40mail.gmail.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/8D837DF1-A149-4871-8336-CCA4B5982D70%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppet 3.3.2 with ruby 2.1.0
Normal - via PL repo yum install. I haven't reinstalled Puppet master and Puppet client for each Ruby upgrade/downgrade. On Friday, December 27, 2013 3:03:04 PM UTC-8, Matthaus Litteken wrote: > Stuart, > How have you installed puppet? Have you installed it for each ruby > you're trying out? > > On Fri, Dec 27, 2013 at 2:59 PM, Stuart Cracraft > > > wrote: > > Tried ruby 2.0.0 but same: > > > > # /etc/init.d/puppetmaster start > > > > Starting puppetmaster: > > /usr/local/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in > > `require': cannot load such file -- pupp\ > > > > et/util/command_line (LoadError) > > > > from > > /usr/local/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in > > `require' > > > > from /usr/bin/puppet:3:in `' > > > > FAILED > > > > # > > > > > > As Robert Burns said: > > > > “O, wad some Power the giftie gie us > > To see oursels as others see us! > > It wad frae monie a blunder free us, > > An' foolish notion.” > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "Puppet Users" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to puppet-users...@googlegroups.com . > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/puppet-users/ef45e361-9e64-4a87-b3f2-725162ab7e85%40googlegroups.com. > > > > > > For more options, visit https://groups.google.com/groups/opt_out. > > > > -- > Matthaus Owens > Release Manager, Puppet Labs > > Join us at PuppetConf 2014, September 23-24 in San Francisco > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6e983dbb-fc50-441a-9770-dcbc44f74d17%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppet 3.3.2 with ruby 2.1.0
Tried ruby 2.0.0 but same: # /etc/init.d/puppetmaster start Starting puppetmaster: /usr/local/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require': cannot load such file -- pupp\ et/util/command_line (LoadError) from /usr/local/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require' from /usr/bin/puppet:3:in `' FAILED # As Robert Burns said: “O, wad some Power the giftie gie us To see oursels as others see us! It wad frae monie a blunder free us, An' foolish notion.” -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/ef45e361-9e64-4a87-b3f2-725162ab7e85%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] puppet 3.3.2 with ruby 2.1.0
Has anyone else seen this? ruby is 2.1.0 and puppet is 3.3.2. # /etc/init.d/puppetmaster start Starting puppetmaster: /usr/local/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- puppet/util/command_line (LoadError) from /usr/local/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/bin/puppet:3:in `' FAILED # I rolled back to the earlier version of ruby which handily works. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/af8cd42d-c0af-42f9-90db-14b60620279d%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: ruby visual debuggers/ide's for Linux
Hi everybody.
My quest for a Ruby debugger is over.
This does it:
http://stackoverflow.com/questions/1359333/how-do-i-use-ruby-debug-inside-emacs
The result is a 6-window split in emacs.
One is interactive to rdb.
One is the code with the program counter (i.e. the "arrow")
One is for variables.
One is for output.
One is for breakpoints.
And so forth.
My ~/.emacs looks like:
(add-to-list 'load-path "/export/home/scracraft/Lisp/")
(add-to-list 'load-path "/usr/local/share/emacs/site-lisp/")
(add-to-list 'auto-mode-alist '("*\\.rb\\'* " . ruby-mode))
(autoload 'ruby-mode "ruby-mode" "Major mode for editing Ruby code" t)
(add-hook 'ruby-mode-hook (lambda () (local-set-key "\r"
'newline-and-indent)))
(require 'inf-ruby)
(require 'rdebug)
Operation consists of:
open emacs
visit the .rb source file
do meta-x (i.e. escape-key) and then rdebug
window splits.
type help.
Commands include step, next, print, break, etc.
Stuart
P.S. I prefer Emacs to GUI editors other than Xcode.
OnTuesday, December 24, 2013 3:21:48 PM UTC-8, Stuart Cracraft wrote:
> Hi,
>
> Is there a plain-text visual debugger ide for Linux for Ruby anyone can
> mention?
>
> Stuart
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/ca079d49-61d2-46cd-b5c4-b24400ae7ebd%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] book
I'm about 20% through my first reading of Pro Puppet, 2nd Edition. It has great examples, is simply written and has clearly been well-edited. You would be well-advised to snap up a copy and commence in-depth. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/84270876-60DE-47FF-A48C-24DAC861C876%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] ruby visual debuggers/ide's for Linux
Bizarre. I downloaded pry-0.9.12.4.gem from rubygems.org and then: gem install pry It gave: ERROR: While executing gem ... (RangeError) integer 7516195309 Google has been unhelpful in ascertaining the path forward from the above error for the pry ide tryout If you are aware of the above, let loose in response. --Stuart On Thursday, December 26, 2013 1:59:14 AM UTC-8, Johan De Wit wrote: > Hi Stuart, > > Someone on the dev irc mentioned pry -> http://pryrepl.org/ > > I learned already a lot trying to write my first custom type and provider > > Grts > > Johan > > > > On 12/25/2013 12:21 AM, Stuart Cracraft wrote: > > Hi, > > > > Is there a plain-text visual debugger ide for Linux for Ruby anyone > > can mention? > > > > Stuart > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Puppet Users" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to puppet-users...@googlegroups.com . > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/puppet-users/b15a63ee-164e-4bb6-bbe4-829c67a91655%40googlegroups.com. > > > > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > Johan De Wit > > Open Source Consultant > > Red Hat Certified Engineer (805008667232363) > Puppet Certified Professional 2013 (PCP006) > _ > > Open-Future Phone +32 (0)2/255 70 70 > Zavelstraat 72 Fax +32 (0)2/255 70 71 > 3071 KORTENBERG Mobile+32 (0)474/42 40 73 > BELGIUM http://www.open-future.be > _ > > > Next Events: > Puppet Advanced Training | > http://www.open-future.be/puppet-advanced-training-7-till-9th-january > Puppet Fundamentals Training | > http://www.open-future.be/puppet-fundamentals-training-4-till-6th-february > Subscribe to our newsletter | http://eepurl.com/BUG8H > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/27aed7e3-2dfa-4a77-8025-f4982c47fefe%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: ruby visual debuggers/ide's for Linux
Juan, Where is this documented? Stuart On Thursday, December 26, 2013 3:35:23 AM UTC-8, JuanBrein wrote: > I would highly suggest you to use VIM+plugins > > Powerful as any other graphical IDE plus you can run it in any console > plus run on any OS plus free :-) > > On Tuesday, December 24, 2013 11:21:48 PM UTC, Stuart Cracraft wrote: >> >> Hi, >> >> Is there a plain-text visual debugger ide for Linux for Ruby anyone can >> mention? >> >> Stuart >> >> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5e1f1bf7-5077-4090-a030-dcab582039d3%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] dashed by dashboard
Hey Felix. Notes inlined with ++ On Dec 25, 2013, at 7:43 AM, Felix Frank wrote: > The meticulous gathering of error output, while commendable, is not > extremely helpful. Also, you should really put this on pastebin or > similar instead of sharing it on the list directly. ++ See below. > > The following would have been more interesting: > 1. What have you tried already by ways of debugging this? ++ None. I am not yet into Ruby on Rails enough. But it's going there. > 2. What have you found on the net? ++ Very little to speak of. > 3. What can you rule out as possible causes by now? ++ While I appreciate this approach, I don't think it will help. I followed as much ++ as possible with: http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html but it blows up at Preparing Schema. > > If the answer to all of these is "nothing", you jumped the gun by posting. > > There may be other aspects that don't spring to my mind right now. I > recommend reviewing the community guideline. ++ Be glad to. Where is it posted? > > On 12/24/2013 08:15 PM, Stuart Cracraft wrote: >> Thoughts? > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/XYf9pNGRVmY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52BAFD24.8010200%40Alumni.TU-Berlin.de. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/DCB0A25D-90A1-40F0-9040-82A38253E0B1%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] ruby visual debuggers/ide's for Linux
Jason: Google shows ruby-debug, inf-ruby emacs lisp packages and separately rdebug and irb but nothing really substantive for a non-GUI IDE which includes code in its running form usefully. Python and Perl have no such obvious limitations but perhaps it is just because I don't know yet... For Puppet itself there is of course: http://puppetlabs.com/blog/geppetto-a-puppet-ide I'd expect with the number of Ruby coders in Puppet Land (perhaps they are all over on puppet-developers...) someone would one-off that question pretty quick with the best practice... I had hoped this would have worked: http://www.emacswiki.org/emacs/ruby-debug like the perldb and pdb debuggers in Emacs work (wonderfully I might add), but alas ruby-debug didn't though I need to play around with it more. Stuart On Dec 25, 2013, at 8:41 AM, Jason Antman wrote: > Since you're asking about a Ruby IDE, not a Puppet IDE, perhaps this question > would be better asked of a Ruby list, or even better, a search engine... > > On 12/24/2013 06:21 PM, Stuart Cracraft wrote: >> Hi, >> >> Is there a plain-text visual debugger ide for Linux for Ruby anyone can >> mention? >> >> Stuart >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/b15a63ee-164e-4bb6-bbe4-829c67a91655%40googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/wwxeRu-cG_o/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52BB0AC6.2010802%40jasonantman.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/D7B5E22F-526F-4CC1-BFE1-965454CFC055%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] ruby visual debuggers/ide's for Linux
Hi, Is there a plain-text visual debugger ide for Linux for Ruby anyone can mention? Stuart -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b15a63ee-164e-4bb6-bbe4-829c67a91655%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Access denied for user 'dashboard'@'localhost' to database 'dashboard_production'
This is helpful. On Friday, July 6, 2012 2:08:53 PM UTC-7, Hai wrote: > followed the instruction for installing dashboard, and created user > > mysql -pmy_password -e "CREATE DATABASE dashboard CHARACTER SET > utf8;CREATE USER 'dashboard'@'localhost' IDENTIFIED BY 'my_password'; GRANT > ALL PRIVILEGES ON dashboard.* TO 'dashboard'@'localhost';" > > however, I keep getting access denied error: > > # rake RAILS_ENV=production db:migrate > (in /usr/share/puppet-dashboard) > rake aborted! > Access denied for user 'dashboard'@'localhost' to database > 'dashboard_production' > > (See full trace by running task with --trace) > > > please help! > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/11bf8b2a-e14f-4266-9148-8f6ee716a821%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Puppet Pro, 2nd edition - status directly from APress
Soft-cover/paperback arrived yesterday at my place. A cursory glance shows better coverage and more practical examples than I see in the previous edition. On Monday, December 23, 2013 1:15:44 AM UTC-8, Johan De Wit wrote: > I don't know what they are doing, but it will be an adventure to get a > hard-copy of the book :) > > Krum, Spencer "Pro Puppet (Professional Apress)" > Voraussichtliches Lieferdatum: 28. Juni 2014 - 30. Juni 2014 > > > > On 12/22/2013 02:59 AM, Stuart Cracraft wrote: > > hey did some ruby and cured those blues away. > > > >> On Dec 21, 2013, at 5:55 PM, Felix Frank > >> > > wrote: > >> > >> Uhm, what is now? > >> > >>> On 12/20/2013 11:35 PM, Stuart Cracraft wrote: > >>> It's all too money-centric and materialist. > >>> > >>> What a shame. > >> -- > >> You received this message because you are subscribed to a topic in the > Google Groups "Puppet Users" group. > >> To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/B-IogA5Tflc/unsubscribe. > >> To unsubscribe from this group and all its topics, send an email to > puppet-users...@googlegroups.com . > >> To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52B6469C.5090202%40Alumni.TU-Berlin.de. > > > >> For more options, visit https://groups.google.com/groups/opt_out. > > > -- > Johan De Wit > > Open Source Consultant > > Red Hat Certified Engineer (805008667232363) > Puppet Certified Professional 2013 (PCP006) > _ > > Open-Future Phone +32 (0)2/255 70 70 > Zavelstraat 72 Fax +32 (0)2/255 70 71 > 3071 KORTENBERG Mobile+32 (0)474/42 40 73 > BELGIUM http://www.open-future.be > _ > > > Next Events: > Puppet Advanced Training | > http://www.open-future.be/puppet-advanced-training-7-till-9th-january > Puppet Fundamentals Training | > http://www.open-future.be/puppet-fundamentals-training-4-till-6th-february > Subscribe to our newsletter | http://eepurl.com/BUG8H > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6b9f7fea-f117-43e1-bf2f-15b88f096ef8%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Puppet Pro, 2nd edition - status directly from APress
hey did some ruby and cured those blues away. > On Dec 21, 2013, at 5:55 PM, Felix Frank > wrote: > > Uhm, what is now? > >> On 12/20/2013 11:35 PM, Stuart Cracraft wrote: >> It's all too money-centric and materialist. >> >> What a shame. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/B-IogA5Tflc/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52B6469C.5090202%40Alumni.TU-Berlin.de. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1FDF0716-3AAC-4532-BCEA-E27EE3855D09%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: yamlyzer
Not just placing all trust in Puppet. That's the point of this tiny program
now named
yaml2csv.rb
If you revise/improve, you must post back your improved version.
And remember, by ensuring you noop your Puppet cloud and review it first
before actions,
you will keep the human in the loop before you un-noop and puppet agent -t
from a far,
rerun on all the YAML's, and see what you did in an actual human-readable
format.
Imagine that?
The fear, of course, is that some kind of whacko code gets into Puppet (I
know, open
source and all that), but, frankly, I can't take that chance so verifying
and proofing
mass-cloud changers is what I'm into.
Happy Hacking,
Stuart
#!/usr/bin/ruby
require 'puppet'
output = ""
# Are there args?
if defined?(ARGV)
# First argument needs to be the yaml file
filename = ARGV.first
# Has to be defined
if defined?(filename)
# Make a real version we can work on that is not frozen
fileName = filename.dup
# Get the report object
report = YAML.load_file(filename)
# Get the base name of the file to the far right
fileName = File.basename(filename)
# Formulate the timestamp
dateStamp = fileName.split /\./
# Loop through the logs and print appropriately
report.logs.each do |logg|
if logg.line or logg.line == 0 then
output = sprintf("%s, %s, %s, %s, (line %s), %s, %s, %s",
report.host,
dateStamp[0],
logg.time,
logg.file,
logg.line,
logg.source,
logg.level,
logg.message
)
searchResult = output.grep(/changed|noop/)
if searchResult.any? then
printf("%s\n",output)
end
else
output = sprintf("%s, %s, %s, %s, (line %s), %s, %s, %s",
report.host,
dateStamp[0],
logg.time,
logg.file,
"none",
logg.source,
logg.level,
logg.message
)
searchResult = output.grep(/changed|noop/)
if searchResult.any? then
printf("%s\n",output)
end
end
end
end
end
# Bless Ygor. Merry Christmas everybody
On Thursday, December 12, 2013 3:20:41 PM UTC-8, Stuart Cracraft wrote:
>
> Hi everybody,
>
> Is there a command-line program which parses:
>
> puppetmasters*:/var/lib/puppet/reports/*/*.yaml
>
> into simple a simple (though lengthy) report perhaps with
> column/field/etc. selection based on a straightforward method.
>
> Holler if you know of any. I know this was queried by me
> on this list recently and all sorts of stuff was posted. If
> I don't get it here, I'll need to go over to puppet-developers
> and ask there.
>
> Surely, someone has written something they're proud of and
> will share it forward.
>
> Stuart
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/e5d8be43-cd80-4b79-bf4c-4a52f2c408bb%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Puppet Pro, 2nd edition - status directly from APress
Must be good. Mine is set to arrive on 12/24 according to Amazon, so we'll see. It's all too money-centric and materialist. What a shame. On Friday, December 20, 2013 6:45:24 AM UTC-8, Ygor wrote: > I queried the publisher directly because depending what site you look at, > you get info that says anything from already published to "will ship on > March 31, 2014" (Books-A-Million). > > Thank you for contacting us. > This book is published on December 16, 2013 but due to a massive system > migration which is just about completed this still shows in Alpha. However > the updated content would be available in a week's time. > In case you have any further queries please let us know. > > I also find it very amusing that there are 5 sellers in the Amazon > Marketplace that say they will sell you a USED copy of THIS book for > between $95 and $115. Does that include a deed to the Brooklyn Bridge or > what ? > > “Sometimes I think the surest sign that intelligent life exists elsewhere > in the universe is that none of it has tried to contact us.” > Bill Waterson (Calvin & Hobbes) > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/ab29597c-74ae-4958-b239-36098db9753b%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] new puppet book revision
it's shipped. > On Dec 19, 2013, at 12:07 PM, Dan White wrote: > > In stock on December 22, 2013 > > ...says the Amazon web page :P > > “Sometimes I think the surest sign that intelligent life exists elsewhere in > the universe is that none of it has tried to contact us.” > Bill Waterson (Calvin & Hobbes) > > From: "William Van Hevelingen" > To: "[Puppet-Users]" , "Spencer Krum" > > Sent: Thursday, December 19, 2013 1:34:21 PM > Subject: Re: [Puppet Users] new puppet book revision > > Hi All, > > There was some problem between the publishing company and the printing > company that caused the book to be delayed for so long. Amazon now says the > book is "in stock" so I'm assuming the problem has been resolved. > > Let us know if you have any feedback good or bad. :) > > Thanks > William > > >> On Wed, Dec 18, 2013 at 9:58 AM, Stuart Cracraft >> wrote: >> Okay, let us know your assessment of the book as well after you get further >> into it. >> >> And your critiques. >> >> >>> On Wednesday, December 18, 2013 7:32:51 AM UTC-8, Benito Mourelo Caldeiro >>> wrote: >> >>> On mar, 2013-12-17 at 14:27 -0800, Stuart Cracraft wrote: >>> > It looks like Amazon/publishers/authors/etc. have revised the new >>> > puppet book date: >>> > >>> > >>> > http://www.amazon.com/Pro-Puppet-Spencer-Krum/dp/1430260408/ref=sr_1_3?ie=UTF8&qid=1387318030&sr=8-3&keywords=puppet+3 >>> > >>> > >>> > >>> > Fun! >>> >>> I bought the alfa book, and today I could download the PDF of the 2nd >>> edition from apress.com. >>> >>> Saudos, Benito. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/cc4ad721-f2a2-4647-9e10-14386b78b345%40googlegroups.com. >> >> For more options, visit https://groups.google.com/groups/opt_out. > > > > -- > Thanks, > William > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CAEXKxLxR%2Bt9du94WhNQLpDrG%3DLRxa4UvJjQnxniOe0Kc4aJK2w%40mail.gmail.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/vikNED3V2A4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/1726458901.124698.1387483671804.JavaMail.root%40sz0126a.westchester.pa.mail.comcast.net. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/41ECBF2F-EE27-4DBE-8AD9-94EAE560C740%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] get a *structured* version of the puppet agent output
It's too expensive given our small company. On Wednesday, December 18, 2013 11:25:31 AM UTC-8, Ygor wrote: > > Try this link: > > http://puppetlabs.com/services/consulting > > “Sometimes I think the surest sign that intelligent life exists elsewhere > in the universe is that none of it has tried to contact us.” > Bill Waterson (Calvin & Hobbes) > > ------ > *From: *"Stuart Cracraft" > > *To: *puppet...@googlegroups.com > *Sent: *Wednesday, December 18, 2013 1:01:42 PM > *Subject: *Re: [Puppet Users] get a *structured* version of the puppet > agent output > > > thanks. > > who is your contact? > > I am not getting the help I need. > > > On Dec 18, 2013, at 10:00 AM, Jason Slagle > > > > wrote: > > > > Hi Stuart, > > > > Puppet Labs has a large professional service department that you might > want to engage with these very specific requests. I'm sure they can give > you a hand with whatever you need done. > > > > Jason > > > >> On 12/18/2013 12:55 PM, Stuart Cracraft wrote: > >> What we are looking for is a Ruby program which takes the contents of > >> > >> /var/lib/puppet/reports/*/*.yaml > >> > >> and reports in detail on everything changed or proposed for change if in > >> noop mode > >> (file permissions, modes, user creates, etc.) > >> > >> Stuart > > > > -- > > You received this message because you are subscribed to a topic in the > Google Groups "Puppet Users" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/cHpZlKkPmr4/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > puppet-users...@googlegroups.com . > > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52B1E2AB.7060909%40tacorp.net > . > > For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users...@googlegroups.com . > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/36C6B660-92B8-4056-B82D-789C1B0AE7ED%40me.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/65902161-3831-4b46-8828-d80f2f3355f1%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] ruby
How would I convert this program to output exactly the same thing but only
for all the (noop) operations.
We keep puppet in noop mode to audit its actions before they are applied.
Thus it is necessary to ensure we understand exactly what all the nodes
noop operations would be if we listed the noop restriction for a normal
apply.
This program will report in a reasonable format for those non-noop
executed actions, but we want the reverse.
#!/usr/bin/ruby
require 'puppet'
if defined?(ARGV)
filename = ARGV.first
if defined?(filename)
report = YAML.load_file(filename)
print "Report for : "
puts report.host
print "Started : "
puts report.time
print "Log count: "
puts report.logs.size
print "Metrics count: "
puts report.metrics.size
print "Resource Status count: "
puts report.resource_statuses.size
print "Status: "
puts report.status
report.logs.each do |logg|
puts "LOG -"
if logg.file
print "File: "
puts logg.file
end
if logg.line
print "Line: "
puts logg.line
end
print "Level: "
puts logg.level
print "Message: "
puts logg.message
print "Source: "
puts logg.source
print "Tags: "
puts logg.tags.join(" ")
print "Time: "
puts logg.time
end
report.resource_statuses.keys.each do |kk|
if report.resource_statuses["#{kk}"].change_count > 0
puts "RESOURCE STATUS "
puts "#{kk} "
report.resource_statuses["#{kk}"].events.each do |line|
print "property: "
puts line.property
print "message: "
puts line.message
print "name: "
puts line.name
print "status: "
puts line.status
print "when: "
puts line.time
end
end
end
puts "-"
end
end
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/da81b10c-a6e1-4e20-9f98-ad43d3038688%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] get a *structured* version of the puppet agent output
thanks. who is your contact? I am not getting the help I need. > On Dec 18, 2013, at 10:00 AM, Jason Slagle wrote: > > Hi Stuart, > > Puppet Labs has a large professional service department that you might want > to engage with these very specific requests. I'm sure they can give you a > hand with whatever you need done. > > Jason > >> On 12/18/2013 12:55 PM, Stuart Cracraft wrote: >> What we are looking for is a Ruby program which takes the contents of >> >> /var/lib/puppet/reports/*/*.yaml >> >> and reports in detail on everything changed or proposed for change if in >> noop mode >> (file permissions, modes, user creates, etc.) >> >> Stuart > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/cHpZlKkPmr4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52B1E2AB.7060909%40tacorp.net. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/36C6B660-92B8-4056-B82D-789C1B0AE7ED%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] new puppet book revision
Okay, let us know your assessment of the book as well after you get further into it. And your critiques. On Wednesday, December 18, 2013 7:32:51 AM UTC-8, Benito Mourelo Caldeiro wrote: > On mar, 2013-12-17 at 14:27 -0800, Stuart Cracraft wrote: > > It looks like Amazon/publishers/authors/etc. have revised the new > > puppet book date: > > > > > > > http://www.amazon.com/Pro-Puppet-Spencer-Krum/dp/1430260408/ref=sr_1_3?ie=UTF8&qid=1387318030&sr=8-3&keywords=puppet+3 > > > > > > > Fun! > > I bought the alfa book, and today I could download the PDF of the 2nd > edition from apress.com. > > Saudos, Benito. > > > > > > > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/cc4ad721-f2a2-4647-9e10-14386b78b345%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] get a *structured* version of the puppet agent output
What we are looking for is a Ruby program which takes the contents of
/var/lib/puppet/reports/*/*.yaml
and reports in detail on everything changed or proposed for change if in
noop mode
(file permissions, modes, user creates, etc.)
Stuart
On Wednesday, November 27, 2013 7:12:48 AM UTC-8, David Portabella wrote:
> Thanks again! It is great to use the puppet report yaml files!
> here there is an example script that prints all resources statuses,
> then it filters them by taking only the services,
> then it filters them by taking only the services changed to running.
>
> test.ruby
> #!/usr/bin/ruby
>
> require 'puppet'
> filename = ARGV.first
> report = YAML.load_file(filename)
> rs = report.resource_statuses.values.sort_by{|r| r.resource}
>
> puts "PRINT ALL RESOURCES STATUSES."
> rs.each do |r|
> puts "#{r.change_count} #{r.events.map {|e| e.previous_value}}
> #{r.events.map {|e| e.desired_value}} #{r.resource}"
> end
>
> puts "PRINT ALL SERVICES."
> services = rs.select{|r| r.resource_type == 'Service'}
> services.each do |r|
> puts "#{r.change_count} #{r.events.map {|e| e.previous_value}}
> #{r.events.map {|e| e.desired_value}} #{r.resource}"
> end
>
> puts "PRINT ALL SERVICES CHANGED TO RUNNING."
> services_changed_to_running = rs.select{|r| r.resource_type == 'Service'
> && r.change_count > 0 && r.events.index { |e| e.desired_value == :running }
> != nil}
> services_changed_to_running.each do |r|
> puts "#{r.change_count} #{r.events.map {|e| e.previous_value}}
> #{r.events.map {|e| e.desired_value}} #{r.resource}"
> end
>
> example output:
> $ test.ruby /var/opt/lib/pe-puppet/reports/test/201311261645.yaml
> PRINT ALL RESOURCES STATUSES.
> 1 [:absent] [:directory] File[/var/app]
> 1 [:absent] [:file] File[/var/app/app.conf]
> 2 [0, "755"] [91, "775"] File[/var/log/tomcat6]
> 0 [] [] Filebucket[puppet]
> 1 [:absent] [:present] Group[release]
> 1 [:absent] [:present] Package[varnish]
> 0 [] [] Schedule[weekly]
> 1 [:stopped] [:running] Service[varnish]
> 0 [] [] Tidy[/etc/collectd.d/]
> 1 ["/sbin/nologin"] ["/bin/bash"] User[tomcat]
> ...
>
> PRINT ALL SERVICES.
> 1 [:stopped] [:running] Service[collectd]
> 1 [:stopped] [:running] Service[logstash-agent]
> 1 [:true] [:false] Service[logstash]
> 1 [:stopped] [:running] Service[nginx]
> 0 [] [] Service[rsyslog]
> 1 [:stopped] [:running] Service[statsd]
> 1 [:false] [:true] Service[supervisord]
> 1 [:stopped] [:running] Service[varnish]
>
> PRINT ALL SERVICES CHANGED TO RUNNING
> 1 [:stopped] [:running] Service[collectd]
> 1 [:stopped] [:running] Service[logstash-agent]
> 1 [:stopped] [:running] Service[nginx]
> 1 [:stopped] [:running] Service[statsd]
> 1 [:stopped] [:running] Service[varnish]
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/37dc9802-5090-4502-aac2-c3f6421236fa%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] new puppet book revision
Johan, Same in US as far as I see. Stuart > On Dec 18, 2013, at 12:22 AM, Johan De Wit wrote: > > In europe the delivery date from march 2014, moved to 24 december 2013. > > > > >> On 12/17/2013 11:27 PM, Stuart Cracraft wrote: >> It looks like Amazon/publishers/authors/etc. have revised the new puppet >> book date: >> >> http://www.amazon.com/Pro-Puppet-Spencer-Krum/dp/1430260408/ref=sr_1_3?ie=UTF8&qid=1387318030&sr=8-3&keywords=puppet+3 >> >> Fun! >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/875905a6-03ea-4da3-83fe-eda66f34384a%40googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > > > -- > Johan De Wit > > Open Source Consultant > > Red Hat Certified Engineer (805008667232363) > Puppet Certified Professional 2013 (PCP006) > _ > Open-Future Phone +32 (0)2/255 70 70 > Zavelstraat 72 Fax +32 (0)2/255 70 71 > 3071 KORTENBERG Mobile+32 (0)474/42 40 73 > BELGIUM http://www.open-future.be > _ > > Next Events: > Puppet Advanced Training | > http://www.open-future.be/puppet-advanced-training-7-till-9th-january > Puppet Fundamentals Training | > http://www.open-future.be/puppet-fundamentals-training-4-till-6th-february > Subscribe to our newsletter | http://eepurl.com/BUG8H -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/98203B35-8ED8-4B86-A3F9-01251B3DE84A%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: yamlyzer
Alas, it was all for naught. Anyone know about the uninitialized constant Yaml2csv error? [root@ca-sna-pm01 bin]# /usr/local/bin/yaml2csv.rb foobar.yml ./yaml2csv.rb:43: uninitialized constant Yaml2csv (NameError) from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:45:in `gem_original_require' from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:45:in `require' from /usr/local/bin/yaml2csv.rb:7 [root@ca-sna-pm01 bin]# Stuart On Tuesday, December 17, 2013 2:20:47 PM UTC-8, Stuart Cracraft wrote: > This is very interesting Jeff. > > I will play with it. > > Thanks! > > On Dec 17, 2013, at 2:04 PM, Jeff Bachtel > wrote: > > Have you tried a yaml to csv converter like > https://github.com/tokland/yaml2csv ? Note that it seems to require the > csv module syntax from ruby 1.9.3. > > Jeff > > On 12/16/2013 03:29 PM, Stuart Cracraft wrote: > > Is the back-end piece of Puppet Dashboard which implements the > CSV-capability > of the YAML interpretation available as a standalone? > > On Thursday, December 12, 2013 3:20:41 PM UTC-8, Stuart Cracraft wrote: > >> >> Hi everybody, >> >> Is there a command-line program which parses: >> >>puppetmasters*:/var/lib/puppet/reports/*/*.yaml >> >> into simple a simple (though lengthy) report perhaps with >> column/field/etc. selection based on a straightforward method. >> >> Holler if you know of any. I know this was queried by me >> on this list recently and all sorts of stuff was posted. If >> I don't get it here, I'll need to go over to puppet-developers >> and ask there. >> >> Surely, someone has written something they're proud of and >> will share it forward. >> >> Stuart >> >> -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/d333f68c-ad66-40bb-b969-9248114cd766%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/GxeE-URziu8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52B0CA5A.2010505%40bericotechnologies.com > . > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/fb001798-f3a4-41fd-8de3-1145ac304fa3%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppet-dashboard status report and bottleneck
All to nought. No change alas. Confirmation of version: [root@ca-sna-pm01 puppet-dashboard]# gem list | grep rubygem rubygems-update (1.8.25) [root@ca-sna-pm01 puppet-dashboard]# Retry of Schematization: [root@ca-sna-pm01 puppet-dashboard]# !1441 rake RAILS_ENV=production db:migrate rake aborted! undefined method `source_index' for Gem:Module (See full trace by running task with --trace) [root@ca-sna-pm01 puppet-dashboard]# The following would not be expected to work without the Schematization prerequisite above: [root@ca-sna-pm01 puppet-dashboard]# sudo -u puppet-dashboard ./script/server -e production ./script/../config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21:in `add_frozen_gem_path': undefined method `source_index\ ' for Gem:Module (NoMethodError) from ./script/../config/boot.rb:50:in `load_initializer' from ./script/../config/boot.rb:41:in `run' from ./script/../config/boot.rb:14:in `boot!' from ./script/../config/boot.rb:113 from ./script/server:2:in `require' from ./script/server:2 [root@ca-sna-pm01 puppet-dashboard]# Stuart On Tuesday, December 17, 2013 2:36:04 PM UTC-8, Matthaus Litteken wrote: > Stuart, googling the rake error you were getting resulted in the following > hit: > > > http://stackoverflow.com/questions/15349869/undefined-method-source-index-for-gemmodule-nomethoderror > > > Which indicated the version of rubygems is not compatible with the > rails application. > > On Mon, Dec 16, 2013 at 10:36 PM, Stuart Cracraft > > > wrote: > > Thanks Ramin. > > > > A good tip. > > > > Thank-you. > > > > On Dec 16, 2013, at 1:49 PM, Ramin K > > wrote: > > > > No Ruby Mysql bindings aka the mysql gem. > > > > > http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#installing-dependencies > > > > > Ramin > > > > On 12/16/2013 12:37 PM, Stuart Cracraft wrote: > > > > And the installed gems and ruby version. > > > > [root@ca-sna-pm01 puppet-dashboard]# gem list > > > > *** LOCAL GEMS *** > > > > actionmailer (3.2.13) > > > > actionpack (3.2.13) > > > > activemodel (3.2.13) > > > > activerecord (3.2.13) > > > > activeresource (3.2.13) > > > > activesupport (3.2.13) > > > > archive-tar-minitar (0.5.2) > > > > arel (3.0.2) > > > > builder (3.0.4) > > > > bundler (1.3.5) > > > > cgi_multipart_eof_fix (2.5.0) > > > > columnize (0.3.6) > > > > daemons (1.1.9) > > > > erubis (2.7.0) > > > > fastthread (1.0.7) > > > > gem_plugin (0.2.3) > > > > hike (1.2.2) > > > > i18n (0.6.1) > > > > journey (1.0.4) > > > > json (1.8.0) > > > > mail (2.5.4) > > > > mime-types (1.23) > > > > mongrel (1.1.5) > > > > multi_json (1.7.4) > > > > polyglot (0.3.3) > > > > rack (1.4.5) > > > > rack-cache (1.2) > > > > rack-ssl (1.3.3) > > > > rack-test (0.6.2) > > > > rails (3.2.13) > > > > railties (3.2.13) > > > > rake (10.0.4) > > > > rdoc (3.12.2) > > > > rgen (0.6.2) > > > > ruby-json (1.1.2) > > > > ruby-shadow (2.2.0) > > > > ruby_core_source (0.1.5) > > > > rubygems-update (2.0.3) > > > > shadow (1.1) > > > > sprockets (2.2.2) > > > > thor (0.18.1) > > > > tilt (1.4.1) > > > > treetop (1.4.12) > > > > tzinfo (0.3.37) > > > > [root@ca-sna-pm01 puppet-dashboard]# ruby --version > > > > ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] > > > > [root@ca-sna-pm01 puppet-dashboard]# > > > > > > > > On Monday, December 16, 2013 11:46:04 AM UTC-8, Stuart Cracraft wrote: > > > >I followed: > > > >http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html > ><http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html> > > > >and have reached the point after > > > > puppet dashboard install/configuration > > MySQL server and MySQL client installation/configuration/startup > > > >at > > > > Preparing Schema > > > >and now receive the error: > > > > rake RAILS_ENV=production db_migra
[Puppet Users] new puppet book revision
It looks like Amazon/publishers/authors/etc. have revised the new puppet book date: http://www.amazon.com/Pro-Puppet-Spencer-Krum/dp/1430260408/ref=sr_1_3?ie=UTF8&qid=1387318030&sr=8-3&keywords=puppet+3 Fun! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/875905a6-03ea-4da3-83fe-eda66f34384a%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: yamlyzer
This is very interesting Jeff. I will play with it. Thanks! > On Dec 17, 2013, at 2:04 PM, Jeff Bachtel > wrote: > > Have you tried a yaml to csv converter like > https://github.com/tokland/yaml2csv ? Note that it seems to require the csv > module syntax from ruby 1.9.3. > > Jeff > >> On 12/16/2013 03:29 PM, Stuart Cracraft wrote: >> Is the back-end piece of Puppet Dashboard which implements the CSV-capability >> of the YAML interpretation available as a standalone? >> >>> On Thursday, December 12, 2013 3:20:41 PM UTC-8, Stuart Cracraft wrote: >>> >>> Hi everybody, >>> >>> Is there a command-line program which parses: >>> >>> puppetmasters*:/var/lib/puppet/reports/*/*.yaml >>> >>> into simple a simple (though lengthy) report perhaps with >>> column/field/etc. selection based on a straightforward method. >>> >>> Holler if you know of any. I know this was queried by me >>> on this list recently and all sorts of stuff was posted. If >>> I don't get it here, I'll need to go over to puppet-developers >>> and ask there. >>> >>> Surely, someone has written something they're proud of and >>> will share it forward. >>> >>> Stuart >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/d333f68c-ad66-40bb-b969-9248114cd766%40googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/GxeE-URziu8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52B0CA5A.2010505%40bericotechnologies.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/C3562BA3-489B-41ED-807E-1D877B595B07%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: recursive descent
I don't have time to play hunt-the-wumpus.
> On Dec 17, 2013, at 1:54 PM, y...@comcast.net wrote:
>
> Have you tried experimenting ?
> Much of my Puppet savvy is from tinkering.
>
> Try some code. See what works and what does not work.
>
> "Sometimes I think the surest sign that intelligent life exists elsewhere in
> the universe is that none of it has tried to contact us."
> Bill Waterson (Calvin & Hobbes)
>
> - Original Message -
> From: smcracr...@gmail.com
> To: puppet-users@googlegroups.com
> Sent:Tue Dec 17 09:17:55 UTC 2013
> Subject: [Puppet Users] Re: recursive descent
>
> That is very, very disturbing.
>
>> On Wednesday, December 11, 2013 2:25:04 PM UTC-8, Stuart Cracraft wrote:
>>
>> I want to recursively descend infinitely through a directory tree in regards
>> to ensuring:
>>
>> (a) owner, group, permission
>> (b) existence of the full path, all the leaves, out to the final leaf, e.g.
>>/somedir/somesubdir/{file1,file2,file3,somesubdirtoo} and so forth
>>
>> This could be done trivially with an exec but is not pure-Puppet-ecosystem,
>> obviously.
>>
>> So my questions are, from a Puppet-puritan-perspective:
>>
>> is there a way to do (a)
>> is there a way to do (b)
>> is there a way to do (a)+(b)
>>
>> and last:
>>
>> is there a way to do (a)+(b) in a reasonable period of time for a shallow
>> tree of few leaves
>>
>> Yours in squirrelhood,
>>
>> Stuart
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/d24784e1-769c-4666-b077-a8856c898ff1%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
> --
> You received this message because you are subscribed to a topic in the Google
> Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/Hf6ReeSy2mE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/594141407.88154.1387317298820.JavaMail.root%40sz0126a.westchester.pa.mail.comcast.net.
> For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/5E36E5F6-7F2B-4E94-9767-E6E22B8D0156%40me.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: recursive descent
That is very, very disturbing.
On Wednesday, December 11, 2013 2:25:04 PM UTC-8, Stuart Cracraft wrote:
>
>
> I want to recursively descend infinitely through a directory tree in
> regards to ensuring:
>
> (a) owner, group, permission
> (b) existence of the full path, all the leaves, out to the final leaf,
> e.g.
>/somedir/somesubdir/{file1,file2,file3,somesubdirtoo} and so forth
>
> This could be done trivially with an exec but is not
> pure-Puppet-ecosystem, obviously.
>
> So my questions are, from a Puppet-puritan-perspective:
>
> is there a way to do (a)
> is there a way to do (b)
> is there a way to do (a)+(b)
>
> and last:
>
> is there a way to do (a)+(b) in a reasonable period of time for a
> shallow tree of few leaves
>
> Yours in squirrelhood,
>
> Stuart
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/d24784e1-769c-4666-b077-a8856c898ff1%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppet-dashboard status report and bottleneck
Thanks Ramin. A good tip. Thank-you. On Dec 16, 2013, at 1:49 PM, Ramin K wrote: > No Ruby Mysql bindings aka the mysql gem. > > http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#installing-dependencies > > Ramin > > On 12/16/2013 12:37 PM, Stuart Cracraft wrote: >> And the installed gems and ruby version. >> >> [root@ca-sna-pm01 puppet-dashboard]# gem list >> >> *** LOCAL GEMS *** >> >> actionmailer (3.2.13) >> >> actionpack (3.2.13) >> >> activemodel (3.2.13) >> >> activerecord (3.2.13) >> >> activeresource (3.2.13) >> >> activesupport (3.2.13) >> >> archive-tar-minitar (0.5.2) >> >> arel (3.0.2) >> >> builder (3.0.4) >> >> bundler (1.3.5) >> >> cgi_multipart_eof_fix (2.5.0) >> >> columnize (0.3.6) >> >> daemons (1.1.9) >> >> erubis (2.7.0) >> >> fastthread (1.0.7) >> >> gem_plugin (0.2.3) >> >> hike (1.2.2) >> >> i18n (0.6.1) >> >> journey (1.0.4) >> >> json (1.8.0) >> >> mail (2.5.4) >> >> mime-types (1.23) >> >> mongrel (1.1.5) >> >> multi_json (1.7.4) >> >> polyglot (0.3.3) >> >> rack (1.4.5) >> >> rack-cache (1.2) >> >> rack-ssl (1.3.3) >> >> rack-test (0.6.2) >> >> rails (3.2.13) >> >> railties (3.2.13) >> >> rake (10.0.4) >> >> rdoc (3.12.2) >> >> rgen (0.6.2) >> >> ruby-json (1.1.2) >> >> ruby-shadow (2.2.0) >> >> ruby_core_source (0.1.5) >> >> rubygems-update (2.0.3) >> >> shadow (1.1) >> >> sprockets (2.2.2) >> >> thor (0.18.1) >> >> tilt (1.4.1) >> >> treetop (1.4.12) >> >> tzinfo (0.3.37) >> >> [root@ca-sna-pm01 puppet-dashboard]# ruby --version >> >> ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] >> >> [root@ca-sna-pm01 puppet-dashboard]# >> >> >> >> On Monday, December 16, 2013 11:46:04 AM UTC-8, Stuart Cracraft wrote: >> >>I followed: >> >>http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html >><http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html> >> >>and have reached the point after >> >> puppet dashboard install/configuration >> MySQL server and MySQL client installation/configuration/startup >> >>at >> >> Preparing Schema >> >>and now receive the error: >> >> rake RAILS_ENV=production db_migrate >> rake aborted! >> undefined method `source_index' for Gem:Module >> >> See full trace by running task with --trace >> >>the above was run while connected to /usr/share/puppet-dashboard >>where there is a project Rakefile which the above uses. >> >>Any thoughts on the above and how to get past it? >> >>Thanks so much! >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send >> an email to puppet-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/ee0f339d-79f4-4622-bd51-3a2872d5aa48%40googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/jXit5cwjA9g/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52AF7562.4050209%40badapple.net. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7129942C-D5D2-4CAE-8456-B8AEBB27C76C%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] gem update error
gem update --system 1.8.25 --http-proxy=//ourproxy:ourport/ is giving me: ERROR: While executing gem ... (Net::HTTPServerException) 403 "Forbidden" I've confirmed at the proxy rubygems.org is open and also confirmed the port. Has something changed about updating with gem update? Or am I missing something entirely? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7bf90127-641b-46f1-9fef-f933533f517a%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: gem install error
You're the man Cory.
Works great.
Thanks.
Stuart
On Monday, December 16, 2013 2:37:23 PM UTC-8, Stuart Cracraft wrote:
>
> Anyone seen this?
>
> [root@ca-sna-pm01 puppet-dashboard]# !gem
>
> gem install mysql-2.9.1
>
> ERROR: While executing gem ... (Net::HTTPServerException)
>
> 403 "Forbidden"
>
> [root@ca-sna-pm01 puppet-dashboard]# gem install mysql
>
> Building native extensions. This could take a while...
>
> ERROR: Error installing mysql:
>
> ERROR: Failed to build gem native extension.
>
>
>
> /usr/bin/ruby extconf.rb
>
> checking for mysql_ssl_set()... no
>
> checking for rb_str_set_len()... no
>
> checking for rb_thread_start_timer()... no
>
> checking for mysql.h... no
>
> checking for mysql/mysql.h... no
>
> *** extconf.rb failed ***
>
> Could not create Makefile due to some reason, probably lack of
>
> necessary libraries and/or headers. Check the mkmf.log file for more
>
> details. You may need configuration options.
>
>
>
> Provided configuration options:
>
> --with-opt-dir
>
> --without-opt-dir
>
> --with-opt-include
>
> --without-opt-include=${opt-dir}/include
>
> --with-opt-lib
>
> --without-opt-lib=${opt-dir}/lib
>
> --with-make-prog
>
> --without-make-prog
>
> --srcdir=.
>
> --curdir
>
> --ruby=/usr/bin/ruby
>
> --with-mysql-config
>
> --without-mysql-config
>
>
>
>
>
> Gem files will remain installed in
> /usr/lib64/ruby/gems/1.8/gems/mysql-2.9.1 for inspection.
>
> Results logged to
> /usr/lib64/ruby/gems/1.8/gems/mysql-2.9.1/ext/mysql_api/gem_make.out
>
> [root@ca-sna-pm01 puppet-dashboard]#
>
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/55dc1a93-296c-4d97-8cde-4f6de0718e42%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] gem install error
Anyone seen this?
[root@ca-sna-pm01 puppet-dashboard]# !gem
gem install mysql-2.9.1
ERROR: While executing gem ... (Net::HTTPServerException)
403 "Forbidden"
[root@ca-sna-pm01 puppet-dashboard]# gem install mysql
Building native extensions. This could take a while...
ERROR: Error installing mysql:
ERROR: Failed to build gem native extension.
/usr/bin/ruby extconf.rb
checking for mysql_ssl_set()... no
checking for rb_str_set_len()... no
checking for rb_thread_start_timer()... no
checking for mysql.h... no
checking for mysql/mysql.h... no
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers. Check the mkmf.log file for more
details. You may need configuration options.
Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/usr/bin/ruby
--with-mysql-config
--without-mysql-config
Gem files will remain installed in
/usr/lib64/ruby/gems/1.8/gems/mysql-2.9.1 for inspection.
Results logged to
/usr/lib64/ruby/gems/1.8/gems/mysql-2.9.1/ext/mysql_api/gem_make.out
[root@ca-sna-pm01 puppet-dashboard]#
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/e2e8905f-8bb5-4067-a8bd-bf0b6012261b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: puppet-dashboard status report and bottleneck
And the installed gems and ruby version. [root@ca-sna-pm01 puppet-dashboard]# gem list *** LOCAL GEMS *** actionmailer (3.2.13) actionpack (3.2.13) activemodel (3.2.13) activerecord (3.2.13) activeresource (3.2.13) activesupport (3.2.13) archive-tar-minitar (0.5.2) arel (3.0.2) builder (3.0.4) bundler (1.3.5) cgi_multipart_eof_fix (2.5.0) columnize (0.3.6) daemons (1.1.9) erubis (2.7.0) fastthread (1.0.7) gem_plugin (0.2.3) hike (1.2.2) i18n (0.6.1) journey (1.0.4) json (1.8.0) mail (2.5.4) mime-types (1.23) mongrel (1.1.5) multi_json (1.7.4) polyglot (0.3.3) rack (1.4.5) rack-cache (1.2) rack-ssl (1.3.3) rack-test (0.6.2) rails (3.2.13) railties (3.2.13) rake (10.0.4) rdoc (3.12.2) rgen (0.6.2) ruby-json (1.1.2) ruby-shadow (2.2.0) ruby_core_source (0.1.5) rubygems-update (2.0.3) shadow (1.1) sprockets (2.2.2) thor (0.18.1) tilt (1.4.1) treetop (1.4.12) tzinfo (0.3.37) [root@ca-sna-pm01 puppet-dashboard]# ruby --version ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] [root@ca-sna-pm01 puppet-dashboard]# On Monday, December 16, 2013 11:46:04 AM UTC-8, Stuart Cracraft wrote: > I followed: > > http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html > > and have reached the point after > > puppet dashboard install/configuration > MySQL server and MySQL client installation/configuration/startup > > at > > Preparing Schema > > and now receive the error: > > rake RAILS_ENV=production db_migrate > rake aborted! > undefined method `source_index' for Gem:Module > > See full trace by running task with --trace > > the above was run while connected to /usr/share/puppet-dashboard > where there is a project Rakefile which the above uses. > > Any thoughts on the above and how to get past it? > > Thanks so much! > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/ee0f339d-79f4-4622-bd51-3a2872d5aa48%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: puppet-dashboard status report and bottleneck
Here is the rake trace: [root@ca-sna-pm01 puppet-dashboard]# !1154 rake RAILS_ENV=production db:migrate rake aborted! undefined method `source_index' for Gem:Module (See full trace by running task with --trace) [root@ca-sna-pm01 puppet-dashboard]# !! --trace rake RAILS_ENV=production db:migrate --trace rake aborted! undefined method `source_index' for Gem:Module /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21:in `add_frozen_gem_path' /usr/share/puppet-dashboard/config/boot.rb:50:in `load_initializer' /usr/share/puppet-dashboard/config/boot.rb:41:in `run' /usr/share/puppet-dashboard/config/boot.rb:14:in `boot!' /usr/share/puppet-dashboard/config/boot.rb:113 /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:45:in `gem_original_require' /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:45:in `require' /usr/share/puppet-dashboard/Rakefile:4 /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/rake_module.rb:25:in `load' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/rake_module.rb:25:in `load_rakefile' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:589:in `raw_load_rakefile' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:89:in `load_rakefile' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:160:in `standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:88:in `load_rakefile' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:72:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:160:in `standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:70:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/bin/rake:33 /usr/bin/rake:19:in `load' /usr/bin/rake:19 [root@ca-sna-pm01 puppet-dashboard]# On Monday, December 16, 2013 11:46:04 AM UTC-8, Stuart Cracraft wrote: > I followed: > > http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html > > and have reached the point after > > puppet dashboard install/configuration > MySQL server and MySQL client installation/configuration/startup > > at > > Preparing Schema > > and now receive the error: > > rake RAILS_ENV=production db_migrate > rake aborted! > undefined method `source_index' for Gem:Module > > See full trace by running task with --trace > > the above was run while connected to /usr/share/puppet-dashboard > where there is a project Rakefile which the above uses. > > Any thoughts on the above and how to get past it? > > Thanks so much! > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e11a0efb-9b55-40a9-9739-512ec27ad004%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: yamlyzer
Is the back-end piece of Puppet Dashboard which implements the CSV-capability of the YAML interpretation available as a standalone? On Thursday, December 12, 2013 3:20:41 PM UTC-8, Stuart Cracraft wrote: > > Hi everybody, > > Is there a command-line program which parses: > > puppetmasters*:/var/lib/puppet/reports/*/*.yaml > > into simple a simple (though lengthy) report perhaps with > column/field/etc. selection based on a straightforward method. > > Holler if you know of any. I know this was queried by me > on this list recently and all sorts of stuff was posted. If > I don't get it here, I'll need to go over to puppet-developers > and ask there. > > Surely, someone has written something they're proud of and > will share it forward. > > Stuart > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d333f68c-ad66-40bb-b969-9248114cd766%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: puppet-dashboard status report and bottleneck
Here's a little more detail if we try to start the production dashboard server prior to having the previous rake runnable error-free... [root@ca-sna-pm01 puppet-dashboard]# sudo -u puppet-dashboard ./script/server -e production ./script/../config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21:in `add_frozen_gem_path': undefined method `source_index\ ' for Gem:Module (NoMethodError) from ./script/../config/boot.rb:50:in `load_initializer' from ./script/../config/boot.rb:41:in `run' from ./script/../config/boot.rb:14:in `boot!' from ./script/../config/boot.rb:113 from ./script/server:2:in `require' from ./script/server:2 [root@ca-sna-pm01 puppet-dashboard]# Stuart On Monday, December 16, 2013 11:46:04 AM UTC-8, Stuart Cracraft wrote: > I followed: > > http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html > > and have reached the point after > > puppet dashboard install/configuration > MySQL server and MySQL client installation/configuration/startup > > at > > Preparing Schema > > and now receive the error: > > rake RAILS_ENV=production db_migrate > rake aborted! > undefined method `source_index' for Gem:Module > > See full trace by running task with --trace > > the above was run while connected to /usr/share/puppet-dashboard > where there is a project Rakefile which the above uses. > > Any thoughts on the above and how to get past it? > > Thanks so much! > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/15105f07-dcc0-4e89-a8af-b5f375497528%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] puppet-dashboard status report and bottleneck
I followed: http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html and have reached the point after puppet dashboard install/configuration MySQL server and MySQL client installation/configuration/startup at Preparing Schema and now receive the error: rake RAILS_ENV=production db_migrate rake aborted! undefined method `source_index' for Gem:Module See full trace by running task with --trace the above was run while connected to /usr/share/puppet-dashboard where there is a project Rakefile which the above uses. Any thoughts on the above and how to get past it? Thanks so much! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/af1c62c9-dd67-4818-a069-68690fa7308e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Puppet Dashboard: how to connect?
Okay, now puppet-dashboard is installed on my Puppet Master and I am ready and ripe. How do I access the dashboard? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/0f180467-733b-4c4d-8dca-c919823cba27%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Puppet Dashboard: how to connect?
Hey Ygor and Jeff. I went to www.redhat.com, logged in, accessed the customer portal, went into the packages and then searched for and found my rubygem-rake-0.8.7-2.1.el6.noarch.rpm, then rpm -i'd then did a yum install puppet-dashboard and voila!!! YEAH Stuart On Friday, December 13, 2013 2:00:20 PM UTC-8, Jeff Bachtel wrote: > yum-config-manager --enable rhel-6-server-optional-rpms > > Has worked on some RHEL machines, for me. It depends on how your system is > subscribed whether that will work or whether you'll need to use another > command. > > Jeff > > On 12/13/2013 04:50 PM, Stuart Cracraft wrote: > > Great! > > What is the .repo file format for the optional channel for rhel 6. > > I would like to install puppet-dashboard using the above as soon as > possible. > > Stuart > > On Friday, December 13, 2013 11:27:41 AM UTC-8, Matthaus Litteken wrote: > >> Stuart, >> rubygem(rake) is provided by the rubygem-rake package, available in >> centos 6 or in the optional channel for rhel 6. >> >> On Fri, Dec 13, 2013 at 9:44 AM, Stuart Cracraft >> wrote: >> > yum install puppet-dashboard gives a requirement for dependency >> resolution: >> > >> > Error: Package: puppet-dashboard-1.2.23-1.el6.noarch (puppetlabs) >> > Requires: rubygem(rake) >> > >> > My question is, how to install rubygem so that puppet-dashboard >> installs? >> > >> > Stuart >> > >> > >> > On Friday, December 13, 2013 9:25:55 AM UTC-8, Stuart Cracraft wrote: >> >> >> >> Hi - I run puppet 3.3.2 currently of Open Source Puppet. >> >> >> >> I am looking for anyone who has run Puppet Dashboard. >> >> >> >> How do I connect to the dashboard? >> >> >> >> Stuart >> >> >> > -- >> > You received this message because you are subscribed to the Google >> Groups >> > "Puppet Users" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an >> > email to puppet-users...@googlegroups.com. >> > To view this discussion on the web visit >> > >> https://groups.google.com/d/msgid/puppet-users/b501fed0-1922-4445-b577-1d212c70970d%40googlegroups.com. >> >> >> > >> > For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> -- >> Matthaus Owens >> Release Manager, Puppet Labs >> >> Join us at PuppetConf 2014, September 23-24 in San Francisco >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users...@googlegroups.com . > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/650e0e91-ff04-4eb8-aa2e-31aa2fe98add%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5a0a26bb-b786-43d8-9257-5cc2956f14fa%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Puppet Dashboard: how to connect?
Great! What is the .repo file format for the optional channel for rhel 6. I would like to install puppet-dashboard using the above as soon as possible. Stuart On Friday, December 13, 2013 11:27:41 AM UTC-8, Matthaus Litteken wrote: > Stuart, > rubygem(rake) is provided by the rubygem-rake package, available in > centos 6 or in the optional channel for rhel 6. > > On Fri, Dec 13, 2013 at 9:44 AM, Stuart Cracraft > > > wrote: > > yum install puppet-dashboard gives a requirement for dependency > resolution: > > > > Error: Package: puppet-dashboard-1.2.23-1.el6.noarch (puppetlabs) > > Requires: rubygem(rake) > > > > My question is, how to install rubygem so that puppet-dashboard > installs? > > > > Stuart > > > > > > On Friday, December 13, 2013 9:25:55 AM UTC-8, Stuart Cracraft wrote: > >> > >> Hi - I run puppet 3.3.2 currently of Open Source Puppet. > >> > >> I am looking for anyone who has run Puppet Dashboard. > >> > >> How do I connect to the dashboard? > >> > >> Stuart > >> > > -- > > You received this message because you are subscribed to the Google > Groups > > "Puppet Users" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to puppet-users...@googlegroups.com . > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/puppet-users/b501fed0-1922-4445-b577-1d212c70970d%40googlegroups.com. > > > > > > For more options, visit https://groups.google.com/groups/opt_out. > > > > -- > Matthaus Owens > Release Manager, Puppet Labs > > Join us at PuppetConf 2014, September 23-24 in San Francisco > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/650e0e91-ff04-4eb8-aa2e-31aa2fe98add%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] get a *structured* version of the puppet agent output
You ask a great question.
Also, it would be great if we could get the actual Unix cli equivalent of
what Puppet is proposing to do.
On Friday, December 13, 2013 5:30:19 AM UTC-8, David Portabella wrote:
> Given this puppet manifest (test.pp):
> $dir = '/tmp'
> file {'myfile':
> path => "$dir/myfile.txt",
> content => 'hello'
> }
>
> puppet produces this report:
> [...]
> File[myfile]: !ruby/object:Puppet::Resource::Status
> resource: File[myfile]
> file: /Users/david/test.pp
> line: 4
> evaluation_time: 0.001354
> change_count: 1
> out_of_sync_count: 1
> tags:
> - file
> - myfile
> - class
> time: 2013-12-13 11:44:59.092716 +01:00
> events:
> - !ruby/object:Puppet::Transaction::Event
> audited: false
> property: ensure
> previous_value: !ruby/sym absent
> desired_value: !ruby/sym file
> historical_value:
> message: "defined content as
> '{md5}5d41402abc4b2a76b9719d911017c592'"
> name: !ruby/sym file_created
> status: success
> time: 2013-12-13 11:44:59.093067 +01:00
> out_of_sync: true
> changed: true
> resource_type: File
> title: myfile
> skipped: false
> failed: false
> containment_path:
> - Stage[main]
> - ""
> - File[myfile]
> [...]
>
> so, the report tells that it has created File[myfile],
> but it does not contain the path of the file /tmp/myfile.txt.
>
> that's a pity, because it means that I cannot get a list of all the files
> updated by puppet.
>
> is there a way to get the final path of all File resources created by
> puppet?
> (not "$dir/myfile.txt", but "/tmp/myfile.txt")
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/8b0f3577-d5e4-4a55-abdb-cc15cbe949de%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Puppet Dashboard: how to connect?
yum install puppet-dashboard gives a requirement for dependency resolution: Error: Package: puppet-dashboard-1.2.23-1.el6.noarch (puppetlabs) Requires: rubygem(rake) My question is, how to install rubygem so that puppet-dashboard installs? Stuart On Friday, December 13, 2013 9:25:55 AM UTC-8, Stuart Cracraft wrote: > Hi - I run puppet 3.3.2 currently of Open Source Puppet. > > I am looking for anyone who has run Puppet Dashboard. > > How do I connect to the dashboard? > > Stuart > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b501fed0-1922-4445-b577-1d212c70970d%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppet Dashboard: how to connect?
Hi - I run puppet 3.3.2 currently of Open Source Puppet. I am looking for anyone who has run Puppet Dashboard. How do I connect to the dashboard? Stuart -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/270ebc67-7884-401b-8503-7823c6aa1624%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] yamlyzer
John, I will look into this tomorrow. It sounds like the solution. Thanks very much. Stuart On Dec 12, 2013, at 8:32 PM, John Warburton wrote: > On 13 December 2013 15:07, Stuart Cracraft wrote: > Our Security Group would like to have complete visibility to logs in simple > formats they can parse > and understand and socialize it to the C-suite with. Also, it can be used to > analyze Puppet's proposed > operations in noop mode prior to an eventual turnup in full 7x24x365 mode for > selected subsets of > our cloud. > > Are you using puppet dashboard? You can get the same information in CSV > format from http://localhost:3000/nodes.csv. It has the same information as > the yaml reports, but in "easier" (familiar) to manage CSV format, and always > up to date when you suck it from the dashboard. Here's a line of an out of > sync resource: > > hostname,pending,736,34,0,702,File,/etc/sudoers,0.483092,/modules/sudoers/manifests/init.pp,22,2013-12-11 > 23:16 UTC,0,1,false,false > > You don't get everything (like a diff on the file),and it is a good idea to > omit in sync resources (!~ /,0,0,[a-z]*,false/) > > And why hasn't someone written exactly what you want? Because probably no-one > has the exact requirements of your organisation. So, at some stage you're > going to have to do some custom work. > > Or even better, engage puppet labs to do what you want, and ensure it gets > rolled back into the product for the community. That's where the totting up > the # resources and states and the CSV dump of the dashboard came from... > > John > > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/GxeE-URziu8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CAAJLFxVfb8A9TwsEng%2B2VK_eFarRa7a%3DkRMMGYu9hu%2BTvmBUGw%40mail.gmail.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/F1E84CBD-E759-46DD-8C6A-2051409C81A9%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] yamlyzer
Thank-you Dan. Stuart On Dec 12, 2013, at 8:42 PM, Dan White wrote: > Extending the script depends on what yaml files you plan to parse and what > serialized objects are contained therein. > > http://www.skorks.com/2010/04/serializing-and-deserializing-objects-with-ruby/ > > On Dec 12, 2013, at 11:07 PM, Stuart Cracraft wrote: > >> Great. >> >> Okay - anyone additionally, how would you extend Dan's script to dump the >> entirety of a Puppet YAML >> to a plain text report. >> >> I know, I know. It sounds boring, painful even but the rationale is to know >> exactly >> what the YAML says even though it is voluminous. >> >> The reason? >> >> Our Security Group would like to have complete visibility to logs in simple >> formats they can parse >> and understand and socialize it to the C-suite with. Also, it can be used to >> analyze Puppet's proposed >> operations in noop mode prior to an eventual turnup in full 7x24x365 mode >> for selected subsets of >> our cloud. >> >> On Dec 12, 2013, at 8:03 PM, Dan White wrote: >> >>> No. >>> I whipped that sample up in about 10 minutes. >>> >>> It provides a starting point for you to develop what you want. > > “Sometimes I think the surest sign that intelligent life exists elsewhere in > the universe is that none of it has tried to contact us.” > Bill Waterson (Calvin & Hobbes) > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/GxeE-URziu8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/A5133F3F-CAAC-45D3-BD84-8D8CA5A174DF%40comcast.net. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/F9F7B799-A94D-437C-9069-CFA1B65C8035%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] yamlyzer
Great. Okay - anyone additionally, how would you extend Dan's script to dump the entirety of a Puppet YAML to a plain text report. I know, I know. It sounds boring, painful even but the rationale is to know exactly what the YAML says even though it is voluminous. The reason? Our Security Group would like to have complete visibility to logs in simple formats they can parse and understand and socialize it to the C-suite with. Also, it can be used to analyze Puppet's proposed operations in noop mode prior to an eventual turnup in full 7x24x365 mode for selected subsets of our cloud. On Dec 12, 2013, at 8:03 PM, Dan White wrote: > No. > I whipped that sample up in about 10 minutes. > > It provides a starting point for you to develop what you want. > > On Dec 12, 2013, at 8:09 PM, Stuart Cracraft wrote: > >> Do you personally use something >> more comprehensive with all fields >> enabled? > > “Sometimes I think the surest sign that intelligent life exists elsewhere in > the universe is that none of it has tried to contact us.” > Bill Waterson (Calvin & Hobbes) > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/GxeE-URziu8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/0D6FF77B-2D05-43A4-B42B-C1268179D221%40comcast.net. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/3EFA4955-6A98-4246-BC72-E805A9830713%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] yamlyzer
Do you personally use something
more comprehensive with all fields
enabled?
> On Dec 12, 2013, at 4:59 PM, Dan White wrote:
>
>
>> On Dec 12, 2013, at 6:20 PM, Stuart Cracraft wrote:
>>
>>
>> Hi everybody,
>>
>> Is there a command-line program which parses:
>>
>> puppetmasters*:/var/lib/puppet/reports/*/*.yaml
>>
>> into simple a simple (though lengthy) report perhaps with
>> column/field/etc. selection based on a straightforward method.
>>
>> Holler if you know of any. I know this was queried by me
>> on this list recently and all sorts of stuff was posted. If
>> I don't get it here, I'll need to go over to puppet-developers
>> and ask there.
>>
>> Surely, someone has written something they're proud of and
>> will share it forward.
>>
>> Stuart
>
>
>> On Nov 26, 2013, at 2:27 PM, Dan White wrote:
>>
>> Reference: http://docs.puppetlabs.com/puppet/3/reference/format_report.html
>>
>> Start with this:
>>
>> #!/usr/bin/ruby
>>
>> require 'puppet'
>> if defined?(ARGV)
>> filename = ARGV.first
>>
>> if defined?(filename)
>> report = YAML.load_file(filename)
>> print "Report for : "
>> puts report.host
>> print "Started : "
>> puts report.time
>> print "Log count: "
>> puts report.logs.size
>> print "Metrics count: "
>> puts report.metrics.size
>> print "Resource Status count: "
>> puts report.resource_statuses.size
>> print "Status: "
>> puts report.status
>>
>> report.logs.each do |logg|
>> puts "LOG -"
>> if logg.file
>> print "File: "
>> puts logg.file
>> end
>>
>> if logg.line
>> print "Line: "
>> puts logg.line
>> end
>>
>> print "Level: "
>> puts logg.level
>> print "Message: "
>> puts logg.message
>> print "Source: "
>> puts logg.source
>> print "Tags: "
>> puts logg.tags.join(" ")
>> print "Time: "
>> puts logg.time
>> end
>>
>> report.resource_statuses.keys.each do |kk|
>> if report.resource_statuses["#{kk}"].change_count > 0
>> puts "RESOURCE STATUS "
>> puts "#{kk} "
>> report.resource_statuses["#{kk}"].events.each do |line|
>> print "property: "
>> puts line.property
>> print "message: "
>> puts line.message
>> print "name: "
>> puts line.name
>> print "status: "
>> puts line.status
>> print "when: "
>> puts line.time
>> end
>> end
>> end
>> puts "-"
>> end
>> end
>> --
>>
>> Good luck.
>>
>>
>> “Sometimes I think the surest sign that intelligent life exists elsewhere in
>> the universe is that none of it has tried to contact us.”
>> Bill Waterson (Calvin & Hobbes)
>>
>> - Original Message -
>> From: "Stuart Cracraft"
>> To: puppet-users@googlegroups.com
>> Sent: Tuesday, November 26, 2013 2:10:53 PM
>> Subject: Re: [Puppet Users] get a *structured* version of the puppet agent
>> output
>>
>> Who will share a report generator for the yaml reports generated by puppet
>> so that we do not have to reinvent wheel after wheel after wheel!!
>>
>>> On Nov 26, 2013, at 11:08 AM, "R.I.Pienaar" wrote:
>>>
>>>
>>>
>>> - Original Message -
>>>> From: "Stuart Cracraft"
>>>> To: puppet-users@googlegroups.com
>>>> Sent: Tues
Re: [Puppet Users] parsing puppet YAML
Where did this go? On Friday, May 21, 2010 9:44:33 PM UTC-7, Luke Baker wrote: > Hey there, > > > > I’ve playing with parsing some of the yaml data that puppet creates. Has > anyone had luck doing this with python or the like? It seems that in every > yaml file, there is a comment at the top of the file like this.. > > > > --- !ruby/object:Puppet::Node > > > > Which doesn’t make may yaml parsers happy.. where am I going wrong? > > > > --Luke Baker > > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet...@googlegroups.com > . > To unsubscribe from this group, send email to > puppet-users...@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 unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e23870ec-93e1-4057-a616-977da955ec73%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] yamlyzer
Hi everybody, Is there a command-line program which parses: puppetmasters*:/var/lib/puppet/reports/*/*.yaml into simple a simple (though lengthy) report perhaps with column/field/etc. selection based on a straightforward method. Holler if you know of any. I know this was queried by me on this list recently and all sorts of stuff was posted. If I don't get it here, I'll need to go over to puppet-developers and ask there. Surely, someone has written something they're proud of and will share it forward. Stuart -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/97ac73f0-f64a-4a09-b571-da222b3bdb1a%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] examples of puppet yaml output
Well, obviously, but... What if you do not have a lot of data or want more yaml's for testing against? Will anyone give me all their yaml's? I'd like thousands and thousands to test against. On Thursday, December 12, 2013 1:05:50 PM UTC-8, Ygor wrote: > /var/lib/puppet/reports > on a puppet master. > > "Sometimes I think the surest sign that intelligent life exists elsewhere > in the universe is that none of it has tried to contact us." > Bill Waterson (Calvin & Hobbes) > > - Original Message - > From: smcra...@gmail.com > To: puppet...@googlegroups.com > Sent:Thu Dec 12 08:47:42 UTC 2013 > Subject: [Puppet Users] examples of puppet yaml output > > Greetings Puppeteers!!! > > Where can I get a very large set of puppet yaml output? > > I want to run my new yamlyzer program over it as a test. > > I don't want to run it against anything small. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users...@googlegroups.com . > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/5d812e4d-2dea-4a3a-ade6-2d61b36f3dc0%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/61101e77-2249-42cd-8127-3d0cb9b583a2%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] examples of puppet yaml output
Greetings Puppeteers!!! Where can I get a very large set of puppet yaml output? I want to run my new yamlyzer program over it as a test. I don't want to run it against anything small. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5d812e4d-2dea-4a3a-ade6-2d61b36f3dc0%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] recursive descent
Sure does John. Thanks for your interest! Do we know when the Puppet 3.0 book is coming out? It's showing as a very, very long delay at Amazon... On Thursday, December 12, 2013 7:17:17 AM UTC-8, jcbollinger wrote: > > > On Wednesday, December 11, 2013 4:38:02 PM UTC-6, Stuart Cracraft wrote: >> >> >> http://christian.hofstaedtler.name/blog/2008/11/puppet-managing-directories-recursively.html >> >> > Yes. Do you still have a question here, or does that blog post answer the > question sufficiently for you? > > > John > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/2bf056f0-cf06-482f-becc-86465530bf3e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] recursive descent
http://christian.hofstaedtler.name/blog/2008/11/puppet-managing-directories-recursively.html
On Wednesday, December 11, 2013 2:36:05 PM UTC-8, Stuart Cracraft wrote:
>
> The tree has to already exist.
>
> One would think having the ability
> to instantiate a tree from a seedling would be useful.
>
> Sent from my iPhone
>
> On Dec 11, 2013, at 2:25 PM, Stuart Cracraft wrote:
>
>
> I want to recursively descend infinitely through a directory tree in
> regards to ensuring:
>
> (a) owner, group, permission
> (b) existence of the full path, all the leaves, out to the final leaf,
> e.g.
>/somedir/somesubdir/{file1,file2,file3,somesubdirtoo} and so forth
>
> This could be done trivially with an exec but is not
> pure-Puppet-ecosystem, obviously.
>
> So my questions are, from a Puppet-puritan-perspective:
>
> is there a way to do (a)
> is there a way to do (b)
> is there a way to do (a)+(b)
>
> and last:
>
> is there a way to do (a)+(b) in a reasonable period of time for a
> shallow tree of few leaves
>
> Yours in squirrelhood,
>
> Stuart
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/Hf6ReeSy2mE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/b9c95f80-9ae3-439b-a451-17327291524d%40googlegroups.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/a0f42acd-6ac7-497f-a218-24c91cc397a5%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] recursive descent
The tree has to already exist.
One would think having the ability
to instantiate a tree from a seedling would be useful.
Sent from my iPhone
> On Dec 11, 2013, at 2:25 PM, Stuart Cracraft wrote:
>
>
> I want to recursively descend infinitely through a directory tree in regards
> to ensuring:
>
> (a) owner, group, permission
> (b) existence of the full path, all the leaves, out to the final leaf, e.g.
>/somedir/somesubdir/{file1,file2,file3,somesubdirtoo} and so forth
>
> This could be done trivially with an exec but is not pure-Puppet-ecosystem,
> obviously.
>
> So my questions are, from a Puppet-puritan-perspective:
>
> is there a way to do (a)
> is there a way to do (b)
> is there a way to do (a)+(b)
>
> and last:
>
> is there a way to do (a)+(b) in a reasonable period of time for a shallow
> tree of few leaves
>
> Yours in squirrelhood,
>
> Stuart
>
>
> --
> You received this message because you are subscribed to a topic in the Google
> Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/Hf6ReeSy2mE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/b9c95f80-9ae3-439b-a451-17327291524d%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/5B231871-F82E-4DBA-9562-1F93B486A6DA%40me.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] recursive descent
I want to recursively descend infinitely through a directory tree in
regards to ensuring:
(a) owner, group, permission
(b) existence of the full path, all the leaves, out to the final leaf,
e.g.
/somedir/somesubdir/{file1,file2,file3,somesubdirtoo} and so forth
This could be done trivially with an exec but is not pure-Puppet-ecosystem,
obviously.
So my questions are, from a Puppet-puritan-perspective:
is there a way to do (a)
is there a way to do (b)
is there a way to do (a)+(b)
and last:
is there a way to do (a)+(b) in a reasonable period of time for a shallow
tree of few leaves
Yours in squirrelhood,
Stuart
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/b9c95f80-9ae3-439b-a451-17327291524d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: audit
Very cool.
We have extremely heavy audit requirements so this will help.
I like the idea that it is noted and extractable and recordable and
countable for analytics.
Now, if I could only get Puppet to tell me exactly what CLI it would
propose running...
As I don't want to have to massage YAML files into reasonability...
On Tuesday, December 10, 2013 7:11:10 AM UTC-8, jcbollinger wrote:
>
>
> On Monday, December 9, 2013 5:12:42 PM UTC-6, Stuart Cracraft wrote:
>>
>>
>> Assume the following question is in regards to Puppet 3.3.2.
>>
>> So my question is in relation to audit.
>>
>> file { '/some/random/path/through/the/tree/to/a/file':
>> owner => 'luke',
>> group => 'rebelalliance',
>> mode => '0444',
>> audit => all
>> }
>>
>> And more specifically: will the named file be force-owned to luke with the
>> group and mode and then any alterations to that initial setting be
>> reported (i.e.
>> audited)?
>>
>> How does audit differ from leaving out audit?
>>
>> Does audit centralize its checksum activity on the server rather than the
>> client?
>>
>>
>
> Here are the docs:
> http://docs.puppetlabs.com/references/3.stable/metaparameter.html#audit
>
> Basically, auditing some or all properties of a resource causes puppet to
> log changes to those properties from run to run, and causes them to be
> included in the output of "puppet inspect". Nothing more or less. In
> particular, marking a resource property for audit has no effect on Puppet's
> evaluation of whether its host resource must be synced, nor on whether
> Puppet synchronizes that particular property.
>
> Thus in your example, Puppet will enforce that
> /some/random/path/through/the/tree/to/a/file is owned by user 'luke', with
> group 'rebelalliance' and mode 0444 when it applies that resource (unless
> running in noop mode). I'm slightly unclear on this, but I think it will
> audit not just those properties, but ALL File properties it knows about:
>
>- ensure
>- content
>- ctime
>- group
>- mode
>- mtime
>- owner
>- selrange
>- selrole
>- seltype
>- seluser
>- target
>
> Other attributes of File do not represent "properties" of the target
> resource, rather they are "parameters" affecting the process of syncing the
> resource. Even 'source' is a parameter -- it affects how the 'content'
> property is synced.
>
> Leaving out 'audit' will omit logging changes to those properties, and
> will omit enrolling them for inclusion in Puppet inspection reports (though
> it's conceivable that some will be enrolled by other means).
>
> I'm not sure I understand the question about checksum activity. Puppet
> must compute checksums of both the actual and expected file content.
> Checksums of the actual content are computed on the target machine, where
> that content actually is. Checksums of the expected content are computed
> on the master, the source of that content. When the 'source' parameter is
> used, computing the checksum on the master allows the content transfer to
> be avoided when it is unneeded. When static content is specified directly
> via the 'content' property, the master has an opportunity to cache the
> checksum, though I'm uncertain how aggressive or effective it is at
> performing such caching.
>
> If this is of interest to you then I would suggest experimenting with
> 'audit' to get a feel for it.
>
>
> John
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/96950e41-e4a9-49ad-9f75-2a1107c4976c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] audit
Assume the following question is in regards to Puppet 3.3.2.
So my question is in relation to audit.
file { '/some/random/path/through/the/tree/to/a/file':
owner => 'luke',
group => 'rebelalliance',
mode => '0444',
audit => all
}
And more specifically: will the named file be force-owned to luke with the
group and mode and then any alterations to that initial setting be reported
(i.e.
audited)?
How does audit differ from leaving out audit?
Does audit centralize its checksum activity on the server rather than the
client?
Stuart
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/51beda0d-6d3b-4253-8f3a-0976c478e3b6%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] crontab
Hi, I'd like to establish and maintain a standard crontab using Puppet. What is best practice? I don't want to invent too much. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/190380fd-fcd3-4a6e-9410-ed83b5d50388%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] mail
Anybody know if Puppet has a way to email directly from a manifest in the DSL? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d390e71b-b668-49c0-b74b-fc72ca8e527a%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] external node classifier with a back-end
HI Jason, No I have no hesitations at all and yes, I would enjoy seeing your Postgres code and learning from it and can share back. So the thought here is to have all the configuration data, client data, node data, in a Postgres database (the one on the Puppet Master) and used downline by all the various Linux apps which need it, including Puppet. I take it (hopefully) this is not too unusual and bizarre in the world of Puppet. On Thursday, December 5, 2013 4:16:10 AM UTC-8, Jason Antman wrote: > PuppetDB isn't an ENC. PuppetDB does, however, use Postgres (unless you > use the embedded database, which you shouldn't). Puppet Dashboard is an > ENC, but ironically, uses MySQL not Postgres. > > Stuart, > > Starting *another* ENC thread a day later isn't likely to get you many > more responses than the two to your last question. I assumed, given your > lack of response to my reply, that you're not terribly interested in > sharing what you need an ENC to do... As I mentioned, I'm working on > getting a Python/Django (Postgres-backed) ENC ready for release... if you > want to see the current code, that could be arranged, though it's not > really up to the "just run this puppet module and it installs the ENC" > stage yet. > > -jantman > > On 12/04/2013 05:10 PM, Stuart Cracraft wrote: > > Hi Ygor/Dan, > > Postgres has better DR. > > We like Postgres. > > Stuart > > On Wednesday, December 4, 2013 2:03:10 PM UTC-8, Ygor wrote: > >> Isn't that what PuppetDB is ? >> >> �Sometimes I think the surest sign that intelligent life exists >> elsewhere in the universe is that none of it has tried to contact us.� >> Bill Waterson (Calvin & Hobbes) >> >> -- >> *From: *"Stuart Cracraft" >> *To: *puppet...@googlegroups.com >> *Sent: *Wednesday, December 4, 2013 4:33:51 PM >> *Subject: *[Puppet Users] external node classifier with a back-end >> >> >> Hi everybody! >> >> Anyone have a back-ended external node classifier to a Postgres database >> they could throw my way? >> >> Stuart >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/7781bed3-7e5a-46e2-8949-e00bfac0fbd0%40googlegroups.com >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users...@googlegroups.com . > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/c642f1be-1121-4ab9-b56a-29b54809140f%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1909c6a8-9dc8-48bf-a397-f975a82749ac%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Automatic installation of puppet agent from puppet master
You can have autosign enabled on the puppet master but I don't recommend it. You want to have control over the initial deployments since by just blanket auto-signing, you may run into some major issues with too much change too suddenly. As you gain experience, you can bulk sign in chunks once your initial signs and time have been producing no impact. Consider a Puppet run on a node a potentially dangerous production-affecting outage-causing operation like any other. On Friday, December 6, 2013 5:12:23 AM UTC-8, Deep wrote: > HI, > > Is there a way in puppet to automatically install agents in unmanaged node > from the puppet dashboard or backend? > > eg: I have a network with a mixture of linux and windows servers.I can > include the puppet agent in the OS installation phase or do it manually in > servers. > But, is there an option in the puppet to install agents on these nodes by > mentioning Hostname/IP address or other related parameters? > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d61d11e2-9dd4-40cd-a32e-593f30094d48%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] external node classifier with a back-end
And if you do not want to store secretive (complete) company data in PuppetDB but instead an alternative securable database, what then pray tell? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/E22CF187-0DDD-409E-9784-4F9995215551%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] puppetmaster and nodes upgraded
3.2.1 to 3.3.2 puppetmaster(s) and associated node(s) passed test(s) one case was a straight "yum upgrade" with puppet labs yum service (the puppet master). the others from a private/local rpm repo I maintain. Didn't see anything weird. Did have to install libselinux-ruby though... Stuart -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/535190a4-4966-4afb-8cfb-56412a078661%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] external node classifier with a back-end
Hi Ygor/Dan, Postgres has better DR. We like Postgres. Stuart On Wednesday, December 4, 2013 2:03:10 PM UTC-8, Ygor wrote: > Isn't that what PuppetDB is ? > > “Sometimes I think the surest sign that intelligent life exists elsewhere > in the universe is that none of it has tried to contact us.” > Bill Waterson (Calvin & Hobbes) > > ------ > *From: *"Stuart Cracraft" > > *To: *puppet...@googlegroups.com > *Sent: *Wednesday, December 4, 2013 4:33:51 PM > *Subject: *[Puppet Users] external node classifier with a back-end > > > Hi everybody! > > Anyone have a back-ended external node classifier to a Postgres database > they could throw my way? > > Stuart > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users...@googlegroups.com . > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/7781bed3-7e5a-46e2-8949-e00bfac0fbd0%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/c642f1be-1121-4ab9-b56a-29b54809140f%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] external node classifier with a back-end
Hi everybody! Anyone have a back-ended external node classifier to a Postgres database they could throw my way? Stuart -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7781bed3-7e5a-46e2-8949-e00bfac0fbd0%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: external node classifiers
Chapter 5 at page 119 in the Pro Puppet book of 2011 by Turnbull/McCune has good explanation and scripts, in Shell, Perl, Ruby. On Tuesday, December 3, 2013 3:50:47 PM UTC-8, Stuart Cracraft wrote: > Hi, > > I'd like to use ENC:: > > http://docs.puppetlabs.com/guides/external_nodes.html > > to keep hardwired customizations away from our classes and other files as > much as possible > particularly for the node name, but potentially as esoteric as a machine > configuration, file > permission, service name, etc - to keep the classes as flexible and > general as possible. > > My questions: > > + have you done the above? > + what were your learnings > + do you have sample puppet_node_classifier's you can share? > + how to use the definitions from ENC via the pm's puppet.conf's linkage > to the ENC > >[main] >: >node_terminus = exec >external_nodes = /usr/local/bin/puppet_node_classifier >: > > My current question is how do you use the ENC definitions within the > classes? > > Is this adequately described in-depth in the yet-to-be-published Puppet > book? > > Stuart > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/30c4f26c-9fec-4419-a9ab-674c0cefc7aa%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] external node classifiers
Hi, I'd like to use ENC:: http://docs.puppetlabs.com/guides/external_nodes.html to keep hardwired customizations away from our classes and other files as much as possible particularly for the node name, but potentially as esoteric as a machine configuration, file permission, service name, etc - to keep the classes as flexible and general as possible. My questions: + have you done the above? + what were your learnings + do you have sample puppet_node_classifier's you can share? + how to use the definitions from ENC via the pm's puppet.conf's linkage to the ENC [main] : node_terminus = exec external_nodes = /usr/local/bin/puppet_node_classifier : My current question is how do you use the ENC definitions within the classes? Is this adequately described in-depth in the yet-to-be-published Puppet book? Stuart -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7b5670b1-8ca6-4d63-bb38-3d0e5f5bfae6%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Announce: Puppet 3.4.0-rc1 Available
Does the community have any scripts to share which do in-place backups of the PM and a new version upgrade? > On Dec 3, 2013, at 2:45 PM, Matthaus Owens wrote: > > Stuart, > This page has plenty of information about upgrading: > http://docs.puppetlabs.com/guides/upgrading.html > >> On Tue, Dec 3, 2013 at 2:33 PM, Stuart Cracraft wrote: >> What is the upgrade methodology / documentation to take a 3.2.1 system to >> 3.4.0-rc1 ? >> >>> On Tuesday, December 3, 2013 11:42:51 AM UTC-8, Melissa Stone wrote: >>> >>> **Release candidate** >>> >>> Puppet 3.4.0-rc1 >>> -- >>> Release Candidate: Puppet 3.4.0 is not yet released. >>> >>> RC1: December 3, 2013. >>> >>> At least one more RC is planned. Known issues with RC 1: >>> >>> An existing but empty csr_attributes.yaml file will cause puppet agent to >>> fail with Error: Could not request certificate: undefined method 'delete' >>> for false:FalseClass when attempting to generate a keypair. To avoid this >>> problem, make sure the csr_attributes.yamlfile is either properly filled or >>> completely absent. >>> >>> 3.4.0 is a backward-compatible feature and fix release in the Puppet 3 >>> series. The main foci of this release are: >>> >>> New certificate autosigning behavior, to help quickly and securely add new >>> nodes in elastic environments >>> Fixes for some high-profile bugs and annoyances, including the "anchor >>> pattern" issue and broken Rdoc on Ruby 1.9+ >>> Windows improvements, especially for file resources >>> Trusted node data in the compiler >>> >>> >>> >>> Puppet 3.4.0-rc1 Downloads >>> -- >>> Source: https://downloads.puppetlabs.com/puppet/puppet-3.4.0-rc1.tar.gz >>> >>> Available in native package format in the pre-release repositories at: >>> http://yum.puppetlabs.com and http://apt.puppetlabs.com >>> >>> For information on how to enable the Puppet Labs pre-release repos, see: >>> >>> http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos >>> >>> Gems are available via rubygems at >>> https://rubygems.org/downloads/puppet-3.4.0-rc1.gem >>> or by using `gem install --pre puppet` >>> >>> Mac packages are available at >>> https://downloads.puppetlabs.com/mac/puppet-3.4.0-rc1.dmg >>> >>> Windows packages are available at >>> https://downloads.puppetlabs.com/windows/puppet-3.4.0-rc1.msi >>> >>> Please report feedback via the Puppet Labs Redmine site, using an >>> affected puppet version of 3.4.0-rc1: >>> https://projects.puppetlabs.com/projects/puppet/ >>> >>> >>> >>> Puppet 3.4.0-rc1 release notes >>> --- >>> New contain Function Removes Need for “Anchor Pattern” >>> >>> Puppet now includes a contain function to allow classes to contain other >>> classes. It functions similarly to the include function, with the added >>> effect of creating a containment relationship. For more information, see: >>> >>> The containment page of the language reference, for background information >>> about class containment issues and an explanation of the anchor pattern >>> The classes page of the language reference, for complete information on >>> declaring classes withcontain, include, and more. >>> >>> (Issue 8040) >>> >>> Policy-Based Certificate Autosigning >>> >>> Puppet can now use site-specific logic to decide which certificate signing >>> requests (CSRs) should be autosigned. This feature is based on custom >>> executables, which can examine each CSR as it arrives and use any >>> decision-making criteria you choose. >>> >>> Prior to 3.4, Puppet would accept a whitelist of nodes whose requests >>> should be autosigned. This wasn’t very flexible, and didn’t allow things >>> like using a preshared key to verify the legitimacy of a node. This is now >>> very possible, and works especially well when combined with the next new >>> feature (custom CSR attributes). >>> >>> For details, see: >>> >>> The “Policy-Based Autosigning” section of the autosigning reference page >>> Documentation for the autosign setting >
Re: [Puppet Users] noop = true and what for test?
Thanks for sharing this. > On Dec 3, 2013, at 2:52 PM, John Warburton wrote: > >> On 4 December 2013 04:54, Stuart Cracraft wrote: >> The rationale for the above methodology is: hosting firm doing database >> hosting in a (very) >> highly secured environment seeking to ensure extreme care of the "crown >> jewels." >> >> We realize it is not an exciting use case. > > We run a similarly unexciting puppet environment with strict change control, > so no "standard" updating every 30 minutes. We run a puppet noop twice a day > from cron (not daemon mode), which reports back to the puppet dashboard. > > We can then extract the dashboard information as a CSV and report on non > conformity, especial some modules like "security". See some examples in a > previous post > > John > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/0vhLrU0Rl_0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CAAJLFxWoQBGrc83%3Dd_jxDkhcTReenKSN_ovWg63gREQmiVaBew%40mail.gmail.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/E6456648-F5BC-4164-9118-3F1A7AF40C49%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: cli-driven list-file-based ad-hoc runs
We'll be using a simple parallel tool which has sequential as an option to
do
puppet agent -t --noop on the remote nodes. This means we won't need
MCollective
and the ports it requires open. We're a hosted environment with very heavy
security
and "deny all" is the default.
On Monday, December 2, 2013 11:23:52 AM UTC-8, Stuart Cracraft wrote:
> Currently, I have
>
> /etc/puppet/puppet.conf
>
> on my nodes with
>
> [main]
> :
> noop = true
>
> [agent]
> :
>
> And puppet is running as:
>
> /usr/bin/ruby /usr/bin/puppet agent --verbose
>
> On the Puppet Master:
>
> /etc/puppet/manifests/nodes.pp
>
> node 'basenode' {
> include baseclass
> }
> :
> node 'somepattern' inherits basenode {
> class { 'abc::def':
> randomvariables => "random values"
> }
> }
>
> However, I am finding it inconvenient for running all assigned classes
> on the node
> or some subset of the nodes or some subset of classes and nodes, etc., and
> only
> when I specify they should be run (not 7x24x365, etc.):
>
> What I want is, from the master do something like
>
> some-magical-puppet-command some-list-file
>
> which based on the one-host-per-line some-list-file simply makes it happen
> on the remote nodes, running the classes then and only then with the normal
> YAML logging and /var/log/messages.
>
> Anyone implemented non-GUI, CLI-based run-from-listfile within Open Source
> Puppet?
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/f5470b32-e511-4c77-9f22-cc555d053d42%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: external facts cause puppet apply to take inordinately longer to run
Scary. On Wednesday, November 27, 2013 9:17:44 PM UTC-8, Glenn Poston wrote: > > My external fact script takes 5s to run. > > With external fact... > puppet takes 2.5m to run > facter takes 33s to run > > Without external fact... > puppet takes 27s to run > facter takes 0.68s > > Bottom line... there's no significant change in facter runtime when > parsing the external fact, but the puppet runtime quadruples. > > From watching the logs in real time I can see that the extra time is taken > before puppet outputs its first response line (compilation time). Also > note that the compilation time that puppet reports is ~2s even though (when > watching the output realtime) it takes 2 minutes for that line to return > when puppet is parsing the external fact script. > > Note: This script generates 36 custom facts > > Should I submit a bug for this? > > #Time of external fact script > [root@fisheye-10-0-2-15 manifests]# time > /etc/facter/facts.d/service_discovery.sh > environment=test > ... > service_discovery_script=ran > > real 0m5.478s > user 0m0.053s > sys 0m0.111s > > # Time of puppet run with external fact > [root@fisheye-10-0-2-15 manifests]# time FACTER_environment='vagrant' > FACTER_role='fisheye' puppet apply --modulepath > '/etc/puppet/modules:/tmp/vagrant-puppet/modules-0' site.ppNotice: Compiled > catalog for fisheye-10-0-2-15.inin.com in environment production in 2.22 > seconds > Notice: Finished catalog run in 30.76 seconds > > real 2m25.856s > user 0m5.124s > sys 0m3.830s > > #Time of facter with external fact > [root@fisheye-10-0-2-15 manifests]# time facter > analyticsapisegmentindexconsusmerwaittimeseconds => 1 > architecture => x86_64 > ... > uptime_hours => 0 > uptime_seconds => 2529 > > real 0m33.587s > user 0m0.658s > sys 0m0.849s > > #Removing external fact script > [root@fisheye-10-0-2-15 manifests]# rm > /etc/facter/facts.d/service_discovery.sh > rm: remove regular file `/etc/facter/facts.d/service_discovery.sh'? y > [root@fisheye-10-0-2-15 manifests]# ls /etc/facter/facts.d/ > > #Time of puppet run without external fact script > [root@fisheye-10-0-2-15 manifests]# time FACTER_environment='vagrant' > FACTER_role='fisheye' puppet apply --modulepath > '/etc/puppet/modules:/tmp/vagrant-puppet/modules-0' site.pp > Notice: Compiled catalog for fisheye-10-0-2-15.inin.com in environment > production in 2.06 seconds > Notice: > /Stage[main]/System::Facts/Facter::Fact[service_discovery]/File[/etc/facter/facts.d/service_discovery.sh]/ensure: > > created > Notice: Finished catalog run in 23.22 seconds > > real 0m27.550s > user 0m4.408s > sys 0m2.292s > > # Removing script again (cuz puppet run put it back) > [root@fisheye-10-0-2-15 manifests]# rm > /etc/facter/facts.d/service_discovery.sh > rm: remove regular file `/etc/facter/facts.d/service_discovery.sh'? y > [root@fisheye-10-0-2-15 manifests]# ls /etc/facter/facts.d/ > > #Time of facter run without external script > [root@fisheye-10-0-2-15 manifests]# time facter > architecture => x86_64 > augeasversion => 0.9.0 > ... > virtual => virtualbox > > real 0m0.687s > user 0m0.324s > sys 0m0.287s > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/84604e29-a050-4fbd-aad8-72c555452193%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] noop = true and what for test?
Understood JC. The use case is a little different and certainly non-Puppeterian in theoretic value but there is rationale for it. I.e. keeps Puppet agent installed but not running on the various nodes except for occasional manual run. When needed to be run (for example for an audit or a forced "drift-back", etc.), run puppet agent -t --noop. Gather logs (yaml's on PM, /var/log/messages on managed node or logged back, etc.) and analyze for changes which would be required to bring the system back into conformity. Then trace down the issues, find root cause, report, etc. We can filter out expected or excused log messages so that is not too much of a concern. The rationale for the above methodology is: hosting firm doing database hosting in a (very) highly secured environment seeking to ensure extreme care of the "crown jewels." We realize it is not an exciting use case. --Stuart December 3, 2013 7:37:00 AM UTC-8, jcbollinger wrote: > > > On Tuesday, December 3, 2013 2:18:25 AM UTC-6, Stuart Cracraft wrote: >> >> >> The rationale expressed to me has to do with non-specific >> auditing/security requirements... >> >> My requirement is to research and contradict with prima face evidence or >> report and confirm >> or some mixture thereof, which is not the simplest of assignments. >> >> > > So, you intend to use Puppet to *detect* variances from nodes' expected > configuration without bringing the target nodes into compliance? This is > possible. However, you do need to be aware of the limitations of noop mode. > > Chief among these is that when running in noop mode, Puppet has to proceed > as if it were successful in syncing each out-of-sync resource, without > knowing whether it actually would be successful and without having any > actual effect on the target node. This may produce anomalies when one > resource depends on another, either because the analysis of whether a > dependent resource is in sync might depend on its dependency being synced, > or in some cases because success of one resource can serve as a condition > for whether another is even considered for syncing. > > You should also be aware that even when running in noop mode, Puppet will > still execute commands on the target node to determine the current state of > each resource in the catalog. Generally speaking, these do not alter the > target node's state, but in principle they might trigger a security alert > or otherwise be logged, which would be a form of state change. Moreover, > Puppet cannot guarantee that the state-inspection commands executed by > third-party custom resource types or by Exec resources do not alter the > target node in other ways. > > > >> If anyone at Puppet Labs and the community can think of a way to >> contradict the first paragraph, send it over. >> >> Stuart >> >> *P.S. Thanks for your input that puppet agent need not be a daemon and >> can be run with:* >> >> * puppet agent -t --noop* >> >> *I will put that in place tomorrow.* >> >> > > In fact, just about any configuration option can be specified on the > command line as well, overriding the config file. > > > John > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7c022e19-13c9-430d-8a83-dcdcc36accae%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Puppet module testing & code coverage...
Gavin, Congratulations on your momentous decision. And it is an important one. You may want to go to www.amazon.com and pick up How Google Tests Software by Whittaker, Arbon, and Carollo. It is also a serious effort. Stuart Afternoon all > > I've read a fair few blogs, slideshares and other sources recently around > Module testing in Puppet, and it has spurned me on to start writing a test > framework around our internal modules... Yes, we aren't currently testing > our internal modules... Yes, we *should *be, and yes, I could give you a > list of excuses why we aren't, but the long and short is we (I) want to > start to :) > > Anyhow, I've been playing with puppetlabs_spec_helper, puppet-lint, > hiera-puppet-helper, librarian-puppet and Jenkins over the past couple of > days, and have got a working test framework finally... After lots of to-ing > and fro-ing with Hiera helpers, Rspec helpers, etc... > > So I've currently got Jenkins running parser tests, lint tests, and am > guna start running spec tests shortly, of which I currently have the grand > sum of 1 (yes, one). > However one thing I'm struggling to find is how to generate Puppet test > code coverage stats... > > So Puppetlabs_spec_helper includes *'rake* *coverage*', with a > description of: > "rake coverage # Generate code coverage information". > > However this doesn't appear to currently do anything useful :( > > $ ruby -S rcov -Ispec:lib --exclude spec >> ./spec/classes/server/linux_spec.rb >> -bash-4.1$ >> > > I found a snippet on the Puppetlabs blog [1] which says: > > 'coverage' runs rcov on your spec tests; it is only useful if your module >> includes Ruby extensions to Puppet. >> > > So my reading of that is that rcov doesn't check Puppet manifest coverage, > only Ruby extensions? > If that's the case, is there any alternative that *will *generate Puppet > manifest code coverage? > > Or am I completely barking up the wrong tree??? > > As always, thanks in advance for any responses/comments/etc... > > Cheers > Gavin > > [1] > http://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/82001dbc-cb72-455e-bda7-7dc193f10167%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] cli-driven list-file-based ad-hoc runs
Thankyou. > On Dec 3, 2013, at 1:06 AM, Felix Frank > wrote: > > If I understand this correctly, you are looking for a way to remotely > initiate noop runs on a subset of your agents with a selected set of tags. > > "puppet kick" used to be available for that, and has been superseded by > MCollective. To do this in a compliant way, you will need to build an > MCollective infrastructure. Scheduling the desired puppet runs should > become trivial then. > >> On 12/02/2013 08:23 PM, Stuart Cracraft wrote: >> some-magical-puppet-command some-list-file >> >> which based on the one-host-per-line some-list-file simply makes it happen >> on the remote nodes, running the classes then and only then with the normal >> YAML logging and /var/log/messages. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/6OlNTbxwaC8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/529D9EF8.3070604%40alumni.tu-berlin.de. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/A5246438-65D1-4126-A540-D35270D4ECB8%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] noop = true and what for test?
The rationale expressed to me has to do with non-specific auditing/security requirements... My requirement is to research and contradict with prima face evidence or report and confirm or some mixture thereof, which is not the simplest of assignments. If anyone at Puppet Labs and the community can think of a way to contradict the first paragraph, send it over. Stuart P.S. Thanks for your input that puppet agent need not be a daemon and can be run with: puppet agent -t --noop I will put that in place tomorrow. On Dec 2, 2013, at 3:52 PM, Rich Burroughs wrote: > Hi Stuart, > > I'm not sure what your use case is for running the agent as a daemon in noop > mode? I can't think of a situation at least in my workplace when I'd want to > do that. > > You know that you can run the agent once in noop mode from the command line? > You can do that without changing any configs really easily: > > puppet agent -t --noop > > We do that a lot where I work when we're testing code. The agent just runs > once and will report on what it would have done, but won't make any changes. > A lot of times when we test that we're doing it on a different git branch, > and we use "--environment=" to run against that other branch. > > I'm not sure if this is helpful, maybe you already know about it :) > > > Rich > > > > On Tue, Nov 26, 2013 at 5:07 PM, Stuart Cracraft wrote: > What I had to do (confirm or deny at-will please) is: > > uncomment the node in /etc/puppet/manifests/nodes.pp > > on the puppet master > > and > > on the daemon have > > noop = true > > in the main section of the puppet.conf > > and run the agent simply as /usr/bin/ruby /usr/bin/puppet agent --verbose > > Now the yaml's get generated, have the message indicating what would be > changed > but don't change it at all. > > And we get "Would have triggered 'refresh' from N events in the > /var/log/messages on > the node. > > The only betterment to the above would be that /var/log/message over on the > puppet master. > > Desirable and controllable > > Stuart > > > On Tuesday, November 26, 2013 4:30:14 PM UTC-8, Stuart Cracraft wrote: > Hi, > > When I put > > noop = true > > in /etc/puppet/puppet.conf > > on the node in question, I observe no changes. Great. Good > > But also, I see because of > > report = true > > absolutely zero information in the yaml regarding what would have > been changed. > > Is there an equivalent to the above for "test = true" or must I alter > the rc file to include --test ? > > Thanks ahead Puppet wizards!!! > > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/3b0f53bf-7d5d-4094-8a26-fe975a1e6f17%40googlegroups.com. > > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/0vhLrU0Rl_0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CAPGcbtCN5ovzMjx2ii0CVaFdzsr2_y%2BVD4JQ%3D3jPiMQF0pnH1Q%40mail.gmail.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/2F378B74-1B2E-4B10-9D54-D9EA5C30335A%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] cli-driven list-file-based ad-hoc runs
Currently, I have
/etc/puppet/puppet.conf
on my nodes with
[main]
:
noop = true
[agent]
:
And puppet is running as:
/usr/bin/ruby /usr/bin/puppet agent --verbose
On the Puppet Master:
/etc/puppet/manifests/nodes.pp
node 'basenode' {
include baseclass
}
:
node 'somepattern' inherits basenode {
class { 'abc::def':
randomvariables => "random values"
}
}
However, I am finding it inconvenient for running all assigned classes
on the node
or some subset of the nodes or some subset of classes and nodes, etc., and
only
when I specify they should be run (not 7x24x365, etc.):
What I want is, from the master do something like
some-magical-puppet-command some-list-file
which based on the one-host-per-line some-list-file simply makes it happen
on the remote nodes, running the classes then and only then with the normal
YAML logging and /var/log/messages.
Anyone implemented non-GUI, CLI-based run-from-listfile within Open Source
Puppet?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/f18a560d-e34a-4027-9eca-8770a4423f66%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] analyzing Puppet's actions and proposed actions via comprehensive reporting
I took care of this on Friday with a 30-line Perl script. Handy-dandy! On Nov 27, 2013, at 1:46 PM, Stuart Cracraft wrote: > Anyone know of a Ruby, Perl, Python, Bash, etc. script to do this already > written? > > Summarize /var/lib/puppet/reports/*all hosts*/*.yaml > Assume infinite store in above. > For any given period in the above, summarize: > action that was performed by puppet or would be performed if in noop > including the specific cli-command-line command equivalent (e.g. chmod > xyz abc, etc.) > number of times and dates/timetamps the actions were taken and what method > of initiation was done (human-initiated, puppet-initiated, etc.) > > So that's it. I don't care what it's written in as I am not a Ruby purist. > > --Stuart > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/JrZsoyPv6OU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/22c71b08-bc1a-454e-832e-910d0b2bc06e%40googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/3E591C94-0559-4C0E-A9F0-51FEB2AEB02F%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] analyzing Puppet's actions and proposed actions via comprehensive reporting
Anyone know of a Ruby, Perl, Python, Bash, etc. script to do this already written? Summarize /var/lib/puppet/reports/*all hosts*/*.yaml Assume infinite store in above. For any given period in the above, summarize: action that was performed by puppet or would be performed if in noop including the specific cli-command-line command equivalent (e.g. chmod xyz abc, etc.) number of times and dates/timetamps the actions were taken and what method of initiation was done (human-initiated, puppet-initiated, etc.) So that's it. I don't care what it's written in as I am not a Ruby purist. --Stuart -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/22c71b08-bc1a-454e-832e-910d0b2bc06e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] get a *structured* version of the puppet agent output
Get the book Learning Ruby.
Worth it.
> On Nov 27, 2013, at 7:44 AM, Dan White wrote:
>
> Very nice.
> I am still learning Ruby and this will help
>
> Thanks.
>
> “Sometimes I think the surest sign that intelligent life exists elsewhere in
> the universe is that none of it has tried to contact us.”
> Bill Waterson (Calvin & Hobbes)
>
> From: "David Portabella"
> To: puppet-users@googlegroups.com
> Sent: Wednesday, November 27, 2013 10:12:48 AM
> Subject: Re: [Puppet Users] get a *structured* version of the puppet agent
> output
>
> Thanks again! It is great to use the puppet report yaml files!
> here there is an example script that prints all resources statuses,
> then it filters them by taking only the services,
> then it filters them by taking only the services changed to running.
>
> test.ruby
> #!/usr/bin/ruby
>
> require 'puppet'
> filename = ARGV.first
> report = YAML.load_file(filename)
> rs = report.resource_statuses.values.sort_by{|r| r.resource}
>
> puts "PRINT ALL RESOURCES STATUSES."
> rs.each do |r|
> puts "#{r.change_count} #{r.events.map {|e| e.previous_value}}
> #{r.events.map {|e| e.desired_value}} #{r.resource}"
> end
>
> puts "PRINT ALL SERVICES."
> services = rs.select{|r| r.resource_type == 'Service'}
> services.each do |r|
> puts "#{r.change_count} #{r.events.map {|e| e.previous_value}}
> #{r.events.map {|e| e.desired_value}} #{r.resource}"
> end
>
> puts "PRINT ALL SERVICES CHANGED TO RUNNING."
> services_changed_to_running = rs.select{|r| r.resource_type == 'Service' &&
> r.change_count > 0 && r.events.index { |e| e.desired_value == :running } !=
> nil}
> services_changed_to_running.each do |r|
> puts "#{r.change_count} #{r.events.map {|e| e.previous_value}}
> #{r.events.map {|e| e.desired_value}} #{r.resource}"
> end
>
> example output:
> $ test.ruby /var/opt/lib/pe-puppet/reports/test/201311261645.yaml
> PRINT ALL RESOURCES STATUSES.
> 1 [:absent] [:directory] File[/var/app]
> 1 [:absent] [:file] File[/var/app/app.conf]
> 2 [0, "755"] [91, "775"] File[/var/log/tomcat6]
> 0 [] [] Filebucket[puppet]
> 1 [:absent] [:present] Group[release]
> 1 [:absent] [:present] Package[varnish]
> 0 [] [] Schedule[weekly]
> 1 [:stopped] [:running] Service[varnish]
> 0 [] [] Tidy[/etc/collectd.d/]
> 1 ["/sbin/nologin"] ["/bin/bash"] User[tomcat]
> ...
>
> PRINT ALL SERVICES.
> 1 [:stopped] [:running] Service[collectd]
> 1 [:stopped] [:running] Service[logstash-agent]
> 1 [:true] [:false] Service[logstash]
> 1 [:stopped] [:running] Service[nginx]
> 0 [] [] Service[rsyslog]
> 1 [:stopped] [:running] Service[statsd]
> 1 [:false] [:true] Service[supervisord]
> 1 [:stopped] [:running] Service[varnish]
>
> PRINT ALL SERVICES CHANGED TO RUNNING
> 1 [:stopped] [:running] Service[collectd]
> 1 [:stopped] [:running] Service[logstash-agent]
> 1 [:stopped] [:running] Service[nginx]
> 1 [:stopped] [:running] Service[statsd]
> 1 [:stopped] [:running] Service[varnish]
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/c70db1f6-b133-4290-a8e1-827ea239028b%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
> --
> You received this message because you are subscribed to a topic in the Google
> Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/cHpZlKkPmr4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/1253465309.4764508.1385567092577.JavaMail.root%40sz0126a.westchester.pa.mail.comcast.net.
> For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/36085646-13B6-4457-A36B-B2C8F97A603E%40me.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: noop = true and what for test?
And, also, update the runinterval = NN in the [agent] section of the puppet.conf. It would be great if Puppet had even more centralized control... The agent/node still has too much need-to-visit... On Tuesday, November 26, 2013 4:30:14 PM UTC-8, Stuart Cracraft wrote: > Hi, > > When I put > > noop = true > > in /etc/puppet/puppet.conf > > on the node in question, I observe no changes. Great. Good > > But also, I see because of > > report = true > > absolutely zero information in the yaml regarding what would have > been changed. > > Is there an equivalent to the above for "test = true" or must I alter > the rc file to include --test ? > > Thanks ahead Puppet wizards!!! > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/f3e36c71-cfb6-487d-ab28-ae1a67da13d0%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: noop = true and what for test?
What I had to do (confirm or deny at-will please) is: uncomment the node in /etc/puppet/manifests/nodes.pp on the puppet master and on the daemon have noop = true in the main section of the puppet.conf and run the agent simply as /usr/bin/ruby /usr/bin/puppet agent --verbose Now the yaml's get generated, have the message indicating what would be changed but don't change it at all. And we get "Would have triggered 'refresh' from N events in the /var/log/messages on the node. The only betterment to the above would be that /var/log/message over on the puppet master. Desirable and controllable Stuart On Tuesday, November 26, 2013 4:30:14 PM UTC-8, Stuart Cracraft wrote: > Hi, > > When I put > > noop = true > > in /etc/puppet/puppet.conf > > on the node in question, I observe no changes. Great. Good > > But also, I see because of > > report = true > > absolutely zero information in the yaml regarding what would have > been changed. > > Is there an equivalent to the above for "test = true" or must I alter > the rc file to include --test ? > > Thanks ahead Puppet wizards!!! > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/3b0f53bf-7d5d-4094-8a26-fe975a1e6f17%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Can't find good tutorial/how-to
I took Puppet Fundamentals in LA last week and there were THREE instructors for a teacher/student ratio I haven't seen since private school. Way to go Luke and Nigel and reports > On Nov 26, 2013, at 3:52 PM, Rich Burroughs wrote: > > I took the Puppet Fundamentals class a few months ago in Portland at Puppet > Labs and it was great. I definitely recommend it. I already was using Puppet > some in my day job but it gave me a lot more context. The instructor was very > well qualified and was fielding some pretty advanced questions, he had years > of experience working with the tool. > > And the second edition of Pro Puppet looks to be pretty good, I'm just a few > chapters in. > > > Rich > > >> On Tue, Nov 26, 2013 at 8:15 AM, Ken Barber wrote: >> > That was a dick move, Dan. Dick. Move. ;-p >> > >> > Not only are you hiding your vileness in an obfuscation (steering all >> > innocent list readers into your trap), but to add insult to injury, your >> > (arguably) annoying signature is larger in volume than the affront itself. >> > >> > No cookie. >> >> +1 thank you Felix :-). >> >> To keep on topic though, I think what Dan was trying to say in his own >> cheeky way was to check out the Learning Puppet tutorials and start >> there: http://docs.puppetlabs.com/learning/. It provides a VM to >> download and some lessons to walk through that should get you sorted >> out on the basics. >> >> Once you've moved beyond those lessons or you start to struggle, come >> back to the list and ask your specific questions. Puppet Labs also >> offers formal training if that is desirable. >> >> ken. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/CAE4bNTnr_gXRx5wGEJbk%3DoNW-LvQZ6xhEbG7rcfK%2BQV5Ke3Svg%40mail.gmail.com. >> For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/AlDGOx4W5Tw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CAPGcbtCncV8kCZVzpHnWKHu8-ZhUEcMd4tmy%3DDFuu%2BGmQ7Q7FQ%40mail.gmail.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/10F9B8FC-6DEF-437B-B5E6-34292D047ACA%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] noop = true and what for test?
Hi, When I put noop = true in /etc/puppet/puppet.conf on the node in question, I observe no changes. Great. Good But also, I see because of report = true absolutely zero information in the yaml regarding what would have been changed. Is there an equivalent to the above for "test = true" or must I alter the rc file to include --test ? Thanks ahead Puppet wizards!!! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/cbc0eb4c-243a-4b4f-815d-a4be4c316a6d%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: get a *structured* version of the puppet agent output
Understood. But, we have some real good troubleshooters here. And we want to get at core fixes. Not just log-examination, esoteric thought and bandaids. > On Nov 26, 2013, at 12:49 PM, Christopher Wood > wrote: > > (inline) > >> On Tue, Nov 26, 2013 at 10:43:31AM -0800, Stuart Cracraft wrote: >> We have this exact same requirement. >> Enforce a non-changing policy on the cloud, avoid automatic >> drift-prevention, await errors and reports, >> track down cause, fix root cause, apply puppet manifests to right things >> back, etc. >> Using Puppet to bandaid things without root-cause drill-down/post-mortem, >> is unwise > > I don't see how it's wise to let configuration deviations loiter in your > systems until a human has the time to manually fix them. This applies even > more if you're working at scale. Surely the ticket generated from (whatever > is monitoring agent runs that unpredictably change things) will still be > there once your configs are back in conformance? > > Short form would be that I think you'll experience fewer pain points if you > let puppet enforce your configuration like it's designed to. > >> We need a simple report-formatting mechanism like David says! >> >> On Tuesday, November 26, 2013 8:54:03 AM UTC-8, David Portabella wrote: >> >> puppet agent --verbose shows a verbose output of the changes done by >> puppet, such as: >> >> notice: >> >> /Stage[main]/Logstash::Config/Logstash::Configdir[agent]/File[/etc/logstash/agent/config]/owner: >> owner changed 'root' to 'logstash' >> notice: /Stage[main]/Varnish/Service[varnish]/ensure: ensure changed >> 'stopped' to 'running' >> >> I'd need to make some analysis about these changes, but it is not >> trivial to correctly parse this output. >> is there an option to get an structured version of this output (such as >> in xml or yaml)? >> so that I can make queries such as: >> - list all the files that have changed >> - list all the services that changed from stopped to running. >> ... >> >> yes, i can use sed and the like as a temporal workaround, but I'd need >> to have a robust approach. >> >> option1: maybe there is a tool that correctly parses this output? >> option2: or maybe there is a "puppet agent" equivalent command that >> directly produces a structured output? >> >> otherwise, how much time would it required to implement option2 (i am a >> software developer, and a puppet-user (not currently a >> puppet-developer)? >> >> Regards, >> David >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> >> [1]https://groups.google.com/d/msgid/puppet-users/5907f644-2285-4298-9a07-3d5e8de63a24%40googlegroups.com. >> For more options, visit [2]https://groups.google.com/groups/opt_out. >> >> References >> >> Visible links >> 1. >> https://groups.google.com/d/msgid/puppet-users/5907f644-2285-4298-9a07-3d5e8de63a24%40googlegroups.com >> 2. https://groups.google.com/groups/opt_out > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/cHpZlKkPmr4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/20131126204924.GA4749%40iniquitous.heresiarch.ca. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/696AE1AA-FE9D-4788-AE1E-0EC6FEBB03A7%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] get a *structured* version of the puppet agent output
I'll try it after exiting this meeting.
> On Nov 26, 2013, at 11:27 AM, Dan White wrote:
>
> Reference: http://docs.puppetlabs.com/puppet/3/reference/format_report.html
>
> Start with this:
>
> #!/usr/bin/ruby
>
> require 'puppet'
> if defined?(ARGV)
>filename = ARGV.first
>
>if defined?(filename)
>report = YAML.load_file(filename)
>print "Report for : "
>puts report.host
>print "Started : "
>puts report.time
>print "Log count: "
>puts report.logs.size
>print "Metrics count: "
>puts report.metrics.size
>print "Resource Status count: "
>puts report.resource_statuses.size
>print "Status: "
>puts report.status
>
>report.logs.each do |logg|
>puts "LOG -"
>if logg.file
>print "File: "
>puts logg.file
>end
>
>if logg.line
>print "Line: "
>puts logg.line
>end
>
>print "Level: "
>puts logg.level
>print "Message: "
>puts logg.message
>print "Source: "
>puts logg.source
>print "Tags: "
>puts logg.tags.join(" ")
>print "Time: "
>puts logg.time
>end
>
>report.resource_statuses.keys.each do |kk|
>if report.resource_statuses["#{kk}"].change_count > 0
>puts "RESOURCE STATUS "
>puts "#{kk} "
>report.resource_statuses["#{kk}"].events.each do |line|
>print "property: "
>puts line.property
>print "message: "
>puts line.message
>print "name: "
>puts line.name
>print "status: "
>puts line.status
>print "when: "
>puts line.time
> end
>end
>end
>puts "-"
>end
> end
> --
>
> Good luck.
>
>
> “Sometimes I think the surest sign that intelligent life exists elsewhere in
> the universe is that none of it has tried to contact us.”
> Bill Waterson (Calvin & Hobbes)
>
> - Original Message -
> From: "Stuart Cracraft"
> To: puppet-users@googlegroups.com
> Sent: Tuesday, November 26, 2013 2:10:53 PM
> Subject: Re: [Puppet Users] get a *structured* version of the puppet agent
> output
>
> Who will share a report generator for the yaml reports generated by puppet so
> that we do not have to reinvent wheel after wheel after wheel!!
>
>> On Nov 26, 2013, at 11:08 AM, "R.I.Pienaar" wrote:
>>
>>
>>
>> - Original Message -
>>> From: "Stuart Cracraft"
>>> To: puppet-users@googlegroups.com
>>> Sent: Tuesday, November 26, 2013 7:02:42 PM
>>> Subject: Re: [Puppet Users] get a *structured* version of the puppet agent
>>> output
>>>
>>> What we want is not more complexity, but more simplicity!
>>>
>>> I could go into
>>>
>>> puppet config print reportdir
>>>
>>> and then to its
>>>
>>> /var/lib/puppet/reports
>>>
>>> then to the host directories of interest and grep out message.
>>>
>>> But that seems a very sorry state of affairs.
>>>
>>> Puppetmasters speak UP!
>>
>> you do not need to grep out anything, as I showed you there is a ruby API
>> for accessing this data.
>>
>> If you use PuppetDB it will also be able to store this information and it has
>> APIs for extracting these logs in a structured manner.
>>
>> API access is about as much as you can hope for I think. Your alternatives
>> are
>> to write a logger plugin for Puppet that outputs JSON, I've done this and it
>> was not clear sailing.
>>
>>
>> --
>> You received this message becau
Re: [Puppet Users] Can't find good tutorial/how-to
Why is this not moderated? > On Nov 26, 2013, at 11:21 AM, Dan White wrote: > > My apologies to all for the inappropriate response. > > “Sometimes I think the surest sign that intelligent life exists elsewhere in > the universe is that none of it has tried to contact us.” > Bill Waterson (Calvin & Hobbes) > > From: "R.I.Pienaar" > To: puppet-users@googlegroups.com > Sent: Tuesday, November 26, 2013 1:39:42 PM > Subject: Re: [Puppet Users] Can't find good tutorial/how-to > > > > - Original Message - > > From: "Felix Frank" > > To: puppet-users@googlegroups.com > > Sent: Tuesday, November 26, 2013 4:02:10 PM > > Subject: Re: [Puppet Users] Can't find good tutorial/how-to > > > > That was a dick move, Dan. Dick. Move. ;-p > > While I agree posting lmgtfy links is not ok in response to questions here > neither > is calling things a "dick move" on a public mailing list. > > Lets keep it civil and inclusive > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/1217578909.560.1385491182459.JavaMail.zimbra%40devco.net. > For more options, visit https://groups.google.com/groups/opt_out. > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/AlDGOx4W5Tw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/978010964.4751539.1385493706820.JavaMail.root%40sz0126a.westchester.pa.mail.comcast.net. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/93A20609-8F49-4976-AF06-8BB547DA389F%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] get a *structured* version of the puppet agent output
Puppet Labs: What report generators do you have and provide at your website so that we can report intelligently? Stuart > On Nov 26, 2013, at 11:15 AM, "R.I.Pienaar" wrote: > > > > - Original Message - >> From: "Stuart Cracraft" >> To: puppet-users@googlegroups.com >> Sent: Tuesday, November 26, 2013 7:10:53 PM >> Subject: Re: [Puppet Users] get a *structured* version of the puppet agent >> output >> >> Who will share a report generator for the yaml reports generated by puppet so >> that we do not have to reinvent wheel after wheel after wheel!! > > not everyone shares the same goals so everyone tend to write them, but here > you go this is one I wrote > > http://www.devco.net/archives/2013/10/10/cli-report-viewer-for-puppet.php > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/cHpZlKkPmr4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/216012641.610.1385493314105.JavaMail.zimbra%40devco.net. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/41DE4370-2957-41D5-9DAC-6AFA8B99C0B7%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] get a *structured* version of the puppet agent output
Who will share a report generator for the yaml reports generated by puppet so that we do not have to reinvent wheel after wheel after wheel!! > On Nov 26, 2013, at 11:08 AM, "R.I.Pienaar" wrote: > > > > - Original Message - >> From: "Stuart Cracraft" >> To: puppet-users@googlegroups.com >> Sent: Tuesday, November 26, 2013 7:02:42 PM >> Subject: Re: [Puppet Users] get a *structured* version of the puppet agent >> output >> >> What we want is not more complexity, but more simplicity! >> >> I could go into >> >> puppet config print reportdir >> >> and then to its >> >> /var/lib/puppet/reports >> >> then to the host directories of interest and grep out message. >> >> But that seems a very sorry state of affairs. >> >> Puppetmasters speak UP! > > you do not need to grep out anything, as I showed you there is a ruby API > for accessing this data. > > If you use PuppetDB it will also be able to store this information and it has > APIs for extracting these logs in a structured manner. > > API access is about as much as you can hope for I think. Your alternatives > are > to write a logger plugin for Puppet that outputs JSON, I've done this and it > was not clear sailing. > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/cHpZlKkPmr4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/1024951816.609.1385492893475.JavaMail.zimbra%40devco.net. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6E1AA223-0401-485C-8E4C-AABF12FB2291%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] get a *structured* version of the puppet agent output
What we want is not more complexity, but more simplicity!
I could go into
puppet config print reportdir
and then to its
/var/lib/puppet/reports
then to the host directories of interest and grep out message.
But that seems a very sorry state of affairs.
Puppetmasters speak UP!
On Tuesday, November 26, 2013 8:57:48 AM UTC-8, R.I. Pienaar wrote:
>
>
> - Original Message -
> > From: "David Portabella" >
> > To: puppet...@googlegroups.com
> > Sent: Tuesday, November 26, 2013 4:54:03 PM
> > Subject: [Puppet Users] get a *structured* version of the puppet agent
> output
> >
> >
> >
> > puppet agent --verbose shows a verbose output of the changes done by
> > puppet, such as:
> >
> > notice:
> >
> /Stage[main]/Logstash::Config/Logstash::Configdir[agent]/File[/etc/logstash/agent/config]/owner:
>
>
> > owner changed 'root' to 'logstash'
> > notice: /Stage[main]/Varnish/Service[varnish]/ensure: ensure changed
> > 'stopped' to 'running'
> >
> > I'd need to make some analysis about these changes, but it is not
> trivial
> > to correctly parse this output.
>
> The same data is in the reports, a bit better there.
>
> >> require 'puppet'
> >> YAML.load_file("/var/lib/puppet/state/last_run_report.yaml").logs.first
> => # @message="Finished catalog run in 0.18 seconds", @time=Thu Nov 21 16:38:42
> + 2013, @tags=["notice"]>
>
>
> > is there an option to get an structured version of this output (such as
> in
> > xml or yaml)?
> > so that I can make queries such as:
> > - list all the files that have changed
> > - list all the services that changed from stopped to running.
> > ...
> >
> > yes, i can use sed and the like as a temporal workaround, but I'd need
> to
> > have a robust approach.
> >
> > option1: maybe there is a tool that correctly parses this output?
> > option2: or maybe there is a "puppet agent" equivalent command that
> > directly produces a structured output?
> >
> > otherwise, how much time would it required to implement option2 (i am a
> > software developer, and a puppet-user (not currently a
> puppet-developer)?
> >
> > Regards,
> > David
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups
> > "Puppet Users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an
> > email to puppet-users...@googlegroups.com .
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/puppet-users/7e4a2aa2-2bd2-4311-81c2-8f7e4bd12a5b%40googlegroups.com.
>
>
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/512658ed-2f0d-42fc-b049-cd3c41b98aca%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: set password to never expire for a user
password_max_age is less destructive. I chose it.
On Tuesday, November 26, 2013 6:23:19 AM UTC-8, jcbollinger wrote:
>
>
> On Monday, November 25, 2013 5:11:13 PM UTC-6, Stuart Cracraft wrote:
>>
>> I have direction to use puppet
>> rather than the OS and exec...
>>
>>
>
> Possibly you are looking for the 'expiry' User property:
> http://docs.puppetlabs.com/references/3.stable/type.html#user-attribute-expiry<http://www.google.com/url?q=http%3A%2F%2Fdocs.puppetlabs.com%2Freferences%2F3.stable%2Ftype.html%23user-attribute-expiry&sa=D&sntz=1&usg=AFQjCNF_uxc-j6fF7qGzS0S5eJnAEt3rUw>
>
> user { 'alice':
> # ...
> expiry => 'absent'
> }
>
> It's a bit unclear to me, though, whether there is a distinction between
> the user's password expiring and the user itself expiring. Probably what
> you get with that is 'chage -E' or an appropriate local analog.
>
> Alternatively, you may be looking for the 'max_password_age' User
> property:
> http://docs.puppetlabs.com/references/3.stable/type.html#user-attribute-password_max_age<http://www.google.com/url?q=http%3A%2F%2Fdocs.puppetlabs.com%2Freferences%2F3.stable%2Ftype.html%23user-attribute-password_max_age&sa=D&sntz=1&usg=AFQjCNEuysglo362cbk328OiqoUVUpMsJw>.
>
> Inasmuch as that looks to be designed to be backed by 'chage -M' or a local
> equivalent, this may do what you want:
>
> user { 'bob':
> # ...
> max_password_age => -1
> }
>
>
> John
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/d5623077-ae18-43dd-a536-7cd0d3053436%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
