Dominic, Am Montag, 22. Mai 2017 16:25:02 UTC+2 schrieb Dominic Cleal: > > > I want the configuration changes to happen through source control only. > > Forman only for transparency, i.e. reporting, sounds perfect. > > Then I'd suggest putting everything into the Puppet environment, forget > Foreman's Puppet class and parameter handling and use Puppet's data > lookup and Hiera to assign classes and parameters to hosts. >
That still sounds a bit like a half-baked solution. 1. Why is the Foreman host being set up and configured using a Puppet recipe, and then I should be throwing it away instead of maintaining, modifying, extending it? 2. What is the cleanest path to add the Foreman host to the Puppet configuration? (I'm not sure how the foreman-answers.yaml is integrated, and whether I should copy everything over from /usr/share/foreman-installer/ modules) 3. Also, shouldn't the foreman-installer be uninstalled to maintain a slim, clean system? I really don't want to SSH into the Foreman host after setting it up, and install stuff manually. How do I set things up that a Forman system is set up, including a Puppet configuration under version control in /etc/puppetlabs, practically from zero? Every step I need to do manually is somewhat wasted time, and potential to introduce errors. I want to avoid that. Thanks, Peter -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
