<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style></style></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>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.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>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.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>This is scripted using bash and executed by cron.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I have implemented a 1:1 (repo:channel) philosophy in our Spacewalk server for the “ease” of it.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Best regards<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Frank Mikkelsen Blohmé<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Axis Communications AB – IT Group<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Sweden, Lund<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> spacewalk-list-bounces@redhat.com [mailto:spacewalk-list-bounces@redhat.com] <b>On Behalf Of </b>Ciro Iriarte<br><b>Sent:</b> den 10 december 2012 22:17<br><b>To:</b> spacewalk-list@redhat.com<br><b>Subject:</b> Re: [Spacewalk-list] Hardware Vendor Repos<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>2012/12/10 Cameron Kerr <<a href="mailto:cameron.kerr@otago.ac.nz" target="_blank">cameron.kerr@otago.ac.nz</a>><o:p></o:p></p><div><div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><div><p class=MsoNormal>The non-rpm files will not pose a problem. I imported HPs repo a few says ago without problem. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>For example, I have custom channels for each third-part/ISV component that makes up part of our standard opener rating environment (SOE).<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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.<span style='color:#888888'><br><br>-- <o:p></o:p></span></p><div><p class=MsoNormal><span style='color:#888888'>Cameron Kerr <o:p></o:p></span></p></div></div><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>On 11/12/2012, at 3:09 AM, "Ciro Iriarte" <<a href="mailto:cyruspy@gmail.com" target="_blank">cyruspy@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>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? <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Ref:<o:p></o:p></p></div><div><p class=MsoNormal><a href="http://downloads.linux.hp.com/SDR/downloads/SPP/suse/SLES11/x86_64/current/" target="_blank">http://downloads.linux.hp.com/SDR/downloads/SPP/suse/SLES11/x86_64/current/</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Currently I have 4 channels with all the related repositories linked to them:<o:p></o:p></p></div><div><p class=MsoNormal>sles11-x86_64-vmware<o:p></o:p></p></div><div><p class=MsoNormal>sles11-x86_64<o:p></o:p></p></div><div><p class=MsoNormal>rhel5-x86_64<o:p></o:p></p></div><div><p class=MsoNormal>rhel6-x86_64<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regards,<o:p></o:p></p></div><div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>-- <br>Ciro Iriarte<br><a href="http://cyruspy.wordpress.com" target="_blank">http://cyruspy.wordpress.com</a><br>--<o:p></o:p></p></div></div></blockquote></div></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>_______________________________________________<o:p></o:p></p><div><p class=MsoNormal><br>Spacewalk-list mailing list<br><a href="mailto:Spacewalk-list@redhat.com" target="_blank">Spacewalk-list@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a><o:p></o:p></p></div></div></blockquote></div></blockquote></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regads,<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>-- <br>Ciro Iriarte<br><a href="http://cyruspy.wordpress.com">http://cyruspy.wordpress.com</a><br>--<o:p></o:p></p></div></div></body></html>