<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"> <html><body style='font-family: Verdana,Geneva,sans-serif'> <p>We have 3 levels, but do something similar. Dev gets cloned from from the Red Hat channel, QA from dev, prod from QA. Servers that can't accept random kernel updates (e.g. Oracle ASM/OCFS boxes) blacklist the kernel* packages on the client side. We have to coordinate with customer DBAs for them to sync up Oracle packages to a new kernel, so that's manual in any case on such systems.</p> <p>On 2012-12-20 7:02, Ree, Jan-Albert van wrote:</p> <blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%"> <p class="d5ef6fad-bee1-4fb0-8516-81793ee9ce0d"> </p> <p> </p> <div style="direction: ltr; font-family: Tahoma; color: #000000; font-size: 10pt;">I used to do patch management at a big hosting company (all this was with Satellite 5.3 , I'm assuming things like this haven't changed since), where we had 4 system levels (DEV, TEST, ACCEPTANCE and PROD) each with their own schedules.<br /><br /> What I did was<br /><br /> - Make a structure with parent + child channels<br /> - Clone these for each system level<br /> - Subscribe the system to the level applicable<br /> - Now when patch day for a level is up, do a sync from the master channel to the clone channel for that level (either an automatic full or a manual package-by-package, in which case you can hold back whatever you want)<br /> - Apply all updates to the systems for that level<br /><br style="direction: ltr; font-family: Tahoma; color: #000000; font-size: 10pt;" /></div> </blockquote> <div> </div> </body></html>