Why don't you use the bootstrap script for those clients? It's really easy to copy the template and plugin the few pieces of information you need to get it to work for your environment. In my environment I have several spanning RHEL, Scientific Linux CentOS and soon Oracle Linux (yuck) for a multi-org environment. That said the bootstrap scripts could use some enhancement and I've been thinking about writing a RFE laying out what's needed. Simply stated there should be a web page to generate them for specific distros and activation keys. Further more the base packages it installs to get the registration to work should come from the distro specific base and the spacewalk client repo for that distro instead of thr RHEL version which is its builtin behavior like the kickstarts attempt to do as well. I've implemented a hack in mine to do that but it should be configurable via the Web page in a similar manner to kickstarts. Incidentally the kickstarts are where I get the URI for the correct repos on the spacewalk server and they don't require authentication. I think I get what you are doing with the vhost it's similar to what a lot of people do with mrepo but you can do it with a directory instead of a vhost and there are a few components of spacewalk that at least historically don't interact with other vhosts on the same box. I also do something similar with ISOs mounted on a loopback and a directory statement in my apache config to initially populate new versions of distros into spacewalk. That is unless I have it all wrong and you are spoofing the DNS domains for the public yum repos to redirect them to your box. Sent from my BlackBerry 10 smartphone.
The host sits on a squid proxy, I rsync just the repos i need from epel and only allow that specific url to pass from the web server. spacewalk uses the proxy as well. However my spacewalk servers are all linked to each other… so only 1 has internet access to retrieve packages… matter of fact the one only reach out to a specific redhat server to pull patches. the web server hosting the epel packages are not on spacewalk… they reside on one of my corporate web servers and its a simple host to a locked folder. Every host in my infrastructure does not see the outside world at all. This is why we use spacewalk and spacewalk slaves. Every aspect is controlled.. I hardly think medical environments are as heavily scrutinized as financial institutions but I have never dealt with many fins. the vhost is just a redirect to a locked up folder, it makes it easier to setup and also makes it easier for systems that do not have all packages installed… when we purchase redhat based appliances we rely heavily on getting spacewalk access to these hosts, for reporting back to the vendors. A simple yum repo file and we can easily install the packages we need to get spacewalk on the host. Again this is my environment and has worked quite well for us. What works for me may not work for you. But Im just giving the user who asked a simple solution. —Joe
| |||||
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
