[Spacewalk-list] Channel Recommendation - Best Practice

[Waldirio Manhães Pinheiro]

Hi Matthew, good morning

Thanks for your reply, in fact this is what I normally recommend and do,
but not automatically, in my point of view the manager have to check if
there are new packages in base channel (erratas), but accessing by cloned
channel and adding erratas (first in dev channels, tests and after that,
homolog and production channel).

The idea of this post is really hear our friends about what normally they
do when talking about freezed channel and erratas sync. We have different
kind of clients with different scenarios, so we have clients where they
don't do update, still in the same version without erratas, other apply
only security packages, other only fix packages when there are know bugs
..., so I would like to share this knowledge.

Thanks for your contribution.

B' Regards
Waldirio


On Fri, Jul 25, 2014 at 2:31 PM, Matthew Madey <mattmadey at gmail.com> wrote:

> In a previous job, we had a requirement to keep all clients at RHEL5.8. To
> do this we created a static RHEL5 channel with nothing subscribed to it,
> and it was sync'd nightly. Then we created clone channels using
> spacewalk-clone-by-date. Once the clone channel was created.. we refreshed
> it daily with only security errata using the -o option for
> spacewalk-clone-by-date. You can also use --blacklist to exclude particular
> packages. I think that might be your best option, as I assume you want to
> continue getting new security Errata's, but prevent upgrading to the next
> minor version.
>
>
> On Wed, Jul 23, 2014 at 9:55 PM, Waldirio Manhães Pinheiro <
> waldirio at gmail.com> wrote:
>
>> Hello friends, good morning
>>
>> I've one doubt and would like to share with you to get feedback about
>> what should be a best practice about it. For any reasons, in different
>> environments we have to create a freeze channel, for example RHEL or CentOS
>> 6.2.
>>
>> What do you recommend !?, Create a freezed channel using a release date
>> from specific version or use a date before the next release ?! Let'me
>> explain with example, the version of RHEL 6.2 was delivered in 2011-12-06
>> (OS without erratas) and the version 6.2 complete with all erratas was in
>> 2012-06-19 (one day before next version).
>>
>>
>> Release/Update General Availability Date redhat-release Errata Date* Kernel
>> Version   RHEL 6 Update 6 TBA TBA
>> TBA  RHEL 6 Update 5 2013-11-21 2013-11-20 RHSA-2013:1645-2
>> <https://rhn.redhat.com/errata/RHSA-2013-1645.html> 2.6.32-431  RHEL 6
>> Update 4 2013-02-21 2013-02-21 RHSA-2013-0496
>> <https://rhn.redhat.com/errata/RHSA-2013-0496.html> 2.6.32-358  RHEL 6
>> Update 3 2012-06-20 2012-06-19 RHSA-2012-0862
>> <http://rhn.redhat.com/errata/RHSA-2012-0862.html> 2.6.32-279  RHEL 6
>> Update 2 2011-12-06 2011-12-06 RHEA-2011:1743
>> <http://rhn.redhat.com/errata/RHEA-2011-1743.html> 2.6.32-220  RHEL 6
>> Update 1 2011-05-19 2011-05-19 RHEA-2011:0540
>> <http://rhn.redhat.com/errata/RHEA-2011-0540.html> 2.6.32-131.0.15  RHEL
>> 6 GA 2010-11-09 - 2.6.32-71
>> Link to check dates - https://access.redhat.com/articles/3078
>>
>> What do you recommend about this procedure ?!
>>
>> Appreciate your comments.
>>
>>
>> --
>> ______________
>> B'Regards
>> Waldirio
>> msn: waldirio at gmail.com
>> 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
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>



-- 
______________
Atenciosamente
Waldirio
msn: waldirio at gmail.com
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20140730/554c024b/attachment.htm>