have you ever used cloned channel?
you can clone by web ui (and spacewalk commang line), and great improvement of
the last year is command spacewalk-clone-by-date wich allow you to clone base
and child channels by date
best regards
a
Da: [email protected]
A: "[email protected]" [email protected]
Cc:
Data: Tue, 28 Oct 2014 15:36:18 +0000
Oggetto: [Spacewalk-list] best practice for node subscription to latest
channels (controlled patching)
> All,
>
> I'm learning this tool and reading articles, watching videos and understand
> the basics regarding channels, repo and activation keys. Where I struggle is
> creating a channel that includes everything the node will need, namely base
> and patch. The problem I've not solved yet is how do I allow nodes access to
> the latest channels w/o risking a version upgrade from 6.x to 6.y?
>
> In theory I think I should allow my latest channels to sync nightly so as to
> stay updated in the event we needed to deploy something immediately.
> However, I do not subscribe my nodes to the latest channel. My idea is that
> I'll clone the latest repo per quarter and make that available to the nodes.
> I see this as a problem b/c I'll have to edit each channel each quarter. Is
> there a best practice to prevent manual intervention? Have I missed the mark
> entirely?
>
>
> Spacewalk 2.0
>
> Thanks
> Wes
>
>
>
> _______________________________________________
> Spacewalk-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
