On Tuesday, October 4, 2016 at 7:24:21 AM UTC-5, Greg Sutcliffe wrote: > > Just to be clear, you're attempting to build a host without any direct > connections to Foreman? Have you done this via changing the :unattended_url > setting in Foreman (not the right way to go) or via the Templates feature > in the smart-proxy (definitely the right way to go)? > > Cheers > Greg >
I am trying to have the primary foreman host do the fiddly bits of building (configuration hostname/ips/disk/etc) like it does for it's "local" host builds and the smart-proxy do the actual building (tftp/centos media). The host initially will have a non-routable ip address (provisioning interface 10.0.10.X) and at a remote location from the foreman primary so I need to figure out how to get past the initial kickstart. As an FYI, the host I'm building will use a "local" puppet master that is a agent of the foreman primary once it's built. Is there a better way to go about this? Not sure if this will make it any more clear but here is what I'm looking at right now. * pop01 -foreman primary (puppet master "alpha" also) * pop02 -builder01, smart-proxy (tftp,dhcp) (puppet master agent of foreman alpha) -host-to-be-built <------ -- 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.
