[Spacewalk-list] Selective updates on client side

[Deependra Shekhawat]

Hi All,

We have a setup where in we have the following channels:

---rhel5.5-x86_64-dvd
------rhel5.5-x86_64-updates

The base channel is rhel5.5-x86_64-dvd having all the RPMs which came in the RHEL 5.5 64bit DVD. The child channel is subscribed to RHN and hence contains all the updates for RHEL 5.5 64bit systems.

Now all the systems are subscribed to both base as well as child channel. The problem is that on the client side the update applet shows all the relevant updates applicable for that system.

The requirement is that the update applet should only show critical updates and only those should be available to admin to apply on the client.

One way we thought of doing this was by creating a new channel and push all the critical updates to that channel. Later subscribe the clients with only that channel. This way only critical updates can be seen on client but that deprives the client to get the other updates if there is a need to do that.

Please let me know if we can restrict the update applet in some way to show only critical updates keeping yum update as an option to apply any other update which might not be critical.

Thanks,
Deependra

[Brian Collins]

As you've seen, if updates are available in a channel to which a system is subscribed, the system will see the updates.

 

We run the commercial product, Satellite, so there may be some differences in functionality.  But, what we do is have multiple base channels, each of which is a copy of the main RHEL 5 distro.  Then, we selectively push updates to those base channels, based on where its machines are in testing the updates.  What we do differently is sync the updates directly to our base channels, not child channels.  But then, when we feel comfortable with a set of updates, we bring the channel entirely up to date, so that it matches the original RHEL channel.

 

What you don't want to do, as you have seen, is swap machines between channels.  You COULD do it with activation keys, but it gets tricky.

 

Another solution is to have a third level of channel - for only critical updates.  Like so

Tier 1 - base RHEL distro

---Tier 2.1 - has updates you want ALL machines under Tier 1 to get, so a LIMITED set of updates

-----Tier 3 - has critical updates

---Tier 2.2 - has all updates

 

Machines in Tier 1 ONLY would only see the base installation packages

Machines in Tier 1, and also Tier 2.1, would get updates that you want ALL machines to get.  Call it a baseline update level.

Machines in Tier 3 would see everything from Tier 1 & 2.1, and also updates you deem critical.

Machines in Tier 1 & also Tier 2.2, would get ALL updates.

 

This is a bit more complicated, and requires more management for pushing out updates.  This is where the API comes in handy.

 

I hope this helps.

Brian Collins, RHCE

Sr. Systems Engineer

Southeastern Data Cooperative

 

---

From: Deependra Shekhawat
Sent: Sat 8/27/2011 7:25 AM
To: spacewa...@redhat.com
Subject: [Spacewalk-list] Selective updates on client side