[Spacewalk-list] Channels Clarification

[Alyson Calhoun]

You should have a "public" channel and a 'private" channel.

Public being all top level channels, that will check in nightly, and
download any new updates etc.
The private channel will be a clone of what you already have in your public
channel, but will not update nightly.

So in your case, what I would do is this:

Public Channel Primary:  Fedora 18 - x86_64
Public Channel Child: Spacewalk 1.9 Client
Public Channel Child: RPMFusion free and so on....

Then you would  clone your Primary, and clone the child channels and
subscribe your systems to your private channels.

This way, you can compare packages between public and private every so
often, and pull down what you need, without installing something you really
didn't need or want.

I personally wouldn't run the script you mention in Q2, as I would want
full control over my packages, and don't want my private and public to be
synced.  Only if I split my private channels down even more, and created a
dev, qa and prod.  That way I would fully sync with dev to work with new
packages, pull some down to qa and verify they work with my apps, then once
verified.. pull them down to prod to have the most stable channel.

Hope that makes sense. (This by the way was how our redhat consultant
suggested we setup our production satellite server)







On Wed, May 29, 2013 at 2:11 PM, The PowerTool
<thepowertool_sc at hotmail.com>wrote:

> Hello,
>
> I have a fully functional Spacewalk server supporting my FC18
> install-base.  I'm running Spacewalk 1.9 server code.  If there's more
> detail required I'm happy to provide upon request (with instructions--if
> it's Spacewalk-specific).
>
> I've read through the documentation on channels and I'm still a little
> unclear on how things work.  I have a "Fedora 18 - x86_64" channel and a
> "Spacewalk 1.9 Client" channel which were the result of following setup
> instructions provided in the Spacewalk documentation.
>
> I would like to add support for RPMFusion free and non-free repos.
>
> I would like to better understand how channels work.  If there's
> documentation I've not found please send me a pointer.
>
> Question 1:  Should I add the RPMFusion free and non-free as child
> channels under my "Fedora 18 - x86_64" channel since it's for those
> systems?  Or should it be a separate "peer" channel?  If the answer is "it
> doesn't matter" then my only question would be what's the best practice and
> why.
>
> Question 2:  In reading the Spacewalk documentation I came across scripts
> for causing channels to update from the upstream server.  My channels seem
> to do that automatically based upon the settings as part of the GUI config
> for Spacewalk.  Are those scripts for older versions or will I need to use
> them if I add more channels?
>
> Note:  Q2 specifically refers to the last section of "Upload Content to
> Spacewalk (URL below)
> Regularly syncing yum repositories This ​script<https://fedorahosted.org/spacewalk/attachment/wiki/UploadFedoraContent/sync_repos.py>will get the yum repo information out of the database and trigger
> spacewalk-repo-sync for every channel that has a yum repository. You can
> run it from cron to sync your repositories on a regular basis.
>
> Reference URL (Upload Content to Spacewalk):
> https://fedorahosted.org/spacewalk/wiki/UploadFedoraContent
>
> Thanks!!!
>
> J. Mirman
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20130530/b34275d8/attachment.htm>