Hi,<div>I've been digging around mrepo and still have one last question: in terms of sizing, on page <a href="https://fedorahosted.org/spacewalk/wiki/HowToInstall">https://fedorahosted.org/spacewalk/wiki/HowToInstall</a>, it is told to plan 6GB per channel.</div>
<div>What is the sizing requirement for mrepo per channel?</div><div>As the mrepo is synced with spacewalk, only spacewalk-pushed rpms have to be backuped. I'm planning to store mrepo on local low perfs disks.</div><div>
<br></div><div>Thanks in advance</div><div><br></div><div>Pierre<br><br><div class="gmail_quote">2011/8/5 Martin Eggen <span dir="ltr"><<a href="mailto:mare@steria.no">mare@steria.no</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="NO-BOK" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">Hi,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">correct, my base channel is still 5.6 and the updates channel receives patches (now at 5.7). Mrepo runs daily (nightly), but I do not rebuild ISOs.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">Documentation for setting up mrepo with RHN is here:
</span><a href="https://github.com/dagwieers/mrepo/blob/master/docs/redhat-network.txt" target="_blank"><span lang="EN-US">https://github.com/dagwieers/mrepo/blob/master/docs/redhat-network.txt</span></a><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Also check </span><a href="https://fedorahosted.org/spacewalk/browser/scripts/clone-errata/rhn-clone-errata.py" target="_blank"><span lang="EN-US">https://fedorahosted.org/spacewalk/browser/scripts/clone-errata/</span></a>
<span lang="EN-US"> for cloning RHN errata into your (Base) channel with rhn-clone-errata.py.
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">You need to edit chanMap (ca line 455) to match your SPW channel name, but apart from that it was not too much work setting up. I did one errata clone with –begin-date=<RHEL 5.6 release date> and then I run it nightly
with –-begin-date=<yesterday> to clone new erratas. I only use rhn-clone-errata (not spw-clone-errata between local channels, yet).<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">Martin<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt">Fra:</span></b><span style="font-size:10.0pt"> <a href="mailto:spacewalk-list-bounces@redhat.com" target="_blank">spacewalk-list-bounces@redhat.com</a> [mailto:<a href="mailto:spacewalk-list-bounces@redhat.com" target="_blank">spacewalk-list-bounces@redhat.com</a>]
<b>På vegne av</b> Pierre Casenove<br>
<b>Sendt:</b> 5. august 2011 07:45<br>
<b>Til:</b> <a href="mailto:spacewalk-list@redhat.com" target="_blank">spacewalk-list@redhat.com</a><br>
<b>Emne:</b> Re: [Spacewalk-list] Architecture question<u></u><u></u></span></p><div class="im">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Hello,<u></u><u></u></p>
<div>
<p class="MsoNormal">Thanks for the feedback.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">So all your system are in version 5.6 minimum and some subscribe to the updates channel, which now contains rhel 5.7 for example. Am I correct?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Could you please point me to some tutorial to setup mrepo and rhn? Do you run mrepo and rebuild an iso every night or just once a week?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Pierre<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
<div>
<p class="MsoNormal">2011/8/4 Martin Eggen <<a href="mailto:mare@steria.no" target="_blank">mare@steria.no</a>><u></u><u></u></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
</div>
</div>
<p class="MsoNormal">Hi,<br>
I follow the advice on <a href="http://wiki.centos.org/HowTos/PackageManagement/Spacewalk" target="_blank">
http://wiki.centos.org/HowTos/PackageManagement/Spacewalk</a> also for our RHEL systems, that is, I rhnpushed 5.6 to a Base RHEL5 channel and sync updates from a yum repo (which uses mrepo to fetch updates from RHN) into a child Updates channel. This is probably
redundant but I can see some uses for having separate channels (allowing some systems to only subscribe to Base for a certain minor release). I created similar channels (Base + Updates) for CentOS 5, and one child channel under each Base for EPEL.<br>
<br>
I experienced some trouble after adding CentOS though, for some reason CentOS packages were appearing in my RHEL channels, making clients system complain (invalid PGP keys) and not fetching updates. For the time being I have removed the CentOS channels/repos,
but will have to make another try later.<br>
<br>
<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></div>
<div><br><br><br><font face="Arial" size="1"><hr><div class="im">This email originates from Steria AS, Biskop Gunnerus' gate 14a, N-0051 OSLO, <a href="http://www.steria.no" target="_blank">http://www.steria.no</a>. This email and any attachments may contain confidential/intellectual property/copyright information and is only for the use of the addressee(s). You are prohibited from copying, forwarding, disclosing, saving or otherwise using it in any way if you are not the addressee(s) or responsible for delivery. If you receive this email by mistake, please advise the sender and cancel it immediately. Steria may monitor the content of emails within its network to ensure compliance with its policies and procedures. Any email is susceptible to alteration and its integrity cannot be assured. Steria shall not be liable if the message is altered, modified, falsified, or even edited.</div>
</font></div>
</div>
<br>_______________________________________________<br>
Spacewalk-list mailing list<br>
<a href="mailto:Spacewalk-list@redhat.com">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><br></blockquote></div><br></div>