| Hello list, | I still have a doubt on the channel architecture I should set up for my installation. | I have to manage centos and rhel 5 clients. For the rhel 5 clients, I wonder what is best: | - Create a base channel (RHEL 5 x64), rhnpush RHEL 5.7 rpm in it and register all my clients to this channel. In the time, I'll rhnpush each minor release in this channel | and upgrade clients. | - Create a base channel for each RHEL minor release (RHEL 5.5 x64, RHEL 5.6 x64, RHEL 5.7 x64, and so on) and register the clients depending on their current | installation. I wonder how to manager the updates this way. | | Thanks in advance for your advices, | | Pierre
Hi, I follow the advice on http://wiki.centos.org/HowTos/PackageManagement/Spacewalk also for our RHEL systems, that is, I rhnpushed 5.6 to a Base RHEL5 channel and sync updates from a yum repo (which uses mrepo to fetch updates from RHN) into a child Updates channel. This is probably redundant but I can see some uses for having separate channels (allowing some systems to only subscribe to Base for a certain minor release). I created similar channels (Base + Updates) for CentOS 5, and one child channel under each Base for EPEL. I experienced some trouble after adding CentOS though, for some reason CentOS packages were appearing in my RHEL channels, making clients system complain (invalid PGP keys) and not fetching updates. For the time being I have removed the CentOS channels/repos, but will have to make another try later. Martin This email originates from Steria AS, Biskop Gunnerus' gate 14a, N-0051 OSLO, http://www.steria.no. This email and any attachments may contain confidential/intellectual property/copyright information and is only for the use of the addressee(s). You are prohibited from copying, forwarding, disclosing, saving or otherwise using it in any way if you are not the addressee(s) or responsible for delivery. If you receive this email by mistake, please advise the sender and cancel it immediately. Steria may monitor the content of emails within its network to ensure compliance with its policies and procedures. Any email is susceptible to alteration and its integrity cannot be assured. Steria shall not be liable if the message is altered, modified, falsified, or even edited. _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
