On 3 October 2016 at 22:37, Neil Hanlon <nhan...@kayak.com> wrote: > Haha I totally get it. I'm in a weird situation since we have puppet > running externally and also alongside our foreman setup while we evaluate > and prepare to switch over to have foreman handle being the puppet > master/ca/etc. All very confusing. For now I think I'll manage DHCP for my > production environment manually and just create a file like > "/etc/dhcp/subnets.conf" which I can force-include after I run > foreman-installer (if I ever do). > > That works, sure. Ultimately, the power is in the users hands - the data *can* be exposed vi the ENC in a variety of ways, so it can be handled by a cfg mgmt agent, or it can be decoupled (or something else again, such as using the Foreman API, which may be how I handle this blog post, if I ever write it....)
Good luck! 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 foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
