Firstly, by default the media comes from an upstream mirror - the default Centos mirror we ship is http://mirror.centos.org/centos/$version/os/$arch - no installation media is going to be retrieved from Foreman under either scenario. Of course, you're welcome to spin up an http mirror of your own on a given network add it in the Foreman UI (or take a look at our Katello plugin for content management). Your "Local" scenario is presumably using an appropriate solution for you, so we're good here (assuming pop2 can see this mirror).
Secondly, the TFTP is always handled at the proxy level, so that doesn't change from your "Local" scenario. The only "non-local" thing you need to worry about is the templates - as you see in your original post, you're trying to retrieve them from the proxy, which (out of the box) won't work - the proxy doesn't understand those URLs. That's what leads to my question about how the proxy's IP appears in your PXE template, because if you hard-coded it (or changed :unattended_url) then not only will it not work, it'll actually break your "Local" setup, because :unattended_url is a global setting. Assuming then that the host in pop2 has no route to Foreman in pop1 (if it does, then you need nothing more than a TFTP proxy in pop2, the rest should work as before), then what you want to do is configure the "Templates" plugin for the proxy - this is *exactly* the use case it was written for. You can find docs for it here: https://theforeman.org/manuals/1.12/index.html#4.3.12Templates 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.
