It depends really on what's in your provisioning template for
preseeds/kickstart. Our stock templates can set up an HTTP proxy using
the "http-proxy" parameter which you can set globally, per host, domain
etc (Foreman :: Manual global
parameters).
Taking kickstart as an example, we have:
https://github.com/theforeman/community-templates/blob/master/kickstart/provision.erb#L21
Which uses the http-proxy parameter value (the hostname of the proxy)
and then adds a --proxy option to the install media configuration.
···
On 18/03/15 12:33, Ben Shephard wrote: > Hello > > I've been using Foreman for about six months but one thing has managed > to perplex me. I can't seem to work out how to to set a HTTP proxy for > the package repo mirrors. I've managed to work around this by creating a > reverse proxy for each repo in use and creating DNS records internally > to point their names to the reverse proxy but I'm sure there must be an > easier way. I've only recently noticed the http_proxy snippet but I'm > unsure how to use it and I can't find anything in the documentation and > if there is already anything written about this it's very hard to find > because most search engine results seem to match Smart Proxy related > articles. > > If anyone can help point me in the right direction it'd be much appreciated.–
Dominic Cleal
Red Hat Engineering