Re: [Puppet Users] Could not run Puppet configuration client: SIGQUIT
Hi, If you try to restart the client during the update, won't that confuse puppet a bit? Dont subscribe puppet.conf to the service. I'm not sure whether puppet re-reads changes to it's config files before it does a run (I think it does), but I'm sure what you're trying to do won't work. Cheers On 24/03/2011, at 3:46, stefanero wrote: > Hello, > > I am farly new to puppet and wanted to start configure a couple of my > servers. > > I started to write a little test manifest and tryed to update the > puppet client configuration as a test. > > > This is my site.pp > - > #set fileserver to get files from > $fileserver = "puppet.hugoboss.com" > > #import different manifets / modules get loaded by default > import "puppetclient.pp" > > # all hosts get these actions > node default { >include puppetclient > } > - > > and this is the included puppetclient.pp > cat puppetclient.pp > > - > #create puppet directory for loggin etc, this is default for all > clients > #also copy our puppet config files first, when done restart service > and continoue > > class puppetclient { > >package { >facter: >ensure => installed; >puppet: >ensure => installed; >} > >file { >"/var/lib/puppet": >ensure => directory, >owner => "puppet", >group => "puppet", >mode => 0644; >"puppet.conf": >owner => "root", >path => "/etc/puppet/puppet.conf", >source => "puppet://$fileserver/files/puppet-agent.conf"; >"auth.conf": >owner => "root", >path => "/etc/puppet/auth.conf", >source => "puppet://$fileserver/files/auth-agent.conf"; >"namespaceauth.conf": >owner => "root", >path => "/etc/puppet/namespaceauth.conf", >source => "puppet://$fileserver/files/namespaceauth-agent.conf"; >} > >service { >puppet: >ensure => true, >enable => true, >subscribe => [File["puppet.conf"], File["auth.conf"], > File["namespaceauth.conf"], Package[puppet] ] >} > > } > > - > > As you can tell, I guess nothing special. > > All files get transfered to the client, but when I change a file for > example the puppet.conf I get in the syslog a msg > > Mar 23 17:35:26 test-box puppet-agent[32527]: Could not run Puppet > configuration client: SIGQUIT > > > Also the new configuration is not applied. I changed the "runinterval" > value from 180 sec to 20 sec, but still only every 30min I see a > connect. > This only works if I manually do a > > /etc/init.d/puppet restart > > I am running a opensuse 11.3 x86 and build the RPM myself using the > puppet specfile present in the tarbal. > > Can anyone help me out what I am missing? > > Thank you very much > stefanero > > > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: puppet-dashboard 1.1.0rc1 - how to enable facts and inventory?
Also I have setup the auth.conf as well. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] puppet-dashboard 1.1.0rc1 - how to enable facts and inventory?
Hi, puppet-dashboard has been great for us, and I appreciate all the hard work from all the developers. I can't however seem to enable facts or inventory browsing. I have generated, signed and retrieved the certs as per the README. Not sure what else I need to do to get them to display (or where it would be)? I also could not find any relevant info in settings.yaml. Any help is appreciated. Thank you, Stan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Upgrade guide?
Hello; Sorry, I meant to say I downloaded the tarball, made the RPM using said tarball (using the redhat/puppet.spec) and moved teh RPM over to the copied puppetmaster server. So for all intents and purposes I am using the RPMs. On Mar 23, 3:58 pm, Adam Gibbins wrote: > On 23 March 2011 22:49, Michel wrote: > > > > > Hello; > > > Is there any documentation on how to perform a puppet upgrade? I > > download the tarball and extracted it to my copied puppetmaster > > server. Right now I have all the node definitions working, but any > > modules are not working. > > (not even a simply touch foo.txt exec command) > > > Some errors I am getting are related to tests > > > Parametr onlyif failed: 'test -f /etc/puppet/puppet.conf` is not a > > qualified and no path was specified. > > > We are upgrading from 2.5-1 to 2.6.6-1 > > Is there a reason you're extracting the tarball over using your > operating systems package management? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Upgrade guide?
On 23 March 2011 22:49, Michel wrote: > Hello; > > Is there any documentation on how to perform a puppet upgrade? I > download the tarball and extracted it to my copied puppetmaster > server. Right now I have all the node definitions working, but any > modules are not working. > (not even a simply touch foo.txt exec command) > > > Some errors I am getting are related to tests > > Parametr onlyif failed: 'test -f /etc/puppet/puppet.conf` is not a > qualified and no path was specified. > > We are upgrading from 2.5-1 to 2.6.6-1 > Is there a reason you're extracting the tarball over using your operating systems package management? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Upgrade guide?
Hello; Is there any documentation on how to perform a puppet upgrade? I download the tarball and extracted it to my copied puppetmaster server. Right now I have all the node definitions working, but any modules are not working. (not even a simply touch foo.txt exec command) Some errors I am getting are related to tests Parametr onlyif failed: 'test -f /etc/puppet/puppet.conf` is not a qualified and no path was specified. We are upgrading from 2.5-1 to 2.6.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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] WEBrick, Passenger or Mongrel
On Mar 23, 2011, at 8:25 AM, hyzhang wrote: > Hi, > > My organization is going to set up puppet soon. We have thousands > servers and desktops. Would WEBrick work well for this? Or should we > use Passenger? Just to make the issues clear, in my experience, depending on your manifests, Webrick will be able to serve from 2-25 clients well per hour, and how well it scales depends mostly on the speed of the slowest clients, and the slowest connections. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: WEBrick, Passenger or Mongrel
On 03/23/2011 06:00 PM, hyzhang wrote: Thanks everybody for the input. Thank you Charles for the information. We also use apache on CentOS 5.x. I find some documentation from the link below: https://github.com/puppetlabs/puppet/tree/master/ext/rack for Puppet 0.25.x and 2.6.x. But the above link does not seem very detailed. Do you also need to install rack? Is it sufficient just following the instructions from this link or is there a better documentation somewhere else? Thanks, -Haiyan On Mar 23, 5:20 pm, Charles Johnson wrote: We use puppet running with apache and passenger on CentOS 5.x. We manage about 700 boxes with no problems. Apache was the stock install using yum. We built ruby 1.8.7 patchlevel 334 from source. We built RubyGems from source, and installed the requisite gems. We built passenger from source, and followed the online documentation to get it running (piece of cake!). I can recommend this setup. ~Charles~ On Wed, Mar 23, 2011 at 10:25 AM, hyzhang wrote: Hi, My organization is going to set up puppet soon. We have thousands servers and desktops. Would WEBrick work well for this? Or should we use Passenger? Thanks, Haiyan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. Check http://projects.puppetlabs.com/projects/1/wiki/Using_Mongrel however I'm not sure how dated. There are passenger instructions near the bottom (or use Mongrel). -- Cody Robertson 1-800-859-8803 ext. 5 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: WEBrick, Passenger or Mongrel
Thanks everybody for the input. Thank you Charles for the information. We also use apache on CentOS 5.x. I find some documentation from the link below: https://github.com/puppetlabs/puppet/tree/master/ext/rack for Puppet 0.25.x and 2.6.x. But the above link does not seem very detailed. Do you also need to install rack? Is it sufficient just following the instructions from this link or is there a better documentation somewhere else? Thanks, -Haiyan On Mar 23, 5:20 pm, Charles Johnson wrote: > We use puppet running with apache and passenger on CentOS 5.x. We manage > about 700 boxes with no problems. > > Apache was the stock install using yum. > > We built ruby 1.8.7 patchlevel 334 from source. > > We built RubyGems from source, and installed the requisite gems. > > We built passenger from source, and followed the online documentation to get > it running (piece of cake!). > > I can recommend this setup. > > ~Charles~ > > On Wed, Mar 23, 2011 at 10:25 AM, hyzhang wrote: > > Hi, > > > My organization is going to set up puppet soon. We have thousands > > servers and desktops. Would WEBrick work well for this? Or should we > > use Passenger? > > > Thanks, > > Haiyan > > > -- > > You received this message because you are subscribed to the Google Groups > > "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users+unsubscr...@googlegroups.com. > > For more options, visit this group at > >http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Trying to set up per-environment manifest file
Got it! It looks like I still had a manifest specified in the [main] section of puppet.conf, AND via a PUPPETMASTER_MANIFEST declaration in the / etc/sysconfig/puppetmaster file which made it a little tricky to track down :) Once I removed those and let it fall back to the [environment] sections all was good. Thanks for the help. Cheers, -elliott- On Mar 22, 1:19 pm, Mohamed Lrhazi wrote: > I use this pattern: > > [master] > > templatedir = /etc/puppet/environments/$environment/ > modulepath = /etc/puppet/environments/$environment/modules > manifest = /etc/puppet/environments/$environment/manifests/site.pp > manifestdir = /etc/puppet/environments/$environment/manifests > > > > > > > > On Tue, Mar 22, 2011 at 3:52 PM, elliott wrote: > > Thanks Cody. > > > The client's environment does need to be set, either through the > > puppet.conf or on the command line, but the environments also need to > > be defined on the master, as far as I know. > > > On Mar 22, 12:46 pm, Cody Robertson wrote: > >> On 03/22/2011 03:41 PM, elliott wrote: > > >> > Hi guys, > > >> > I've had separate development/testing environments partially working > >> > for a while, in that modules get pulled from the correct per- > >> > environment path. However, something that has never seemed to work > >> > was a per-environment manifest. I have more need for this now so I'd > >> > like to track it down. > > >> > Here is the relevant part of my puppet.conf file: > > >> > [puppetmasterd] > >> > modulepath = /etc/puppet/modules:/usr/share/puppet:/var/lib/modules > >> > environments=production,testing,development > > >> > [production] > >> > manifest = /etc/puppet/manifests/site.pp > >> > modulepath = /etc/puppet/modules:/usr/share/puppet:/var/lib/modules > > >> > [testing] > >> > manifest = /etc/puppet/testing/manifests/site.pp > >> > modulepath = /etc/puppet/testing/modules:/etc/puppet/modules:/usr/ > >> > share/puppet:/var/lib/modules > > >> > [development] > >> > manifest = /etc/puppet/development/manifests/site.pp > >> > modulepath = /etc/puppet/development/modules:/etc/puppet/modules:/usr/ > >> > share/puppet:/var/lib/modules > > >> > I've added some notify's to each of the site.pp files mentioned, and > >> > sure enough it is always ending up in production. > > >> > Any clues? Anyone else have this working? > > >> > Thanks in advance! > > >> I don't personally use these however by glancing at the doc it appears > >> you specify the environment on the agent and not the master? > > >>http://projects.puppetlabs.com/projects/1/wiki/Using_Multiple_Environ... > > > -- > > You received this message because you are subscribed to the Google Groups > > "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users+unsubscr...@googlegroups.com. > > For more options, visit this group > > 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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Ruby DSL: create_resource with exec
On Wed, Mar 23, 2011 at 10:33 PM, Maxim Ivanov wrote: > Hi! How to create "exec" resource in ruby DSL? Found mention of > create_resource but had no luck in using it =( node 'default' do create_resource(:exec, "/bin/touch /tmp/f", :creates=>"/tmp/f") end or hostclass 'demo' do create_resource(:exec, "/bin/touch /tmp/f", :creates=>"/tmp/f") end and you can add the class via include demo in any regular puppet manifest. HTH, 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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] WEBrick, Passenger or Mongrel
We use puppet running with apache and passenger on CentOS 5.x. We manage about 700 boxes with no problems. Apache was the stock install using yum. We built ruby 1.8.7 patchlevel 334 from source. We built RubyGems from source, and installed the requisite gems. We built passenger from source, and followed the online documentation to get it running (piece of cake!). I can recommend this setup. ~Charles~ On Wed, Mar 23, 2011 at 10:25 AM, hyzhang wrote: > Hi, > > My organization is going to set up puppet soon. We have thousands > servers and desktops. Would WEBrick work well for this? Or should we > use Passenger? > > Thanks, > Haiyan > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] WEBrick, Passenger or Mongrel
On 03/23/2011 11:25 AM, hyzhang wrote: Hi, My organization is going to set up puppet soon. We have thousands servers and desktops. Would WEBrick work well for this? Or should we use Passenger? Thanks, Haiyan WEBrick will not work - look into Passenger or Mongrel setup with some frontend proxy like Nginx. -- Cody Robertson 1-800-859-8803 ext. 5 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] way of importing .pp file or some string that contain class definition in ruby dsl
Have a look at external node classifiers, I believe this is a more appropriate approach for what you are trying to accomplish: http://docs.puppetlabs.com/guides/external_nodes.html On Wed, Mar 23, 2011 at 7:47 AM, junaid_malik wrote: > I'm finding the way to import a file or a class stored in string in > ruby manifest. > > I have tried following code to parse the class having packages and > services. > > pp = Puppet::Parser::Parser.new("development") > pp.string = "class webhttpd{package { 'httpd': ensure => installed, } > service { 'httpd': ensure => running, enable => true, require => > Package['httpd'] } }" > pp.parse > > > pp = pp = Puppet::Parser::Parser.new("development") > pp.file = "web.pp" > pp.parse > > My idea is to re-use the classes written in the pp file style and they > are stored in database. I just want to load those classes depending on > 'FQDN' name of a node and then create a node in ruby like this. > > node name_of_the_node{ > create_resource :class, "httpd" > } > > I hope now you get what i'm trying to do in the ruby manifest. If its > still not clear then please ask me to explain more about what i want > to achieve from 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-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Could not run Puppet configuration client: SIGQUIT
Hello, I am farly new to puppet and wanted to start configure a couple of my servers. I started to write a little test manifest and tryed to update the puppet client configuration as a test. This is my site.pp - #set fileserver to get files from $fileserver = "puppet.hugoboss.com" #import different manifets / modules get loaded by default import "puppetclient.pp" # all hosts get these actions node default { include puppetclient } - and this is the included puppetclient.pp cat puppetclient.pp - #create puppet directory for loggin etc, this is default for all clients #also copy our puppet config files first, when done restart service and continoue class puppetclient { package { facter: ensure => installed; puppet: ensure => installed; } file { "/var/lib/puppet": ensure => directory, owner => "puppet", group => "puppet", mode => 0644; "puppet.conf": owner => "root", path => "/etc/puppet/puppet.conf", source => "puppet://$fileserver/files/puppet-agent.conf"; "auth.conf": owner => "root", path => "/etc/puppet/auth.conf", source => "puppet://$fileserver/files/auth-agent.conf"; "namespaceauth.conf": owner => "root", path => "/etc/puppet/namespaceauth.conf", source => "puppet://$fileserver/files/namespaceauth-agent.conf"; } service { puppet: ensure => true, enable => true, subscribe => [File["puppet.conf"], File["auth.conf"], File["namespaceauth.conf"], Package[puppet] ] } } - As you can tell, I guess nothing special. All files get transfered to the client, but when I change a file for example the puppet.conf I get in the syslog a msg Mar 23 17:35:26 test-box puppet-agent[32527]: Could not run Puppet configuration client: SIGQUIT Also the new configuration is not applied. I changed the "runinterval" value from 180 sec to 20 sec, but still only every 30min I see a connect. This only works if I manually do a /etc/init.d/puppet restart I am running a opensuse 11.3 x86 and build the RPM myself using the puppet specfile present in the tarbal. Can anyone help me out what I am missing? Thank you very much stefanero -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] WEBrick, Passenger or Mongrel
Hi, My organization is going to set up puppet soon. We have thousands servers and desktops. Would WEBrick work well for this? Or should we use Passenger? Thanks, Haiyan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] way of importing .pp file or some string that contain class definition in ruby dsl
I'm finding the way to import a file or a class stored in string in ruby manifest. I have tried following code to parse the class having packages and services. pp = Puppet::Parser::Parser.new("development") pp.string = "class webhttpd{package { 'httpd': ensure => installed, } service { 'httpd': ensure => running, enable => true, require => Package['httpd'] } }" pp.parse pp = pp = Puppet::Parser::Parser.new("development") pp.file = "web.pp" pp.parse My idea is to re-use the classes written in the pp file style and they are stored in database. I just want to load those classes depending on 'FQDN' name of a node and then create a node in ruby like this. node name_of_the_node{ create_resource :class, "httpd" } I hope now you get what i'm trying to do in the ruby manifest. If its still not clear then please ask me to explain more about what i want to achieve from 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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] gpg key errors
Tim Dunphy wrote: > I am having a strange occurrence where I can run puppet on a client > successfully and have it install httpd and php and a few other > packages. The first run everything goes ok and everything installs > perfectly the first run. But if I delete the packages (using yum > remove foo) and run puppet again I get gpg key errors and the packages > fail to install. > > ## puppet errors > > err: /Stage[main]/Apache/Package[php-mcrypt.i386]/ensure: change from > absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y > install php-mcrypt.i386' returned 1: warning: rpmts_HdrFromFdno: > Header V3 DSA signature: NOKEY, key ID cf4c4ff9 > > > Public key for php-mcrypt-5.2.17-1.1.w5.i386.rpm is not installed You need to install the GPG key for the repository that is providing those php packages. Alternately, you could disable gpg checks in the repo file for this repo, but that's not something I'd recommend. -- ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Learn from the mistakes of others--you can never live long enough to make them all yourself. -- John Luther pgp5pJgUSvgVg.pgp Description: PGP signature
[Puppet Users] Adding existing users to groups
Hi, I have an interesting problem with groups and users. Our puppet configuration is nice and modular so each application we wish to install has its own class. For some applications we want to add existing users, created in another class to a new group. Here's an example: class App1 { package { "App1" ... } user { "app1user" : ... } } class App2 { package { "app2" requires => Package["app1"] } group { "app2users" : ensure => present } user { name => "app1user" groups => "app2users" } } However puppet seems to balk doing this (even the first app) with: "Cannot alias User[app1inapp3] to app1user; resource User[app1user] already exist" Just to add some extra complexity we also need to have two apps that extend the first one, like so: class App3 { package { "app3" requires => Package["app1"] } group { "app3users" : ensure => present } user { "app1inapp3" name => "app1user" groups => "app3users" } } To get around this we have dumped everything in the app1user definition but this isn't very modular as machines that have no App2 or App3 end up with their user groups everywhere. Is there an alternative approach that I'm missing? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet Camp Announcements
Just in case you guys weren't aware, but your EU Puppet Camp is running very close to the Netherlands' Queensday and Queensnight: http://en.wikipedia.org/wiki/Koninginnedag Which is a rather busy party holiday. Not to mention that the same weekend is the UK's Royal Wedding, so there will be even more UK people over looking to dodge the havoc in London at that time and get inebriated (myself included). That might also be why hotels are being a little less accommodating, demand is high. If anyone is planning on leaving Amsterdam on the weekend then I would allocate more time to get to train stations and airports. While I've never been to Queensday, Dutch friends of mine say the city centre gets packed with street vendors and revellers. If you're staying the weekend though, pray for good weather and join the party! If you see me, please say hi, I'll be the one wearing orange ;) On Mar 23, 3:45 pm, Jose Palafox wrote: > > On the FAQ site you mention that you will try to get some "discounted rooms > > at a nearby hotel". > > > Do you already know if or when the group registration code will be > > available? > > Unfortunately hotels in the area don't seem too keen on giving us a > room block. However, I've been referring people to these two hotels > > http://www.nh-hotels.com/nh/en/hotels/the-netherlands/amsterdam/nh-ba...http://www.ibishotel.com/gb/home/index.shtml -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet Camp Announcements
> On the FAQ site you mention that you will try to get some "discounted rooms > at a nearby hotel". > > Do you already know if or when the group registration code will be available? > Unfortunately hotels in the area don't seem too keen on giving us a room block. However, I've been referring people to these two hotels http://www.nh-hotels.com/nh/en/hotels/the-netherlands/amsterdam/nh-barbizon-palace.html http://www.ibishotel.com/gb/home/index.shtml -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] gpg key errors
hello list I am having a strange occurrence where I can run puppet on a client successfully and have it install httpd and php and a few other packages. The first run everything goes ok and everything installs perfectly the first run. But if I delete the packages (using yum remove foo) and run puppet again I get gpg key errors and the packages fail to install. ## puppet errors err: /Stage[main]/Apache/Package[php-mcrypt.i386]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install php-mcrypt.i386' returned 1: warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID cf4c4ff9 Public key for php-mcrypt-5.2.17-1.1.w5.i386.rpm is not installed err: /Stage[main]/Apache/Package[php-pear.noarch]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install php-pear.noarch' returned 1: warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID cf4c4ff9 Public key for php-pear-1.9.2-1.w5.noarch.rpm is not installed err: /Stage[main]/Apache/Package[php-soap.i386]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install php-soap.i386' returned 1: warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID cf4c4ff9 Public key for php-soap-5.2.17-1.1.w5.i386.rpm is not installed err: /Stage[main]/Baseapps/Package[keychain]/ensure: change from absent to present failed: Could not find package keychain err: /Stage[main]/Apache/Package[php.i386]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install php.i386' returned 1: warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID cf4c4ff9 here is my apache class manifest class apache { $packagelist = ["httpd.$architecture","httpd-devel.$architecture","webalizer.$architecture","php.$architecture","php-common.$architecture","php-devel.$architecture","php-xmlrpc.$architecture","php-gd.$architecture", "php-pear.noarch", "php-pdo.$architecture", "php-mcrypt.$architecture", "php-mhash", "php-mysql.$architecture", "php-cli.$architecture", "php-soap.$architecture", "php-xml.$architecture"] package { $packagelist: ensure => "installed" } package { "mod_ssl.$architecture": require => Package["httpd.$architecture"], ensure => "installed" } exec { "create httpd dir" : command => "/bin/mkdir -p /etc/httpd" , creates => "/etc/httpd" ; "create apache module dir": command => "/bin/mkdir -p /usr/lib/httpd/modules" , creates => "/usr/lib/httpd/modules/mod_file_cache.so" ; "create apache module link" : command => "/bin/ln -s /usr/lib/httpd/modules /etc/httpd/modules" , require => Exec["create apache module dir"] , creates => "/etc/httpd/modules" ; "create apache log dir" : command => "/bin/mkdir -p /var/log/httpd/logs" , creates => "/var/log/httpd/logs" ; "create apache error log" : command => "/bin/touch /etc/httpd/logs/error_log" , require => Exec["create apache log dir"] , creates => "/etc/httpd/logs/error_log" ; "create apache log link" : command => "/bin/ln -s /var/log/httpd/logs /etc/httpd/logs" , require => Exec["create apache log dir"] , creates => "/etc/httpd/logs" ; "create apache run dir" : command => "/bin/mkdir -p /var/run/httpd" , creates => "/var/run/httpd" ; "create apache run link" : command => "/bin/ln -s /var/run/httpd /etc/httpd/run" , require => Exec["create apache log dir"] , creates => "/etc/httpd/run" ; "create httpd conf dir" : command => "/bin/mkdir -p /etc/httpd/conf" , creates => "/etc/httpd/conf" ; "create httpd vhost conf dir" : command => "/bin/mkdir -p /etc/httpd/conf.d" , creates => "/etc/httpd/conf.d" ; "create chrome docroot" : command => "/bin/mkdir -p /var/www/chrome/current" , creates => "/var/www/chrome/current" ; "create ssl cert dir" : command => "/bin/mmkdir -p /etc/pki/tls/certs/" , creates => "/etc/pki/tls/certs/" ; "create ssl key dir" : command => "/etc/pki/tls/private" , creates => "/etc/pki/tls/private" ; } tidy { "/etc/httpd/conf.d/ssl.conf" : age => '0s' , } file { "/etc/php.ini" : owner => root , group => root , mode => 440 , source => "puppet:///modules/apache/php.ini"
RE: [Puppet Users] Re: RFC: Splitting up the file{} type functionality.
jcbollinger: > On the other hand, perhaps the new thing needed is something > different: what about resource sub-types? [...] > plainfile { "/etc/profile.d/foo.sh": source => "..." } > filelink { "/etc/profile.d/foo.sh": target => "/opt/foo/foo_env.sh" } > service { "foo": require => File["/etc/profile.d/foo.sh"] } ... > it models the problem domain better This is an excellent idea. It breaks the exact correspondence between file/File, service/Service, etc., but that's easier to explain than symlinks and recursion (if not easier to implement). -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] RFC: Refactoring the mount provider.
Hi, I don't see the problems, really. > mount { '/mnt/foo': > device => '/dev/foo', > options => 'ro', > mount_state => mounted > fstab_state => present > } > > and lets also say that options is 'ro' in fstab but someone mounted the > device 'rw'. What should puppet report now? Needs remount. > Is the »options« property > insync now? There are two properties, fstab-options and mount-state options. The former is in sync. I'm not sure this is easily implemented in a puppet type/provider. > If not, what is its current value? ro or rw? What if its the > other way around? Wrong entry in fstab but correctly mounted? Then fstab needs changing, no remount necessary. Apart from that, I still agree with splitting being the saner choice and second the notion that things that share names and properties can be wrapped up on the DSL level, and shouldn't share actual types instead. Regards, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: about http basic authentication dashboard
hi, I tried with the puppet tools and some browsers. I think the first one is the revelant one . Some browsers could support this method (ff and epiphany do not support it afaik) . So if it appears in the docs, i thought maybe it was a lacking apache directive but i did not found anything about it. With wget and such tools there is no problem since they are tools done to support 401 requests on the command line (--user --password). Thanks. On 22 mar, 17:08, Felix Frank wrote: > On 03/22/2011 04:34 PM, chp wrote: > > > Hi, > > > I am running dashboard 1.1.0rc1 under passenger 3.0.5 and apache 2.2.3 > > with puppet 2.6.6. Im trying to get urls like this > > >http://user:password@host > > > working as suggested in the docs for reporting but atm i did not get > > it (401 auth requided). Maybe I am forgetting something? I use a > > common .htpasswd file. Auth type Basic, etc. > > > Sorry if this has been seen in this mailing-list. I searched for it > > but I could not find it. > > Hi, > > do you enter this in your browser? I think that should work. > > Now if you're using wget or curl, things may be different. E.g., wget > uses special extra params for authentication. > > HTH, > Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Ruby DSL: create_resource with exec
Hi! How to create "exec" resource in ruby DSL? Found mention of create_resource but had no luck in using it =( -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] RFC: Splitting up the file{} type functionality.
Am 22.03.2011 23:52, schrieb Nigel Kersten: > If you're enabling recursive copies for Directories, then you're also > supporting the 'source' property, and you're also supporting the > "links => {follow, manage, ignore}" parameter and recurse and > recurselimit I see your point. As an alternative, extracting the recursive directory copy facility is definitely a step in the right direction. I'm not sure if the symlink feature should be extracted too. It should at least get a different parameter name, though. The overloaded 'ensure' is confusing. Regards Christian -- Dipl.-Inf. Christian Kauhaus <>< · k...@gocept.com · systems administration gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 11 · fax +49 345 1229889 1 Zope and Plone consulting and development -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Camp Announcements
Hi Jose, On Mar 18, 2011, at 9:40 PM, Jose Palafox wrote: > Hi, > > We've set up a speaker line up, menu, and a bunch of other useful information > about Puppet Camp on our website. The event is going to be awesome, we've got > some great speakers, and social events planned. Nearly half the team at > Puppet Labs will be in attendance at the event, and we're really looking > forward to meeting everyone. I'd like to encourage everyone that's been > waiting to register to sign up, even if you're local in Amsterdam, by signing > up a bit in advance you'll get a pre printed name badge and everyone's more > likely to get shirts that fit rather than whatever sizes I guess. [...] On the FAQ site you mention that you will try to get some "discounted rooms at a nearby hotel". Do you already know if or when the group registration code will be available? See you in Amsterdam, - Martin > > > > > -- > Jose Cruz Palafox Jr. > Operations | Puppet Labs > (503) 877-2403 | @Cruzfox > j...@puppetlabs.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-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.