Jason Ball wrote:
Hi all,
I run a worldwide network running a combination of RHEL, Centos and Core
11 systems and have provisioned a centralised spacewalk server. I am
now in the process of configuring a number of proxy servers at various
locations and I want the proxies to be used for all access from
Just to be sure: You are setting up Spacewalk proxy, right? Not ordinary
http proxy (squid).
kickstarts through to package updates/installs. I've been looking for
information on running kickstarts through a proxy and haven't found
anything so any pointers would be appreciated.
It should work automagicaly. Just replace name of Spacewalk server with
name of Spacewalk proxy in all place in tftp record.
I am currently trialling the following to get the kickstarts to work:
* Replicated the installation media to the proxy (under /var/www/html/pub).
* Set the media url in the kickstart to the above media location.
Hm, I believe this should not be needed. But I did not made KS through
proxy for some time...
* I have found the default kickstart set the 'yum' repositories for the
kickstart to my spacewalk server. A %pre script has been added to
change this to the required proxy server:
current setting: repo --name=rhel5-x64-rpmforge
--baseurl=http://spacewalk.server/ks/dist/child/rhel5-x64-rpmforge/rhel5-x86_64-updated
/usr/bin/sed -e 's/spacewalk.server/proxy.server/' < /tmp/ks.cfg >
/tmp/ks.cfg.lcbld01 /usr/bin/mv /tmp/ks.cfg.lcbld01 /tmp/ks.cfg
I believe that we rewriete all occurencies of spacewalk server hostname
in ks.cfg to proxy hostname. But I could not find it anywhere in code.
So you may have truth.
I should set up some proxy and try it on my own.
* Added a rule to the proxy squid.conf to forward requests for files
(/ks/...) to the spacewalk server as there didn't seem to be any rules
to cater for this.
And why should be?
--
Miroslav Suchy
Red Hat Satellite Engineering
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list