This is a very common scenario. You will want to deploy smart-proxies in
each remote location. Typically, these smart-proxies run dhcpd, tftpd, etc
for hosts in that specific location. The smart-proxy communicates directly
with your main Foreman instance to orchestrate provisioning for these
hosts. I would suggest reviewing both the 'Smart Proxies'  and
'Provisioning'  sections in the Foreman manual for more information.
On Thu, Oct 13, 2016 at 8:13 AM, Dimitar Hristov <
> Hi All,
> I wonder if it would be possible to provision bare metal servers, which
> are not in a same subnet with the Foreman server (they should connect to
> the Foreman server via the Internet). I saw the `smart proxy` feature
> Foreman has, however I wasn't able to find a similar use case.
> I can only guess whether a server can do a network boot, then a local
> server in the same subnet, running Foreman's `Smart Proxy` can get
> installed with image and kickstart/preseed file, which are stored and
> provided by a Foreman server located in a different network.
> So please, share if you've seen similar environment used with Foreman.
> 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 firstname.lastname@example.org.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
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 post to this group, send email to email@example.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.