[Spacewalk-list] looking for kernel mangement recommendations

[Paul Robert Marino]

I would go with route 2 with some alterations
you should get into the habit of taking snapshots the host that way
you can always compare and role back updates
The other thing is you still need mrepo as a middle man for RHN. So
optionally you can alter the repos after they synced to move the
kernel update packages to a repo and sync them to a different channel
and copy them over to the standard channel when you are ready to push
them to hosts.
The trick is you could then never subscribe the hosts to the channel
with the new kernel updates unless it a test host you are using to
test the latest greatest versions of packages.


On Wed, Dec 19, 2012 at 3:47 PM, Snyder, Chris <Chris_Snyder at sra.com> wrote:
> I’m sure there’s something that could be done with cloning channels, but I
> admit, I haven’t investigated this much, it seems that this would be a very
> ugly solution as it would probably involve having to clone our core RHEL
> channel (minus any kernel updates) once a month, then update all hosts to
> use the cloned RHEL channel, or something like that.  This just feels like
> it’s the wrong direction and would involve lots of effort and potentially
> raise risk of something going very wr