<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=us-ascii"><meta name=Generator content="Microsoft Word 12 (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'>Have you looked into using clone-by-date to push content from your level 1 to 2? Or you can look into the spacewalk-manage-channel-lifecycle script. <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'>Cloning will take all content from a source channel into a target, so you won’t need to push individual packages. For example, if you clone the RHN public channel on the 1<sup>st</sup> of every month to dev, you can do whatever inspection and testing you need to do on system subcribed to the dev channel. Say on the 15<sup>th</sup> of the month you are comfortable that dev has the packages you need (further cloning, single errata push, what have you) you can then clone from dev to test on that date. Since dev is the source here, you won’t get anything from the level above (RHN Public). <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'>The script I mentioned was written to provide a wrapper around base channels with multiple child channels and give you a way to do naming conventions, rollbacks, etc. You can do multiple channels with clone-by-date if you use config files.<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'>HTH,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Matt<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><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><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>Choure, Siddharth<br><b>Sent:</b> Thursday, May 23, 2013 1:46 PM<br><b>To:</b> spacewalk-list@redhat.com<br><b>Subject:</b> Re: [Spacewalk-list] Need help with implementation<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Ok I figured out to add packages from one channel to another using the GUI. Now my question is how do I make sure that the dependencies for those packages get transferred as well?<o:p></o:p></p></div><p class=MsoNormal>Thanks,<br>Siddharth Choure<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On Thu, May 23, 2013 at 12:41 PM, Choure, Siddharth <<a href="mailto:schoure@1worldsync.com" target="_blank">schoure@1worldsync.com</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal>Hi Alyson,<br>Thanks for your response. My setup is identical to yours. I have all the packages in Level1 and created a Level 2 Private Channel that has all the packages that one would expect in 6.4 release. Now if I want to push packages from Level 1 to Level 2, how would I do that other than rhn_push?<br><br>Thanks,<br>Siddharth Choure<o:p></o:p></p></div><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On Thu, May 23, 2013 at 12:19 PM, Alyson Calhoun <<a href="mailto:alyson.calhoun@gmail.com" target="_blank">alyson.calhoun@gmail.com</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal>This is how we are currently implementing our setup:<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal> Level 1: RHN public channel<o:p></o:p></p></div><div><p class=MsoNormal> Level 2: Create a "private" channel (considered as dev)<o:p></o:p></p></div><div><p class=MsoNormal> Level 3:Create another channel (considered as qa)<o:p></o:p></p></div><div><p class=MsoNormal> Level 4: one more channel - stable packages (considered as prod)<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>Pull all your nightly packages in level 1<o:p></o:p></p></div><div><p class=MsoNormal>Then sync level2 - do not sync after that until you are ready for updated packages and test they work on your dev builds.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>As you go down the levels, each step is a more "stable" package release.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>From level 2 down, it will only sync when you manually push the packages.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Hope that makes sense.<o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><div><div><p class=MsoNormal>On Thu, May 23, 2013 at 10:32 AM, Choure, Siddharth <<a href="mailto:schoure@1worldsync.com" target="_blank">schoure@1worldsync.com</a>> wrote:<o:p></o:p></p></div></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><div><div><div><div><div><div><div><div><div><p class=MsoNormal>So I am doing a Spacewalk installation for our organization.<br><br>Here is my setup -<o:p></o:p></p></div><p class=MsoNormal>1. Dedicated Spacewalk server.<o:p></o:p></p></div><p class=MsoNormal>2. mrepo pulls all packages from RH base channel and dumps it into rhel-x86_64-server-6 channel.<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>3. I have created a custom channel for our machines matching the release and update we are using. eg. for RHEL6.4, I created rhel6u4 channel using the following command - <br><br>spacewalk-create-channel --user=me --server=localhost --version=6 --update=u4 --release=Server --arch=x86_64 --destChannel=rhel6u4<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>and all my test machines are subscribed to this channel.<o:p></o:p></p></div><div><p class=MsoNormal>This channel has packages that would exist like if I had a 6.4 iso.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>Now my question is, rhel-x86_64-server-6 channel gets updated nightly by mrepo via a cronjob. Suppose RH releases a newer version of kernel that we think we need for our machines or any other package for that matter, how do I transfer that package from mrepo updated channel to our release channel? I know I can do rhn_push but that will involve a lot of work. Is there an easier way to do it?<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>I am also open to suggestions on how to tweak what I am trying to do which is basically, have a frozen channel to which all new machines will be subscribed to as per their release and update and then update the packages in those channels as per our organizations need.<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>Thanks,<o:p></o:p></p></div><p class=MsoNormal>Siddharth Choure<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></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></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><br>_______________________________________________<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><p class=MsoNormal><o:p> </o:p></p></div></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>