[Spacewalk-list] Firewall requires internal Mirroring EPEL and spacewalk repos

[Boyd, Robert]

Jan,

I don't comprehend what you are suggesting.  

The instructions clearly require the installation of the spacewalk client prior to completing the registration.  

The clients I am working with are inside a firewall so they do not have access to the Internet directly.  This means they must be provided with access to the client software by having a repository accessible inside the firewall.  

Is there some way to register a client before installing the spacewalk-client packages?

Robert

On Aug 30, 2012, at 0:15, "Jan Hutař" <jhutar at redhat.com> wrote:

> On Wed, 22 Aug 2012 15:41:11 -0400 "Boyd, Robert"
> <Robert.Boyd at peoplefluent.com> wrote:
> 
>> If you look in the text below everywhere it says to install
>> spacewalk-client-repo or epel-release I'm going to be able to
>> pull down those RPMs and install them         -- then I'll
>> need to go into the /etc/yum.repos.d/spacewalk.repo and
>> epel.repo and fix up the baseurl to point to something on my
>> Spacewalk server and/or proxy server.   That's the part I'm
>> uncertain of at this point.    Or do I have to copy/link the
>> files from inside of spacewalk's repositories to something
>> accessible underneath the /pub tree and use that as the
>> baseurl?
> 
> Hello,
> if you register client into Spacewalk, you do not have to
> set /etc/yum.repos.d/*.repo - yum-rhn-plugin used by yum to
> communicate to Spacewalk subscribes your client into given
> Spacewalk channels - no repo files will be created,
> yum-rhn-plugin just handles this.
> 
> Check:
>  https://fedorahosted.org/spacewalk/wiki/RegisteringClients
> 
> Regards,
> Jan
> 
> 
> 
> -- 
> Jan Hutar     Systems Management QA
> jhutar at redhat.com     Red Hat, Inc.