[Spacewalk-list] how do the files in /etc/yum.repos.d/ relate when using spacewalk?

Jet Wilda Jet.Wilda at fadv.com
Thu Sep 23 13:37:59 UTC 2010


Hi,

 

                Please excuse my ignorance but I still do not understand
something.  I get how to populate the channels in the Spacewalk server.
What I do not understand is how you prevent packages from EPEL or
RpmForge from overwriting base OS packages on the workstation that pulls
its updates (yum update) from the Spacewalk server.  Does the fact that
they are child channels automatically make it so they won't step on the
top base channel?   Thanks again for answering my questions and being so
patient with me as I try to understand.

 

Thanks,

~Jet

 

From: spacewalk-list-bounces at redhat.com
[mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Marco Giunta
Sent: Thursday, September 23, 2010 4:08 AM

 

On -28163-01--10 20:59, Jet Wilda wrote: 

Hi,

 

                So then your workstations have the spacewalk server and
your local yum repository setup to get RPMs from.  Am I understanding
that correctly?


No, my workstations have only spacewalk repository by rhnplugin




  Or how do the work stations get something from say EPEL that isn't
setup via it's activation key channels?


In my spacewalk server I have a channel for every different repository:
Centos base, updates, extras, Epel, Rpmforge, Karan , Spacewalk-client
and another with my personal rpms. Every night, a cron script, sync all
repositories from external source with 'reposync -l bla bla bla ' ('-l'
flag = enable yum plugin support) to a local directories on my spacewalk
server; in this way I manage 'priority plugin'. Then, same script, sync
my local mirrors with spacewalk channels (spacewalk-repo-sync bla bla
bla)

My activation keys have as base channel, CentOS Base and as child
channels, all other channels. So, with 'yum install bla bla' I can
install a rpm belong to Epel, from my spacewalk server ...

  Marco





 

Thanks,

~Jet

 

From: spacewalk-list-bounces at redhat.com
[mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Marco Giunta
Sent: Wednesday, September 22, 2010 2:41 AM

 

Hi,
workstations are connected to spacewalk server repository by
'rhnplugin'; I think you can enable or disable a channel modifing
'/etc/yum/pluginconf.d/rhnplugin.conf':

/etc/yum/pluginconf.d/rhnplugin.conf 

[main]
enabled = 1
gpgcheck = 1

# You can specify options per channel, e.g.:
#
#[rhel-i386-server-5]
#enabled = 1
#
#[some-unsigned-custom-channel]
#gpgcheck = 0

But you cannot manage priority, AFAIK. I manage it in this way:

- first, I sync external repositories (centos update, extras, rpmforge,
epel and karan) with 'reposync -l bla bla bla ' ('-l' flag = enable yum
plugin support) to a local directories on my spacewalk server
-then  I sync my local mirrors with spacewalk channels
(spacewalk-repo-sync bla bla bla)

  Marco



On -28163-01--10 20:59, Jet Wilda wrote: 

Hi,

 

                I'm trying to understand the relationship of the files
in /etc/yum.repos.d/*.rep once a system is configured to sync against
the spacewalk server.  Are those files not used at all once the system
is using spacewalk?  If not is there a place that you can configure the
repo settings like priority, enabled, etc?

 

Thanks,

~Jet






-- 
 -----------------------------------
|Marco Giunta - SISSA Computer Staff|
|Via Bonomea, 265                   |
|34136 - Trieste, Italy             |
|Tel: +39-40-3787-503               |
|Fax: +39-040-3787-528              |
|e-mail: giunta AT sissa.it         |
 -----------------------------------





-- 
 -----------------------------------
|Marco Giunta - SISSA Computer Staff|
|Via Bonomea, 265                   |
|34136 - Trieste, Italy             |
|Tel: +39-40-3787-503               |
|Fax: +39-040-3787-528              |
|e-mail: giunta AT sissa.it         |
 -----------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20100923/fe6c1c68/attachment.htm>


More information about the Spacewalk-list mailing list