You have three things to configure if you want to take an existing
puppetmaster:
- ENC: external_nodes, nodes_terminus in puppet.conf, node.rb script
- reporting: foreman.rb report processor, reports in puppet.conf
- Smart proxy: foreman-proxy package, settings.yaml config
They're not particularly difficult to set up (there are sections in the
manual for each I think), but I'd recommend having a reference setup
from the installer on a VM or something if you do. You'll find it far
easier to copy what it's done than to work from scratch.
The only other thing that may sway you is that the installer configures
the puppetmaster to run under Apache and Passenger. If you're using the
standalone puppetmaster service today, you will find this beneficial as
it's much more scalable.
Remember that if you choose to configure the puppetmaster piece by
yourself, you can still use the installer and deselect the puppetmaster
option from the menu.
Cheers,
···
On 17/04/13 23:11, Brian Dunbar wrote: > I've stood up a Puppet 3 server, it's running two servers, more to > follow. Suddenly I realize that a GUI would be nice to have. > > Is the optimal solution to blow away the existing server, allow Foreman > to install 'by default' and build a new puppet master? Or is there a > not-so-very painful way to hook up a new install of Foreman with an > already existing Puppet Master?–
Dominic Cleal
Red Hat Engineering