On 3 October 2016 at 22:28, Neil Hanlon <[email protected]> wrote: > Sure. That definitely makes sense. > > It does seem logical to me that foreman would manage DHCP/DNS on a proxy > if it's installed, but I also understand why this isn't the case. >
It does makes logical sense, thats the problem :) - this is just a case of two things that make sense conflicting and one of them (in this case the "don't change stuff directly" rule") having to win. I may try to write a blog post on consuming those two modules at some point, but I'm not promising :) > Is the rule of thumb just to... not run foreman-install if you can avoid > it? > It's not a bad rule, although it is up for debate (this manual suggests it after a major version upgrade, for example). My approach is to use it to set up a new instance of Foreman and then import the installer modules into the newly-created puppetmaster (and configure the UI to pass the same overrides that I used on the cmdline, if any). It's a touch more work up front, but that way I'm doing the same thing as running the installer (but every half-hour), with the advantadge of knowing exactly what's being passed to Puppet (and thus the option of tweaking it in the future). HTH Greg -- 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.
