Hey, all;

I've come to the point where i need to install puppetdb in my opensource 
puppet server 4.5 implementation.  

Although the use of exported resources is on the scope, the two immediate 
use cases that I'm looking for are:

   - puppet node status
   - Use of a dashboard yet TBD

I looked through the docs at https://docs.puppet.com/puppetdb/4.1/ and have 
some general questions:


   - Are there any hidden issues when installing puppetdb for use with 
   puppet server?  The doc mentions puppet master repeatedly.  I'm not seeing 
   anything in any of the docs that look like they wouldn't run on puppet 
   server 4.5.  Even the "puppet master --configprint route_file" works but 
   having direct feedback from someone who's done it would be nice.
   - When should I consider installing puppetdb on a separate node?  I have 
   8 very basic modules managing roughly 1200 linux systems.  The puppet 
   server is a physical HP dl360 gen8 w/2x16 core cpus and 32 gigs of ram. 
    The number of modules will increase as we migrate more fully into the 
   puppet management paradigm and we will probably end up with nigh on 2000 
   nodes by year's end.  We may also have other teams using open source puppet 
   if the long-delayed puppet enterprise is delayed yet again; however, for 
   the moment, the implementation is very low impact.
   - If I do install puppetdb on the puppet server, how hard is it to move 
   if I later decide to split them up?

I think that covers the questions.  Any hints/tips/suggestions on avoiding 
hurdles would be greatly appreciated as well.  

Thanks for your time

Doug O'Leary

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/595d957c-f360-49d5-b2dc-e39f56e85cae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to