Hello Friends A good practice is you create a env like bellow:
Base Software Channel - This channel will receive update all days for example |--- Child Channel - This channel will receive update all days for example Cloned Channel - This channel the admin will control the version of packages |--- Child Channel - This channel the admin will control the version of packages So here you can create cloned channels like prod-centos-6.5_x86-64 |-- epel-6-X86-64 homolog-centos-6.5_x86-64 |-- epel-6-X86-64 desv-centos-6.5_x86-64 |-- epel-6-X86-64 Basically is this, put all with automatically update is no recommended, because in fact what you need is, test your server with a new package version to check if the system will work fine or not., after the "approve" of your IT team, you can apply the updates in your prod servers. Take a note, you can add in your prod. channel the diff between prod and desv or prod and homolog for example. Please friend, add your suggests and ideas! B'Regards ______________ Atenciosamente Waldirio msn: [email protected] Skype: waldirio Site: www.waldirio.com.br Blog: blog.waldirio.com.br LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646 PGP: www.waldirio.com.br/public.html On Tue, Oct 28, 2014 at 1:36 PM, Reneau, Wes W [HDS] < [email protected]> wrote: > 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
