[Spacewalk-list] Hardware Vendor Repos

[Frank Mikkelsen Blohmé]

I had issues on our Spacewalk 1.7 server when syncing directly from HP Software Delivery Repository (HP SDR), the information in HP’s RPM packages seemed to be broken so the Spacewalk 1.7 server couldn’t sync the HP SDR cleanly.
My solution was to sync only RPM packages from the HP SDR to a local directory on the Spacewalk server using lftp’s mirror feature. After the sync is done, only RPM packages of interest is synced from local directory into HP specific custom channels in the Spacewalk server using rhnpush.
This is scripted using bash and executed by cron.
I have implemented a 1:1 (repo:channel) philosophy in our Spacewalk server for the “ease” of it.

Best regards
Frank Mikkelsen Blohmé
Axis Communications AB – IT Group
Sweden, Lund

From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Ciro Iriarte
Sent: den 10 december 2012 22:17
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Hardware Vendor Repos

2012/12/10 Cameron Kerr <cameron.kerr at otago.ac.nz<mailto:cameron.kerr at otago.ac.nz>>
The non-rpm files will not pose a problem. I imported HPs repo a few says ago without problem.

I would wonder though why you don't have more o a 1:1 repo:channel relationship, and then manage membership using the same methodology as with channels.

For example, I have custom channels for each third-part/ISV component that makes up part of our standard opener rating environment (SOE).

You could then also have separate activation keys which enable a particular SOE +HP_Proliant, or +VMWare_guest. You could then put in some logic in the kick start which does some hardware inspection and uses a comma-separated list of activation keys. However, this is currently a hypothesis, and is not something I have actively explored.

--
Cameron Kerr

On 11/12/2012, at 3:09 AM, "Ciro Iriarte" <cyruspy at gmail.com<mailto:cyruspy at gmail.com>> wrote:
Hi!, do you guys usually include repo from hardware vendors?, HP and Dell have their utilities in public repositories but HP includes some non RPM files in there also, can that be handled by spacewalk?

Ref:
http://downloads.linux.hp.com/SDR/downloads/SPP/suse/SLES11/x86_64/current/

Currently I have 4 channels with all the related repositories linked to them:
sles11-x86_64-vmware
sles11-x86_64
rhel5-x86_64
rhel6-x86_64

What would be the best way to organize them?, should I keep this organization adding Dell and HP to each channel or create different channels with repos for each vendor?


Regards,

--
Ciro Iriarte
http://cyruspy.wordpress.com
--
_______________________________________________

Spacewalk-list mailing list
Spacewalk-list at redhat.com<mailto:Spacewalk-list at redhat.com>
https://www.redhat.com/mailman/listinfo/spacewalk-list

Well, currently I have a channel for each Distro/Arch in production and each of them is linked to many repositories (sles+obs, rhel+epel, etc). This is my first installation of SW so I'm not sure if this is the way to go.


Regads,

--
Ciro Iriarte
http://cyruspy.wordpress.com
--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20121212/10aba7d1/attachment.htm>