I am confused about all the database talk on the list lately. I''ve been playing with Puppet for the last 6 months and have never set up a DB for it to use. What are you guys using the DB for? My first though (really the only thing I could find) was for storing node configurations. But I''m storing them in the file system and it seem to work just fine. What are the advantages of a DB? Also, people seem to be using Rails|Apache|Mongrel|etc. with Puppet for some reason. Again, I don''t know what it might be for though. I don''t have any of those running and it seems to work OK. Is it because PuppetMaster is really running Webrick in the background and if you get more than 10-15 clients it really bogs down the server? I only have about 5 clients right now so maybe I''m not seeing it. Anyway, I know these are pretty low level questions, but I''m going to be ramping up soon and I don''t want any performance surprises. :) Later... Richard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Fri, Aug 22, 2008 at 2:56 AM, Richard Hurt <rnhurt@gmail.com> wrote:> I am confused about all the database talk on the list lately. I''ve been > playing with Puppet for the last 6 months and have never set up a DB for it > to use. What are you guys using the DB for? My first though (really the > only thing I could find) was for storing node configurations. But I''m > storing them in the file system and it seem to work just fine. What are the > advantages of a DB?They are storing the configuration of each node in the database, which gives them some reporting features, and the possiblity of exporting resources on one node and collecting them an another. (See Export/Collect on the wiki)> Also, people seem to be using Rails|Apache|Mongrel|etc. with Puppet for some > reason. Again, I don''t know what it might be for though. I don''t have any > of those running and it seems to work OK. Is it because PuppetMaster is > really running Webrick in the background and if you get more than 10-15 > clients it really bogs down the server? I only have about 5 clients right > now so maybe I''m not seeing it.Exactly. Mongrel + Apache allows for multiple puppetmasterd''s, which share larger workloads much better. The only "Rails" portion here is if you wind up using Storeconfigs, and even then, I''m pretty sure it''s really just ActiveRecord.> Anyway, I know these are pretty low level questions, but I''m going to be > ramping up soon and I don''t want any performance surprises. :)You likely want to move to the Apache->Mongrel setup sooner rather than later. Adam -- HJK Solutions - We Launch Startups - http://www.hjksolutions.com Adam Jacob, Senior Partner T: (206) 508-4759 E: adam@hjksolutions.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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Aug 22, 1:20 pm, "Adam Jacob" <a...@hjksolutions.com> wrote:> On Fri, Aug 22, 2008 at 2:56 AM, Richard Hurt <rnh...@gmail.com> wrote:...snip...> They are storing the configuration of each node in the database, which > gives them some reporting features, and the possiblity of exporting > resources on one node and collecting them an another. (See > Export/Collect on the wiki)Excellent information. I''ll look at the Export/Collect stuff but I''m not sure its for me. Almost all of my clients are going to be exactly the same so I really wont have that big a collection of modules (I hope). When that no longer is true I''ll look into Storeconfigs.> Exactly. Mongrel + Apache allows for multiple puppetmasterd''s, which > share larger workloads much better. > > You likely want to move to the Apache->Mongrel setup sooner rather than later.Ahh, that might explain a few timeouts I''ve had in the past. 3-4 clients all hitting Webrick at nearly the same time is not a good thing. I would think that this type of information should be on the Wiki a little more prominently. Probably in a section about Productionization or something. Thanx! Richard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Aug 23, 2008, at 2:38 AM, Richard wrote:> > On Aug 22, 1:20 pm, "Adam Jacob" <a...@hjksolutions.com> wrote: >> On Fri, Aug 22, 2008 at 2:56 AM, Richard Hurt <rnh...@gmail.com> >> wrote: > ...snip... >> They are storing the configuration of each node in the database, >> which >> gives them some reporting features, and the possiblity of exporting >> resources on one node and collecting them an another. (See >> Export/Collect on the wiki) > > Excellent information. I''ll look at the Export/Collect stuff but I''m > not sure its for me. Almost all of my clients are going to be exactly > the same so I really wont have that big a collection of modules (I > hope). When that no longer is true I''ll look into Storeconfigs. > >> Exactly. Mongrel + Apache allows for multiple puppetmasterd''s, which >> share larger workloads much better. >> >> You likely want to move to the Apache->Mongrel setup sooner rather >> than later. > > Ahh, that might explain a few timeouts I''ve had in the past. 3-4 > clients all hitting Webrick at nearly the same time is not a good > thing. I would think that this type of information should be on the > Wiki a little more prominently. Probably in a section about > Productionization or something.http://reductivelabs.com/trac/puppet/wiki/UsingMongrel -Blake --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Possibly Parallel Threads
- Upgraded puppet-server from EPEL 24.8 to 25.1 - now seeing "puppetmasterd[xxxx]: Too many connections"
- puppet with postgresql adapter
- storeconfigs + environments issue
- PuppetDatabase - collection "yes", anything in db "no"
- End of file and other errors: solution