[Puppet Users] Access control for Puppet Dashboard
Hello all, Is it possible at the moment to set up access control for Puppet Dashboard? As of now anyone within our organization will have full access to the dashboard. I thought I'd set up regular Apache access control, but this will probably not work well with dashboard as an external node tool. I found http://projects.puppetlabs.com/issues/3459 which suggest running dashboard unsecurily on localhost, but I'm hoping that there are other ways. Best regards, Kenneth -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Problems when puppet runs on freebsd
Hey guys! I have hundreds of freebsd servers to manage, so i try to deploy puppet on my servers. The version of puppet client i used is 0.25.4 , while puppetmaster uses the same version , which is a debian system. The problems i encountered are as follows: 1. when i run puppetd -t -d on client side, it returns err: Could not retrieve catalog from remote server: Error 403 on SERVER: Forbidden request: bjchinanetxxx.xxx.domainname .(xxx.xxx.xxx.xxx) access to /catalog/bjchinanetxxx.xxx.domainname [find] authenticated. File /etc/puppet/auth.conf on master side is as default , path ~ ^/catalog/([^/]+)$ method find allow $1 then i modified allow $1 to allow * to solve the problem ,but i don't understand why this problem comes out on freebsd . When i tested on debian , the default /etc/puppet/auth.conf is ok. 2. when i tried to use exec resource to run script to do sth , sometimes it returned 1 instead of 0 , even i put 'exit 0' at the end of my script.@@ I'm so confused. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] cucumber-puppet and environments
Now that cucumber-puppet is a Puppet Labs project, I guess it is time to email questions about it here ;) I'm in the process of adding RoR environment support into my module tree, so instead of just having a single location for all modules, I now have several environments. Logically to test my different environments I'll need to call cucumber-puppet once for each environment (and I guess it is possible I'll need to change which tests I run in each). What mechanism is there (or is needed) in order to make cucumber-puppet aware of the environment (or at least modulepath) settings? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Error in using custom providers - can't recognize custom provider
Hi, I'm using custom providers for installing pear and pecl package. But every time I ran puppetd --test, it says that pear provider is not recognized. But when I remove the custom providers from /var/lib/puppet/lib/puppet/provider (client server), and ran puppetd --test once more, it downloads the custom providers and everything works out fine. Is this a bug in 2.6 --Mark -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] cucumber-puppet and environments
Hi Oliver, try: http://projects.puppetlabs.com/projects/1/wiki/Using_Multiple_Environments On Sep 14, 2010, at 7:09 AM, Oliver ohook...@gmail.com wrote: Now that cucumber-puppet is a Puppet Labs project, I guess it is time to email questions about it here ;) I'm in the process of adding RoR environment support into my module tree, so instead of just having a single location for all modules, I now have several environments. Logically to test my different environments I'll need to call cucumber-puppet once for each environment (and I guess it is possible I'll need to change which tests I run in each). What mechanism is there (or is needed) in order to make cucumber-puppet aware of the environment (or at least modulepath) settings? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] UK Meet-up?
Hi all, I've been to a few conferences where puppet has been presented, but would love to know if there's a more puppet specific meet-up planned in the UK any time soon? t.i.a. Joel -- $ echo kpfmAdpoofdufevq/dp/vl | perl -pe 's/(.)/chr(ord($1)-1)/ge' -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] UK Meet-up?
- Joel Merrick joel.merr...@gmail.com wrote: Hi all, I've been to a few conferences where puppet has been presented, but would love to know if there's a more puppet specific meet-up planned in the UK any time soon? Not that I am aware of, we have a london devops group (londondevops.org) that meet regularly and we discuss all sorts of things that might be of interest but not specific to puppet. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] UK Meet-up?
On 14 September 2010 14:09, R.I.Pienaar r...@devco.net wrote: - Joel Merrick joel.merr...@gmail.com wrote: Hi all, I've been to a few conferences where puppet has been presented, but would love to know if there's a more puppet specific meet-up planned in the UK any time soon? Not that I am aware of, we have a london devops group (londondevops.org) that meet regularly and we discuss all sorts of things that might be of interest but not specific to puppet. There were a few puppet meets in London years ago, but nothing recent AFAIK. A puppet pint after the next Devops might be nice. Gary -- Gary Law Email: gary...@garylaw.net Chat googletalk/messenger: gary@gmail.com iChat/jabber/AIM: gary@mac.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] UK Meet-up?
- Gary Law gary...@garylaw.net wrote: On 14 September 2010 14:09, R.I.Pienaar r...@devco.net wrote: - Joel Merrick joel.merr...@gmail.com wrote: Hi all, I've been to a few conferences where puppet has been presented, but would love to know if there's a more puppet specific meet-up planned in the UK any time soon? Not that I am aware of, we have a london devops group (londondevops.org) that meet regularly and we discuss all sorts of things that might be of interest but not specific to puppet. There were a few puppet meets in London years ago, but nothing recent AFAIK. A puppet pint after the next Devops might be nice. When there's something going on we do make it puppet themed, like when Luke was in town. Doubt there's enough traction here for too focused events :( -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Making edits to /etc/system on Solaris
Alternatively you could just use a template /etc/system where you put most of the logic into the ERB by putting if defined entries in. -- Derek Yarnell On Sep 14, 2010, at 1:25 AM, John Warburton jwarbur...@gmail.com wrote: I may not go down that path, but you've triggered something in my head - why don't I use concat file? http://www.devco.net/archives/2010/03/12/puppet_concat_20100312.php If there isn't anything more elegant, I'll use concat Thanks for the different viewing angle :-) John On 14 September 2010 15:03, Brian Gallew g...@gallew.org wrote: I've basically ended up with one /etc/system to rule them all (and in the darkness bind them?). Fortunately for me, my systems are large enough to support this and there have been no conflicting requirements. I'm sure I'm losing some tiny bit of performance and memory, but I really can't work up enough concern to do anything about it. On Mon, Sep 13, 2010 at 5:29 PM, John Warburton jwarbur...@gmail.com wrote: Hi All Just wondering what everyone else does when editing /etc/system on Solaris It is on the Augeas To Do list (http://augeas.net/page/Augeas_on_Solaris) - has anyone tried a lens for it? I tried to start but the file format is almost free form and there would always be an exception causing the parse to fail So, apart from http://projects.puppetlabs.com/projects/1/wiki/Simple_Text_Patterns, I don't see any other solution Thanks John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- John Warburton Ph: 0417 299 600 Email: jwarbur...@gmail.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] cucumber-puppet and environments
On Tue, Sep 14, 2010 at 08:34:00AM -0400, Ryan Coleman wrote: Hi Oliver, try: http://projects.puppetlabs.com/projects/1/wiki/Using_Multiple_Environments I've never been fond of the way RoR treats environments (or, at least, the way RoR developers treat them). The thing I really don't like about the way Puppet implements them is the fact that the *client* specifies which environment to use. This is just plain wrong. At the very least, the puppetmaster should be able to ignore or override the client's idea of which environment to use on a per host basis. -- Bruce I see a mouse. Where? There, on the stair. And its clumsy wooden footwear makes it easy to trap and kill. -- Harry Hill signature.asc Description: Digital signature
Re: [Puppet Users] ANNOUNCE: Puppet 2.6.1 released!
On Mon, Sep 13, 2010 at 10:26 PM, James Turnbull ja...@puppetlabs.comwrote: In the long Puppet tradition of fast releases and agile iteration comes the 2.6.1 release! 2.6.1 is a maintenance release in the 2.6.x branch. It contains a number of functional and performance enhancements including preliminary support for running Puppet under JRuby (thanks Brice!). We've include release notes below that you can also see at: http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes The release candidate is available for download at: http://puppetlabs.com/downloads/puppet/puppet-2.6.1.tar.gz I take it you mean 'release', right? :) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] UK Meet-up?
On 09/14/2010 03:25 PM, R.I.Pienaar wrote: Doubt there's enough traction here for too focused events :( A Europe-based Puppet Camp would probably go over well ; i mean, us Europeans use Puppet, too. :) -- Daniel Maher dma AT witbe DOT net The Internet is completely over. -- Prince -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] UK Meet-up?
- Daniel Maher d...@witbe.net wrote: On 09/14/2010 03:25 PM, R.I.Pienaar wrote: Doubt there's enough traction here for too focused events :( A Europe-based Puppet Camp would probably go over well ; i mean, us Europeans use Puppet, too. :) Yeah the one held this may did go down well :P -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] cucumber-puppet and environments
On Tue, Sep 14, 2010 at 6:28 AM, Bruce Richardson itsbr...@workshy.org wrote: On Tue, Sep 14, 2010 at 08:34:00AM -0400, Ryan Coleman wrote: Hi Oliver, try: http://projects.puppetlabs.com/projects/1/wiki/Using_Multiple_Environments I've never been fond of the way RoR treats environments (or, at least, the way RoR developers treat them). The thing I really don't like about the way Puppet implements them is the fact that the *client* specifies which environment to use. This is just plain wrong. At the very least, the puppetmaster should be able to ignore or override the client's idea of which environment to use on a per host basis. Bruce, we have some bugs in around this. The external node classifier should be able to set the environment, and should be able to do so without the client environment specification being consulted at all if that's what you want. I'll try and dig them up today, but from what I understand it's not a simple fix. -- Bruce I see a mouse. Where? There, on the stair. And its clumsy wooden footwear makes it easy to trap and kill. -- Harry Hill -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkyPeJEACgkQtkVqYTMBSwExSwCeP/F7rMGXs9IQ7Ulz1gsGxD/9 WTEAnRwgtxB46w6bq4Ft46DmhUMYw26q =KRMp -END PGP SIGNATURE- -- nigel -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] call define and keep getting Duplicate definition
well I upgraded to 2.6.1 and it works.. changed nothing!! But thanks for the help and your time Nan!! -- -ls -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Provider useradd does not support features manages_passwords; not managing attribute password
Hello I just upgraded to 2.6.1 and now when I create a new account I can no longer add the encrypted password added... the message i see is Provider useradd does not support features manages_passwords; not managing attribute password I presume I need to add something to tell the primitive 'user' to add the password? thanks -- -ls -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Managing puppet.conf and other critical config files
Is there any built-in method for puppet to update its own configs and then restart a puppetd run should they change? One of the (few) features of cfengine I always liked was that you had your emergency configs, which allowed you to update your primary cfengine configs even if you made a mistake that hosed up your ability to run updates. It'd be nice if there was some mechanism akin to the pluginsync option that would allow you to update your core configs while just specifying the server they should be pulled from. Even if there's no interest in a feature like this, I'd be interested in hearing how others keep there puppet.conf updated across their environments without causing problems. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] UK Meet-up?
On Tue, Sep 14, 2010 at 3:49 PM, Daniel Maher d...@witbe.net wrote: On 09/14/2010 03:25 PM, R.I.Pienaar wrote: Doubt there's enough traction here for too focused events :( A Europe-based Puppet Camp would probably go over well ; i mean, us Europeans use Puppet, too. :) +1 ! As much as I'd love to go to San Francisco, getting the buy-in from $WORK is a little difficult :) -- $ echo kpfmAdpoofdufevq/dp/vl | perl -pe 's/(.)/chr(ord($1)-1)/ge' -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] ANNOUNCE: Puppet 2.6.1 released!
Disconnect wrote: The release candidate is available for download at: http://puppetlabs.com/downloads/puppet/puppet-2.6.1.tar.gz I take it you mean 'release', right? :) Yes - that should be release. Regards James Turnbull -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Managing puppet.conf and other critical config files
We manage puppet.conf as a template. I've often wanted something similar to your feature request, where you could signify in a puppet manifest that the whole run should simply restart at that point. You should file it :) Have you thought about maybe using the pre-run hook? We use a wrapper script that upgrades an internal metapackage before the puppet run starts, so we can always do things in that package to work around this limitation. I didn't know you could do pre-run hooks. Where's the documentation on that? I'm currently using RIP's concat module for our puppet configs, so we can tack on some extra stuff for puppetmasterd for the servers. It's templated also, so we can specify the server = line per environment. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Managing puppet.conf and other critical config files
On Tue, Sep 14, 2010 at 9:24 AM, James Cammarata j...@sngx.net wrote: We manage puppet.conf as a template. I've often wanted something similar to your feature request, where you could signify in a puppet manifest that the whole run should simply restart at that point. You should file it :) Have you thought about maybe using the pre-run hook? We use a wrapper script that upgrades an internal metapackage before the puppet run starts, so we can always do things in that package to work around this limitation. I didn't know you could do pre-run hooks. Where's the documentation on that? nigelk$ puppetd --genconfig | grep -B4 run_command # A command to run before every agent run. If this command returns a non-zero # return code, the entire Puppet run will fail. # The default value is ''. # prerun_command = -- # A command to run after every agent run. If this command returns a non-zero # return code, the entire Puppet run will be considered to have failed, even though it might have # performed work during the normal run. # The default value is ''. # postrun_command = I'm currently using RIP's concat module for our puppet configs, so we can tack on some extra stuff for puppetmasterd for the servers. It's templated also, so we can specify the server = line per environment. We've taken a different approach and have an entirely separate config file and vardir for our puppetmasters. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- nigel -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] UK Meet-up?
Joel Merrick wrote: On Tue, Sep 14, 2010 at 3:49 PM, Daniel Maherd...@witbe.net wrote: On 09/14/2010 03:25 PM, R.I.Pienaar wrote: Doubt there's enough traction here for too focused events :( A Europe-based Puppet Camp would probably go over well ; i mean, us Europeans use Puppet, too. :) +1 ! Well we did just have Puppet Camp Europe in Ghent earlier in the year! :) It's not like we left you guys out. :P http://puppetcamp.org/2010/02/15/puppetcamp-2010-europe-will-happen-in-ghent-belgium-2728-may/ We'll almost certainly be having another in the new year in Europe - probably on a similar time frame. In the meantime there is training in London in November: http://www.puppetlabs.com/events/london-nov-2010/ Someone will be across for that and Puppet Labs staff are notorious for getting sore, dry throats during visits that require frequent fermented vegetable drink lubrication. :) Regards James Turnbull -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Provider useradd does not support features manages_passwords; not managing attribute password
Luc Suryo wrote: Hello I just upgraded to 2.6.1 and now when I create a new account I can no longer add the encrypted password added... the message i see is Provider useradd does not support features manages_passwords; not managing attribute password I presume I need to add something to tell the primitive 'user' to add the password? What platform is this? The useradd provider should manage passwords IF the libshadow package is installed. Regards James Turnbull -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Access control for Puppet Dashboard
On Tue, 14 Sep 2010 08:19:24 +0200, Kenneth Holter wrote: Hello all, Is it possible at the moment to set up access control for Puppet Dashboard? As of now anyone within our organization will have full access to the dashboard. I thought I'd set up regular Apache access control, but this will probably not work well with dashboard as an external node tool. I found http://projects.puppetlabs.com/issues/3459 which suggest running dashboard unsecurily on localhost, but I'm hoping that there are other ways. Best regards, Kenneth Currently, the Dashboard doesn't have any built-in authentication, or authorization (this isn't _quite_ true, but it's close enough to make no difference). There is a ticket generally about this[1], but (as far as I'm aware) it's a bit hand-wavey, since there hasn't been much speced out (but, again, I could be wrong about this). If you know what granularity of access-control you'd like/need/actually-use, I'd love to hear what that is (especially if you would be kind enough to take some time to comment in the ticket I mentioned earlier). As far as getting access control right now, it's pretty much what you mentioned: Putting Dashboard behind something like Apache access controls. You should still be able to use the dashboard as an external node tool, but I'd imagine that you'd either need to allow public access to GET at http://dashboard-host/nodes/* (specifically for requests accepting 'text/yaml'), or modify the external_node script to pass along auth credentials. I haven't actually done this myself, so I'd love it if someone with more experience doing this could chime in. Hope this helps. [1] http://projects.puppetlabs.com/issues/4168 -- Jacob Helwig signature.asc Description: Digital signature
Re: [Puppet Users] Re: Setup 2.6 + apache, passenger
I'm trying to use puppet with passenger as well. I'm running puppet 2.6.1 and I'm running into the issue mentioned under the troubleshooting section of http://projects.reductivelabs.com/projects/puppet/wiki/Using_Passenger. The instructions there are very vague. I've tried adding the ca_name setting to puppet.conf on the puppet master, but it doesn't seem to have any effect. I took a look at http://docs.puppetlabs.com/references/stable/configuration.html and there does not appear to be a ca_name option. On the other hand, there is a certname option. When I set this option to something like ca-foo.bar.com and restart the puppet master, I do see a new certificate generated, however, I get errors on the client side stating that the cert is incorrect Could not retrieve catalog from remote server: hostname was not match with the server certificate. Any suggestions? On Fri, Sep 10, 2010 at 12:54 PM, Stefan Schlesinger s...@ono.at wrote: On Sep 10, 2010, at 15:47 , Gavin wrote: File does not exist: /usr/share/puppet/rack/puppetmasterd/public/ production. Actually I think I can reproduce your problem when I turn that option off in puppetmaster vhost: RackAutoDetect On ;-) Regards, Stefan. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Provider useradd does not support features manages_passwords; not managing attribute password
James its a CentOS 5.5. box, and it worked before I installed 2.6.1 this morning. Do I need to add manages_passwords = true maybe? thanks On Tue, Sep 14, 2010 at 9:34 AM, James Turnbull ja...@puppetlabs.comwrote: Luc Suryo wrote: Hello I just upgraded to 2.6.1 and now when I create a new account I can no longer add the encrypted password added... the message i see is Provider useradd does not support features manages_passwords; not managing attribute password I presume I need to add something to tell the primitive 'user' to add the password? What platform is this? The useradd provider should manage passwords IF the libshadow package is installed. Regards James Turnbull -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- -ls -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Provider useradd does not support features manages_passwords; not managing attribute password
Luc Suryo wrote: James its a CentOS 5.5. box, and it worked before I installed 2.6.1 this morning. Do I need to add manages_passwords = true maybe? No - that will have no impact. Can you confirm you have libshadow installed? If you do it's a bug and can you please log it. Regards James Turnbull -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Provider useradd does not support features manages_passwords; not managing attribute password
Hmm very odd and yes your are correct somehow ruby-shadow was removed... I added it back and it works again.. not a bug.. sorry and thanks On Tue, Sep 14, 2010 at 9:45 AM, James Turnbull ja...@puppetlabs.comwrote: Luc Suryo wrote: James its a CentOS 5.5. box, and it worked before I installed 2.6.1 this morning. Do I need to add manages_passwords = true maybe? No - that will have no impact. Can you confirm you have libshadow installed? If you do it's a bug and can you please log it. Regards James Turnbull -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- -ls -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Access control for Puppet Dashboard
On Tue, Sep 14, 2010 at 9:34 AM, Jacob Helwig ja...@puppetlabs.com wrote: As far as getting access control right now, it's pretty much what you mentioned: Putting Dashboard behind something like Apache access controls. You should still be able to use the dashboard as an external node tool, but I'd imagine that you'd either need to allow public access to GET at http://dashboard-host/nodes/* (specifically for requests accepting 'text/yaml'), or modify the external_node script to pass along auth credentials. I haven't actually done this myself, so I'd love it if someone with more experience doing this could chime in. Teyo has written an external nodes classifier script using existing certificates to secure puppet master access to dashboard: http://projects.puppetlabs.com/issues/4688 This should allow: SSLVerifyClient optional SSLOption +FakeBasicAuth Thanks, Nan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Setup 2.6 + apache, passenger
On Tue, Sep 14, 2010 at 9:35 AM, M C maem...@gmail.com wrote:
I'm trying to use puppet with passenger as well. I'm running puppet 2.6.1
and I'm running into the issue mentioned under the troubleshooting section
of http://projects.reductivelabs.com/projects/puppet/wiki/Using_Passenger.
The instructions there are very vague. I've tried adding the ca_name
setting to puppet.conf on the puppet master, but it doesn't seem to have any
effect. I took a look at
http://docs.puppetlabs.com/references/stable/configuration.html and there
does not appear to be a ca_name option. On the other hand, there is a
certname option. When I set this option to something like ca-foo.bar.com
and restart the puppet master, I do see a new certificate generated,
however, I get errors on the client side stating that the cert is incorrect
Could not retrieve catalog from remote server: hostname was not match with
the server certificate. Any suggestions?
What's the output of puppetd --genconfig | grep server = ? By default
puppet agent connects to the puppet master named puppet.
Try setting certdnsname=puppet:puppet.bar.com (include the output of server
=... if it's not puppet). I'm guessing the client is is resolving puppet
master through a DNS cname, puppet.bar.com = ca-foo.bar.com. The
certificate X509v3 Subject Alternative Name should include all possible DNS
cname for the puppet master.
You can examine the puppet master certificate using the command:
openssl x509 -text -in /var/lib/puppet/ssl/certs/${puppetmaster_fqdn}.pem
certname configures the certificate CN= and in your case should display:
Subject: CN=ca-foo.bar.com
certdnsname configures the following section:
X509v3 Subject Alternative Name:
DNS:puppet, DNS:puppet.bar.com
Thanks,
Nan
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Setup 2.6 + apache, passenger
Nan,
The puppet master is running on a machine called admin. We have a cname
that resolves puppet.bar.com to admin.baz.bar.com. I've checked the
certificate and it shows the following:
Subject: CN=admin.baz.bar.com
X509v3 Subject Alternative Name:
DNS:puppet, DNS:admin.baz.bar.com, DNS:puppet.baz.bar.com
I added the following line to /etc/puppet/puppet.conf and restarted the
puppet master:
certdnsname = puppet:puppet.bar.com:admin.baz.bar.com
Restarting the puppet master with the certdnsname option set did not change
the certificate in /var/lib/puppet/ssl/certs/admin.baz.bar.com at all.
My understanding from the documentation is that the issue was with ca.pem.
Is that not the case? Is there some trick to get puppet to regenerate the
certs properly? From what I've been able to find, this seems to be at least
partially related to Bug #4226. Please let me know what I can do to get
puppet to work with passenger as we're rapidly approaching the point where
we'd like to roll this out, but WEBbrick isn't going to satisfy our needs.
On Tue, Sep 14, 2010 at 2:02 PM, Nan Liu n...@puppetlabs.com wrote:
On Tue, Sep 14, 2010 at 9:35 AM, M C maem...@gmail.com wrote:
I'm trying to use puppet with passenger as well. I'm running puppet 2.6.1
and I'm running into the issue mentioned under the troubleshooting section
of http://projects.reductivelabs.com/projects/puppet/wiki/Using_Passenger.
The instructions there are very vague. I've tried adding the ca_name
setting to puppet.conf on the puppet master, but it doesn't seem to have any
effect. I took a look at
http://docs.puppetlabs.com/references/stable/configuration.html and there
does not appear to be a ca_name option. On the other hand, there is a
certname option. When I set this option to something like
ca-foo.bar.com and restart the puppet master, I do see a new certificate
generated, however, I get errors on the client side stating that the cert is
incorrect Could not retrieve catalog from remote server: hostname was not
match with the server certificate. Any suggestions?
What's the output of puppetd --genconfig | grep server = ? By default
puppet agent connects to the puppet master named puppet.
Try setting certdnsname=puppet:puppet.bar.com (include the output of
server =... if it's not puppet). I'm guessing the client is is resolving
puppet master through a DNS cname, puppet.bar.com = ca-foo.bar.com. The
certificate X509v3 Subject Alternative Name should include all possible DNS
cname for the puppet master.
You can examine the puppet master certificate using the command:
openssl x509 -text -in /var/lib/puppet/ssl/certs/${puppetmaster_fqdn}.pem
certname configures the certificate CN= and in your case should display:
Subject: CN=ca-foo.bar.com
certdnsname configures the following section:
X509v3 Subject Alternative Name:
DNS:puppet, DNS:puppet.bar.com
Thanks,
Nan
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Strange exec issue with tar
I do have a really strange issue with exec a tar command with puppet
2.6.0. If I run it with puppetmasterd I get the following error
message:
(//my.domain.net//Stage[main]/Workerzone/Build::Install[top]/
Exec[extract-top]/returns) change from notrun to 0 failed: /bin/bash -
c '/usr/sbin/tar -xzvf /usr/local/src/top-3.7.tar.gz' returned 1
instead of one of [0] at /etc/puppet/modules/build/manifests/init.pp:
58
If I run the code manually with 'puppetd -t --debug' there are no
errors. What am I doing wrong? Here is my code:
# build::install { 'top':
# download = 'http://www.unixtop.org/dist/top-3.7.tar.gz',
# creates = '/url/local/bin/top',
# }
define build::install ($download, $creates, $pkg_folder='',
$pkg_format=tar, $pkg_extension=, $buildoptions=,
$rm_build_folder=true) {
if defined( Package['build-essential'] ) {
debug(build-essential already installed)
} else {
package { 'build-essential': ensure = installed }
}
$filename = basename($download)
$extension = $pkg_format ? {
zip = .zip,
tar = .tar.gz,
bzip= .tar.bz2,
default = $pkg_extension,
}
$foldername = $pkg_folder ? {
'' = gsub($filename, $extension, ),
default = $pkg_folder,
}
$extractor = $pkg_format ? {
zip = /usr/bin/unzip -q -d /usr/local/src,
bzip= /usr/sbin/tar -xjf,
default = /usr/sbin/tar -xzf ,
}
# download is fine
exec { download-$name:
cwd = /usr/local/src,
command = /usr/bin/wget -q $download,
timeout = 120,
unless = test -f $creates,
}
# here I always get an error
exec { extract-$name:
cwd = /usr/local/src,
command = $extractor /usr/local/src/$filename,
timeout = 120,
path= /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/
sbin:/bin,
require = Exec[download-$name],
}
exec { config-$name:
cwd = /usr/local/src/$foldername,
command = ./configure $buildoptions,
timeout = 120,
require = Exec[extract-$name],
}
exec { make-install-$name:
cwd = /usr/local/src/$foldername,
command = /usr/bin/make /usr/bin/make install,
timeout = 600,
require = Exec[config-$name],
}
# remove build folder
case $rm_build_folder {
true: {
notice(remove build folder)
exec { remove-$name-build-folder:
command = /usr/bin/rm -rf /usr/local/src/$foldername,
require = Exec[make-install-$name],
} # exec
} # true
} # case
}
The code runs on a nexenta ncp 3.0 (SunOS) box. Any ideas?
Thanks
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Convert string to int?
If I have...
$version_core = t.1538-1
$is_trunk_release = regsubst($version_core, '^(.*?)\.(.*?)$', '\1')
if $is_trunk_release == t {
notice (here 1)
if $t = 1583 {
notice (here 2)
}
}
Puppet complains with:
comparison of String with 1583 failed at
/etc/puppet/modules/elements/manifests/init.pp:220 on node
app09.fr.xxx.com
However, the documentation says you can do:
if $ram 1024 {
$maxclient = 500
}
So, therefore how can I convert $is_trunk_release to an integer
so I can do a numerical comparison against it?
Doug.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Convert string to int?
On Tue, Sep 14, 2010 at 12:12 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
If I have...
$version_core = t.1538-1
$is_trunk_release = regsubst($version_core, '^(.*?)\.(.*?)$', '\1')
if $is_trunk_release == t {
notice (here 1)
if $t = 1583 {
notice (here 2)
}
}
Puppet complains with:
comparison of String with 1583 failed at
/etc/puppet/modules/elements/manifests/init.pp:220 on node
app09.fr.xxx.com
However, the documentation says you can do:
if $ram 1024 {
$maxclient = 500
}
So, therefore how can I convert $is_trunk_release to an integer
so I can do a numerical comparison against it?
Doug.
Tried this:
$is_trunk_release = regsubst($version_core, '^(.*?)\.(.*?)$', '\1')
if $is_trunk_release == t {
$trunk_release = regsubst($version_core, '^(.*?)\.(.*?)$', '\2')
if (versioncmp($trunk_release, 1583) = 0 {
notice (Trunk release 1583)
}
}
}
This gives the same error.
Doug.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Convert string to int?
On Tue, Sep 14, 2010 at 12:12 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
If I have...
$version_core = t.1538-1
$is_trunk_release = regsubst($version_core, '^(.*?)\.(.*?)$', '\1')
if $is_trunk_release == t {
notice (here 1)
if $t = 1583 {
notice (here 2)
}
}
Puppet complains with:
comparison of String with 1583 failed at
/etc/puppet/modules/elements/manifests/init.pp:220 on node
app09.fr.xxx.com
However, the documentation says you can do:
if $ram 1024 {
$maxclient = 500
}
You can.
So, therefore how can I convert $is_trunk_release to an integer
so I can do a numerical comparison against it?
Where are you defining $t ? I don't see it there.
$version_core = t.1538-1
$is_trunk_release = regsubst($version_core, '^(.*?)\.(.*?)$', '\1')
if $is_trunk_release == t {
notice (here 1)
notice(t is [$t]) # -
if $t = 1583 {
notice (here 2)
}
}
nigelk$ puppet --factpath /tmp/foo /tmp/test.pp
notice: Scope(Class[main]): here 1
notice: Scope(Class[main]): t is []
comparison of String with 1583 failed at /tmp/test.pp:7 on node
dhcp-172-19-29-14.mtv.corp.google.com
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Custom provider
Yes, this does the trick. Thanks!
Erik
On Sep 13, 12:55 pm, Stefan Schulte stefan.schu...@taunusstein.net
wrote:
Put your provider in /etc/puppet/modules/mymodule/lib/
puppet/provider/package/myprovider.rb
Notice the provider/TYPE subfolder
Hope this does the trick
-Stefan
On Mon, Sep 13, 2010 at 07:52:48AM -0700, SiD wrote:
Hi all,
I've recently created a new custom provider. I put it into /etc/puppet/
modules/mymodule/lib/puppet/provider/myprovider.rb
So it works fine, at least at the first.
puppet-agent[8329]: (/File[/var/lib/puppet/lib/puppet]/ensure) created
puppet-agent[8329]: (/File[/var/lib/puppet/lib/puppet/provider]/
ensure) created
puppet-agent[8329]: (/File[/var/lib/puppet/lib/puppet/provider/
myprovider.rb]/ensure) defined content as '{md5}
13be544b81b7e77abfec081b912c4b1f'
Then, everytime when Puppet reload the configuration, Puppet can not
find my custom provider anymore :
puppet-agent[11205]: Could not run Puppet configuration client:
Parameter provider failed: Invalid package provider 'myprovider' at /
etc/puppet/modules/mymodule/manifests/init.pp:10
Line number 10, it's the call to my custom provider :
package {
mymodule:
ensure = installed,
provider = myprovider,
source = /home/mymodule.rpm,
vendor = --prefix=/myprefix;
}
$ rpm -aq | grep puppet
puppet-2.6.1-0.3.rc3.el5
I've also tired with Puppet 2.6.0, but same trouble.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group
athttp://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Convert string to int?
On Tue, Sep 14, 2010 at 12:19 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
On Tue, Sep 14, 2010 at 12:12 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
If I have...
$version_core = t.1538-1
$is_trunk_release = regsubst($version_core, '^(.*?)\.(.*?)$', '\1')
if $is_trunk_release == t {
notice (here 1)
if $t = 1583 {
notice (here 2)
}
}
Puppet complains with:
comparison of String with 1583 failed at
/etc/puppet/modules/elements/manifests/init.pp:220 on node
app09.fr.xxx.com
However, the documentation says you can do:
if $ram 1024 {
$maxclient = 500
}
So, therefore how can I convert $is_trunk_release to an integer
so I can do a numerical comparison against it?
Doug.
Tried this:
$is_trunk_release = regsubst($version_core, '^(.*?)\.(.*?)$', '\1')
if $is_trunk_release == t {
$trunk_release = regsubst($version_core, '^(.*?)\.(.*?)$', '\2')
if (versioncmp($trunk_release, 1583) = 0 {
notice (Trunk release 1583)
}
}
}
This gives the same error.
That doesn't even parse for me.
Doug.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
nigel
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Tagging / Exported Resources
Hello All,
I've been battling with issue all day to no avail. I'm exporting
all host entries this way:
class basics::host_export { @@host{ $fqdn:
ip = $ipaddress,
host_aliases = $hostname,
tag = $group
}}
and I'm collecting them this way:
class basics::host_collect { Host |tag==$group | }
The values for $group is obviously defined. The thing is that
specifying the tag=$group doesn't work for me, I always get (from
debug mode):
debug: Scope(Class[basics::basics::host_collect]): Collected 0 Host
resources in 0.01 seconds..
It doesn't collect any nodes even though I've defined a couple. If I
do the same thing without the tag definition, it works fine; i.e:
class basics::host_export { @@host{ $fqdn:
ip = $ipaddress,
host_aliases = $hostname
}}
class basics::host_collect { Host | | }
The thing is that I don't want to get all hosts, I want to filter per
group. Can anyone share how they're doing this? Thanks,
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] GitHub Account move - the Great Migration continues...
Hi all Many of you know we renamed ourselves from Reductive Labs to Puppet Labs. We've slowly been removing the remnants of the old company name from various places. As part of this exercise we're also migrating our GitHub accounts. We've set-up a new puppetlabs GitHub account and forked all our old repositories to this account. This means if you clone or fork our Puppet and other repositories you will need to update their addresses. For example the Puppet respository that would have been cloned like: $ git clone git://github.com/reductivelabs/puppet.git Should now be cloned like: $ git clone git://github.com/puppetlabs/puppet.git It is important you do this because the Puppet Labs reductivelabs account will be decommissioned and those repositories removed in the future. This applies to projects including: Puppet Facter Puppet Dashboard Naginator and others. You can see the full list of repositories and their new addresses at: http://github.com/puppetlabs If you have any questions or concerns please don't hesitate to contact me. Regards James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Tagging / Exported Resources
btw: I'm running puppet 0.25.5
On Sep 14, 3:53 pm, CraftyTech hmmed...@gmail.com wrote:
Hello All,
I've been battling with issue all day to no avail. I'm exporting
all host entries this way:
class basics::host_export { @@host{ $fqdn:
ip = $ipaddress,
host_aliases = $hostname,
tag = $group
}}
and I'm collecting them this way:
class basics::host_collect { Host |tag==$group | }
The values for $group is obviously defined. The thing is that
specifying the tag=$group doesn't work for me, I always get (from
debug mode):
debug: Scope(Class[basics::basics::host_collect]): Collected 0 Host
resources in 0.01 seconds..
It doesn't collect any nodes even though I've defined a couple. If I
do the same thing without the tag definition, it works fine; i.e:
class basics::host_export { @@host{ $fqdn:
ip = $ipaddress,
host_aliases = $hostname
}}
class basics::host_collect { Host | | }
The thing is that I don't want to get all hosts, I want to filter per
group. Can anyone share how they're doing this? Thanks,
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Run Frequency
This is weird. I'm noticing that with 2.6rcx that puppet isn't running on the nodes every 30 minutes. In fact, not even every few hours. Was the default changed to some huge value in 2.6? I don't see errors in the logs... I don't even see puppet starting a run. Doug -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Specifying version for shared packages
I've been banging my head on this all day, and I cannot seem to figure
out how to do it.
I have a package for Apache HTTPd. I want to be able to specify the
exact version of the package to use for a particular installation. And
it is also possible that I want to have two separate modules install the
same package.
So, what I end up with is the following
class app-apache {
package { apache : ensure = installed, noop = true }
}
class app-apache-server1 inherits app-apache {
Package[apache] {ensure = 2.2.15, noop = false}
}
class app-apache-server2 inherits app-apache {
Package[apache] {ensure = 2.2.15, noop = false}
}
Basically, I have two servers configured. Now, it is possible that both
servers could end up on the same host, depending upon a number of
facters. When that happens, I get an error about not being able to
override the ensure method in app-apache-server2 because it was
already overridden in app-apache-server1.
Anyone have any ideas on how to do this? I need to be able to specify
the version I want for a particular class, and that can change from
class to class. I realize that if two different classes define two
different versions and both classes end up on the same node, I will get
errors from YUM. I'm ok with that.
Marc Zampetti
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Small bug: puppet.spec still refers to 2.6.0
Minor buglet: the *.spec file for linux needs to be updated for 2.6.1. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Run Frequency
On Tue, Sep 14, 2010 at 1:11 PM, Douglas Garstang doug.garst...@gmail.com wrote: This is weird. I'm noticing that with 2.6rcx that puppet isn't running on the nodes every 30 minutes. In fact, not even every few hours. Was the default changed to some huge value in 2.6? I don't see errors in the logs... I don't even see puppet starting a run. Doug Oh, I know what it is. In puppet 0.24.8, 0.25.5, it would display Starting catalog run when it was doing a periodic run. In 2.6rc(whatever), it DOES NOT display this message, or any like it, when doing a catalog run. All you see is the 'Finished' message. Good grief. Anyone know if there is a bug opened on this, and if maybe it's fixed in 2.6? Doug. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Specifying version for shared packages
On 14.09.2010 23:12, Marc Zampetti wrote:
I've been banging my head on this all day, and I cannot seem to
figure out how to do it.
I have a package for Apache HTTPd. I want to be able to specify the
exact version of the package to use for a particular installation. And
it is also possible that I want to have two separate modules install
the same package.
So, what I end up with is the following
class app-apache {
package { apache : ensure = installed, noop = true }
}
class app-apache-server1 inherits app-apache {
Package[apache] {ensure = 2.2.15, noop = false}
}
class app-apache-server2 inherits app-apache {
Package[apache] {ensure = 2.2.15, noop = false}
}
Basically, I have two servers configured. Now, it is possible that
both servers could end up on the same host, depending upon a number of
facters. When that happens, I get an error about not being able to
override the ensure method in app-apache-server2 because it was
already overridden in app-apache-server1.
Anyone have any ideas on how to do this? I need to be able to specify
the version I want for a particular class, and that can change from
class to class. I realize that if two different classes define two
different versions and both classes end up on the same node, I will
get errors from YUM. I'm ok with that.
Marc Zampetti
I don't see any way to do what you want directly. But in your specific
case you may add another level of inheritance, that specifies the
version, and inherit both of your classes from that, and you will get an
error from puppet for double override in that case. You shouldn't feed
much into yum as you might get an actual response in package management...
As an alternative you may get the version from a variable for the
specified class, but this would leave you with somewhat of a nightmare
for double inclusion.
Leaving that aside what are you trying to do? What you are doing doesn't
seem right to me. Any code that uses copy/paste should be refactored to
call that common piece of code instead of the programmer/admin doing a
copy paste of that code.
Silviu
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Strange exec issue with tar
Check you environment path variable. Tar might not find something,
most probably, the gzip executable (not 100% sure on this part). Usually
if something doesn't work in specific cases, but it works in you bash
console, you can make a safe bet on environment variables and/or running
user.
Silviu
On 14.09.2010 21:35, jerry wrote:
I do have a really strange issue with exec a tar command with puppet
2.6.0. If I run it with puppetmasterd I get the following error
message:
(//my.domain.net//Stage[main]/Workerzone/Build::Install[top]/
Exec[extract-top]/returns) change from notrun to 0 failed: /bin/bash -
c '/usr/sbin/tar -xzvf /usr/local/src/top-3.7.tar.gz' returned 1
instead of one of [0] at /etc/puppet/modules/build/manifests/init.pp:
58
If I run the code manually with 'puppetd -t --debug' there are no
errors. What am I doing wrong? Here is my code:
# build::install { 'top':
# download = 'http://www.unixtop.org/dist/top-3.7.tar.gz',
# creates = '/url/local/bin/top',
# }
define build::install ($download, $creates, $pkg_folder='',
$pkg_format=tar, $pkg_extension=, $buildoptions=,
$rm_build_folder=true) {
if defined( Package['build-essential'] ) {
debug(build-essential already installed)
} else {
package { 'build-essential': ensure = installed }
}
$filename = basename($download)
$extension = $pkg_format ? {
zip = .zip,
tar = .tar.gz,
bzip= .tar.bz2,
default = $pkg_extension,
}
$foldername = $pkg_folder ? {
'' = gsub($filename, $extension, ),
default = $pkg_folder,
}
$extractor = $pkg_format ? {
zip = /usr/bin/unzip -q -d /usr/local/src,
bzip= /usr/sbin/tar -xjf,
default = /usr/sbin/tar -xzf ,
}
# download is fine
exec { download-$name:
cwd = /usr/local/src,
command = /usr/bin/wget -q $download,
timeout = 120,
unless = test -f $creates,
}
# here I always get an error
exec { extract-$name:
cwd = /usr/local/src,
command = $extractor /usr/local/src/$filename,
timeout = 120,
path= /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/
sbin:/bin,
require = Exec[download-$name],
}
exec { config-$name:
cwd = /usr/local/src/$foldername,
command = ./configure $buildoptions,
timeout = 120,
require = Exec[extract-$name],
}
exec { make-install-$name:
cwd = /usr/local/src/$foldername,
command = /usr/bin/make /usr/bin/make install,
timeout = 600,
require = Exec[config-$name],
}
# remove build folder
case $rm_build_folder {
true: {
notice(remove build folder)
exec { remove-$name-build-folder:
command = /usr/bin/rm -rf /usr/local/src/$foldername,
require = Exec[make-install-$name],
} # exec
} # true
} # case
}
The code runs on a nexenta ncp 3.0 (SunOS) box. Any ideas?
Thanks
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Specifying version for shared packages
Basically, I'm trying to build modules that implement best practices
(the app-apache module), and then admins that need to build specific
apache instances just create a new module that inherits from the base
class and provides the information they need.
So, admin A wants to build apache server 1, and thus creates
app-apache-server1. They set the version of apache they need, any other
required information (like docroot, etc.), and add anything else
specific to that application.
Admin B wants to build apache server 2, and thus creates
app-apache-server2. They go through the same process as admin A.
Notice, there are no nodes in this discussion. Its all about defining an
application. Then its time to say which nodes that apps will run on. In
this case, I want a single node to run both apps. Whenever I try to do
that with Puppet, I keep getting duplicate errors related to the package.
All of this assumes that the appropriate coordination has occurred to
make sure that both app definitions. That means that they are both
trying to use the same version of the package, don't conflict with files
or ports, etc.
Also, I think I forgot to mention that I am using puppet 0.25.5.
Marc
On 9/14/10 4:39 PM, Silviu Paragina wrote:
On 14.09.2010 23:12, Marc Zampetti wrote:
I've been banging my head on this all day, and I cannot seem to
figure out how to do it.
I have a package for Apache HTTPd. I want to be able to specify the
exact version of the package to use for a particular installation.
And it is also possible that I want to have two separate modules
install the same package.
So, what I end up with is the following
class app-apache {
package { apache : ensure = installed, noop = true }
}
class app-apache-server1 inherits app-apache {
Package[apache] {ensure = 2.2.15, noop = false}
}
class app-apache-server2 inherits app-apache {
Package[apache] {ensure = 2.2.15, noop = false}
}
Basically, I have two servers configured. Now, it is possible that
both servers could end up on the same host, depending upon a number
of facters. When that happens, I get an error about not being able to
override the ensure method in app-apache-server2 because it was
already overridden in app-apache-server1.
Anyone have any ideas on how to do this? I need to be able to specify
the version I want for a particular class, and that can change from
class to class. I realize that if two different classes define two
different versions and both classes end up on the same node, I will
get errors from YUM. I'm ok with that.
Marc Zampetti
I don't see any way to do what you want directly. But in your
specific case you may add another level of inheritance, that specifies
the version, and inherit both of your classes from that, and you will
get an error from puppet for double override in that case. You
shouldn't feed much into yum as you might get an actual response in
package management...
As an alternative you may get the version from a variable for the
specified class, but this would leave you with somewhat of a nightmare
for double inclusion.
Leaving that aside what are you trying to do? What you are doing
doesn't seem right to me. Any code that uses copy/paste should be
refactored to call that common piece of code instead of the
programmer/admin doing a copy paste of that code.
Silviu
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Setup 2.6 + apache, passenger
On Tue, Sep 14, 2010 at 11:53 AM, M C maem...@gmail.com wrote: Restarting the puppet master with the certdnsname option set did not change the certificate in /var/lib/puppet/ssl/certs/admin.baz.bar.com at all. My understanding from the documentation is that the issue was with ca.pem. If that's the case, the options I provided wasn't addressing the right certificate. Is that not the case? Is there some trick to get puppet to regenerate the certs properly? From what I've been able to find, this seems to be at least partially related to Bug #4226. If the problem is related to 4226, you just need to specify ca_name option when running puppetmaster for the first time. Once the ca.pem file is created it won't replace it: puppetmasterd -v --ca_name=Puppet CA puppet.bar.com Issuer: CN=Puppet CA puppet.bar.com ... X509v3 Key Usage: Certificate Sign, CRL Sign I would backup the ssl directory first. Thanks, Nan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Specifying version for shared packages
On Tue, Sep 14, 2010 at 1:12 PM, Marc Zampetti marc.zampe...@gmail.com wrote:
I've been banging my head on this all day, and I cannot seem to figure out
how to do it.
I have a package for Apache HTTPd. I want to be able to specify the exact
version of the package to use for a particular installation. And it is also
possible that I want to have two separate modules install the same package.
So, what I end up with is the following
class app-apache {
package { apache : ensure = installed, noop = true }
}
class app-apache-server1 inherits app-apache {
Package[apache] {ensure = 2.2.15, noop = false}
}
class app-apache-server2 inherits app-apache {
Package[apache] {ensure = 2.2.15, noop = false}
}
Basically, I have two servers configured. Now, it is possible that both
servers could end up on the same host, depending upon a number of facters.
When that happens, I get an error about not being able to override the
ensure method in app-apache-server2 because it was already overridden in
app-apache-server1.
Anyone have any ideas on how to do this? I need to be able to specify the
version I want for a particular class, and that can change from class to
class. I realize that if two different classes define two different versions
and both classes end up on the same node, I will get errors from YUM. I'm ok
with that.
Marc Zampetti
Marc,
We're doing what your trying to. We'd be screwed without the ability
to specify a package version. We do:
package foo {
ensure = 1.21-10-1
}
Works fine...
Doug.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Specifying version for shared packages
On Tue, Sep 14, 2010 at 2:36 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
On Tue, Sep 14, 2010 at 1:12 PM, Marc Zampetti marc.zampe...@gmail.com
wrote:
I've been banging my head on this all day, and I cannot seem to figure out
how to do it.
I have a package for Apache HTTPd. I want to be able to specify the exact
version of the package to use for a particular installation. And it is also
possible that I want to have two separate modules install the same package.
So, what I end up with is the following
class app-apache {
package { apache : ensure = installed, noop = true }
}
class app-apache-server1 inherits app-apache {
Package[apache] {ensure = 2.2.15, noop = false}
}
class app-apache-server2 inherits app-apache {
Package[apache] {ensure = 2.2.15, noop = false}
}
Basically, I have two servers configured. Now, it is possible that both
servers could end up on the same host, depending upon a number of facters.
When that happens, I get an error about not being able to override the
ensure method in app-apache-server2 because it was already overridden in
app-apache-server1.
Anyone have any ideas on how to do this? I need to be able to specify the
version I want for a particular class, and that can change from class to
class. I realize that if two different classes define two different versions
and both classes end up on the same node, I will get errors from YUM. I'm ok
with that.
Marc Zampetti
Marc,
We're doing what your trying to. We'd be screwed without the ability
to specify a package version. We do:
package foo {
ensure = 1.21-10-1
}
Works fine...
Doug.
Sorry... really bad example. Lets do it right this time...
package {
foo:
ensure = 1.21.10-1;
}
Doug
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Specifying version for shared packages
Skipping the practices part, you can achieve the final objective by
adding another level of inheritance (apache-app-ver-2) and the two
classes in the end would inherit from, or include, this new class.
Logically if there is any reason for apache having the same version in
both application 1 and 2, that reason with it's specific configuration
should go in a common manifest. Your logic for naming the intermediary
class should then become apache-app-reason. If there is no reason I
don't see why you aren't using latest/installed, with or without a
private repository.
IMHO in puppet you should specify what an application needs, not
everything down to the version, or at least set the version somewhere
common to all the classes that need to use it. Think of it this way, if
you get to have 1000 applications, and need to upgrade apache because of
a security flaw you will have to edit that in 1000 places, instead of a
single class or using latest.
A case where this shouldn't apply is virtual boxes, where there is only
one function for the machine, and you might want the version of every
software you use to be fixed.
For how it would be ideal to do it, I'm not sure, I'm waiting for
comments too. :)
Silviu
On 14.09.2010 23:55, Marc Zampetti wrote:
Basically, I'm trying to build modules that implement best practices
(the app-apache module), and then admins that need to build specific
apache instances just create a new module that inherits from the base
class and provides the information they need.
So, admin A wants to build apache server 1, and thus creates
app-apache-server1. They set the version of apache they need, any
other required information (like docroot, etc.), and add anything else
specific to that application.
Admin B wants to build apache server 2, and thus creates
app-apache-server2. They go through the same process as admin A.
Notice, there are no nodes in this discussion. Its all about defining
an application. Then its time to say which nodes that apps will run
on. In this case, I want a single node to run both apps. Whenever I
try to do that with Puppet, I keep getting duplicate errors related to
the package.
All of this assumes that the appropriate coordination has occurred to
make sure that both app definitions. That means that they are both
trying to use the same version of the package, don't conflict with
files or ports, etc.
Also, I think I forgot to mention that I am using puppet 0.25.5.
Marc
On 9/14/10 4:39 PM, Silviu Paragina wrote:
On 14.09.2010 23:12, Marc Zampetti wrote:
I've been banging my head on this all day, and I cannot seem to
figure out how to do it.
I have a package for Apache HTTPd. I want to be able to specify the
exact version of the package to use for a particular installation.
And it is also possible that I want to have two separate modules
install the same package.
So, what I end up with is the following
class app-apache {
package { apache : ensure = installed, noop = true }
}
class app-apache-server1 inherits app-apache {
Package[apache] {ensure = 2.2.15, noop = false}
}
class app-apache-server2 inherits app-apache {
Package[apache] {ensure = 2.2.15, noop = false}
}
Basically, I have two servers configured. Now, it is possible that
both servers could end up on the same host, depending upon a number
of facters. When that happens, I get an error about not being able
to override the ensure method in app-apache-server2 because it was
already overridden in app-apache-server1.
Anyone have any ideas on how to do this? I need to be able to
specify the version I want for a particular class, and that can
change from class to class. I realize that if two different classes
define two different versions and both classes end up on the same
node, I will get errors from YUM. I'm ok with that.
Marc Zampetti
I don't see any way to do what you want directly. But in your
specific case you may add another level of inheritance, that
specifies the version, and inherit both of your classes from that,
and you will get an error from puppet for double override in that
case. You shouldn't feed much into yum as you might get an actual
response in package management...
As an alternative you may get the version from a variable for the
specified class, but this would leave you with somewhat of a
nightmare for double inclusion.
Leaving that aside what are you trying to do? What you are doing
doesn't seem right to me. Any code that uses copy/paste should be
refactored to call that common piece of code instead of the
programmer/admin doing a copy paste of that code.
Silviu
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
Re: [Puppet Users] Small bug: puppet.spec still refers to 2.6.0
On Tue, Sep 14, 2010 at 3:34 PM, Nigel Kersten nig...@google.com wrote: On Tue, Sep 14, 2010 at 3:28 PM, Douglas Garstang doug.garst...@gmail.com wrote: On Tue, Sep 14, 2010 at 3:03 PM, James Turnbull ja...@puppetlabs.com wrote: Forrie wrote: Minor buglet: the *.spec file for linux needs to be updated for 2.6.1. This is usually done by the packagers at some point. We only maintain these specs for convenience. It seems like an inconvenience in it's correct form. I agree with you. I quite strongly feel that the puppet source shouldn't include the packaging stuff, but instead have a readme of some kind that links to all the package maintenance websites/repos/whatever. I agree with you there. If the puppet people aren't going to do it correctly, they're better off not doing it at all. Lets play rock paper scissors to see who files a bug... Rock... Doug -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Small bug: puppet.spec still refers to 2.6.0
On Tue, Sep 14, 2010 at 3:51 PM, Douglas Garstang doug.garst...@gmail.com wrote: On Tue, Sep 14, 2010 at 3:34 PM, Nigel Kersten nig...@google.com wrote: On Tue, Sep 14, 2010 at 3:28 PM, Douglas Garstang doug.garst...@gmail.com wrote: On Tue, Sep 14, 2010 at 3:03 PM, James Turnbull ja...@puppetlabs.com wrote: Forrie wrote: Minor buglet: the *.spec file for linux needs to be updated for 2.6.1. This is usually done by the packagers at some point. We only maintain these specs for convenience. It seems like an inconvenience in it's correct form. I agree with you. I quite strongly feel that the puppet source shouldn't include the packaging stuff, but instead have a readme of some kind that links to all the package maintenance websites/repos/whatever. I agree with you there. If the puppet people aren't going to do it correctly, they're better off not doing it at all. Lets play rock paper scissors to see who files a bug... That's uncharitable and unfair. The package maintainers are responsible for their packages. The spec file was in the upstream source as a convenience to make it easier for people to rebuild packages themselves, but the maintainers are still responsible for the package and spec files. This is pretty standard open source ecosystem stuff. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] ANNOUNCE: Puppet Dashboard 1.0.4 Release Candidate 1!
We're pleased to announce the availability of Puppet Dashboard 1.0.4rc1! The 1.0.4 release is a maintenance release, it fixes a number of bugs and significantly improves performance. Please try this release candidate and let us know about any issues on the mailing list (http://groups.google.com/group/puppet-users/), or in the ticket tracker with an Affected Version of 1.0.4 (http://projects.puppetlabs.com/projects/dashboard/). If you're interested in what we're hoping to work on next, please see our roadmap and watch or comment on those tickets that are important to you: http://projects.puppetlabs.com/projects/dashboard/roadmap GET THE SOURCE: You can download the release candidate from: http://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.0.4rc1.tgz Or check it out using git: git clone git://github.com/puppetlabs/puppet-dashboard.git \ cd puppet-dashboard \ git checkout v1.0.4rc1 At this time there are no operating system packages available for the release candidate. INSTALLING AND UPGRADING: New installation and upgrading instructions for use with Puppet versions 0.25.x and 2.6.x are available in the included README, which you can also read online at: http://github.com/puppetlabs/puppet-dashboard/blob/v1.0.4rc1/README.markdown IMPORTANT: This release involves database migrations. Please see the README.markdown for instructions on applying them. RELEASE NOTES: v1.0.4rc1 - * MIGRATION: Fixed truncation of long reports and deleted these invalid records. Please reimport your reports (see README) after migrating to readd these deleted reports. * MIGRATION: Fixed slow database queries on the home page, reports listing page, and site-wide sidebar. * MIGRATION: Fixed orphaned records left behind when classes or groups were deleted, and removed these orphans from the database. * MIGRATION: Fixed duplicate membership records by removing them and preventing new ones from being added, e.g. a node belongs to the same class or group multiple times. * Fixed user interface for specifying classes and groups to work with standards-compliant browsers, autocomplete on keystroke rather than submitting, etc. * Fixed default node search, it was incorrectly using the ever failed node query rather than the all nodes query. * Fixed run-failure chart to correctly count the reports by day. * Fixed run-time chart to correctly display its unit-of-measure labels as seconds, not milliseconds. * Fixed report display and sorting to use the time the report was created by a client, rather than the time it was imported. * Fixed class validations to accept valid Puppet class names, including those with correctly-placed dashes, double-colons and numbers. * Fixed cycle exception caused when a node belonged to two or more groups that inherited a single, common group. * Fixed parameter inheritance so that a node belonging to a group can see the parameters it inherited from its groups' ancestors. * Fixed parameter collision to display errors if the same parameter was defined differently by groups at the same level of inheritance (e.g. both parents). * Fixed class edit form to use new-style form that can display error messages. * Fixed node to recalculate its latest report if the current report record was deleted. * Fixed external node classifier to return a special result when asked for an unknown node so that Puppet can classify it. * Fixed node, class, and group listing pages to describe the current search and non-matches correctly. * Fixed documentation for adding the EPEL repository on CentOS and RHEL hosts. * Fixed documentation to use sh-compatible commands and explain that this is the expected shell for commands. * Fixed exceptions on the node's create and edit forms if the user submitted the form with a blank name. * Fixed release notes styling to properly indent bullet points. * Improved node classification to display useful error messages when there's a problem. * Improved page headings to display the type of resource shown, e.g. Node: mynodename.net * Improved graph legends to more prominently show their intervals. * Added documentation describing how to upgrade to a new Puppet Dashboard release. * Added documentation describing how to set the Puppet Dashboard's filesystem ownership and permissions. * Added documentation describing how to prune old reports and fixed the script for pruning these to use the time the report was created rather than imported. * Added documentation describing how to locate error logs to help debug and report problems. Regards James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Tagging / Exported Resources
Has anyone used this feature?
On Sep 14, 4:08 pm, CraftyTech hmmed...@gmail.com wrote:
btw: I'm running puppet 0.25.5
On Sep 14, 3:53 pm, CraftyTech hmmed...@gmail.com wrote:
Hello All,
I've been battling with issue all day to no avail. I'm exporting
all host entries this way:
class basics::host_export { @@host{ $fqdn:
ip = $ipaddress,
host_aliases = $hostname,
tag = $group
}}
and I'm collecting them this way:
class basics::host_collect { Host |tag==$group | }
The values for $group is obviously defined. The thing is that
specifying the tag=$group doesn't work for me, I always get (from
debug mode):
debug: Scope(Class[basics::basics::host_collect]): Collected 0 Host
resources in 0.01 seconds..
It doesn't collect any nodes even though I've defined a couple. If I
do the same thing without the tag definition, it works fine; i.e:
class basics::host_export { @@host{ $fqdn:
ip = $ipaddress,
host_aliases = $hostname
}}
class basics::host_collect { Host | | }
The thing is that I don't want to get all hosts, I want to filter per
group. Can anyone share how they're doing this? Thanks,
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Strange exec issue with tar
Thanks for your tip! Path is set early in base inheritance class to:
Exec { path = /usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/
sbin:/sbin }
But even if I set this path env var in the exec block it fails:
# here I always get an error
exec { extract-$name:
cwd = /usr/local/src,
command = $extractor /usr/local/src/$filename,
timeout = 120,
path= /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/
sbin:/bin,
require = Exec[download-$name],
}
Adding:
loglevel = verbose,
logoutput = true,
Doesn´t give any additional output. I´m a little loss with it...
On 14 Sep., 22:45, Silviu Paragina sil...@paragina.ro wrote:
Check you environment path variable. Tar might not find something,
most probably, the gzip executable (not 100% sure on this part). Usually
if something doesn't work in specific cases, but it works in you bash
console, you can make a safe bet on environment variables and/or running
user.
Silviu
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
