<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: More on CentOS 5.3 to 5.4</title>
	<atom:link href="http://holyhandgrenade.org/blog/2009/11/more-on-centos-5-3-to-5-4/feed/" rel="self" type="application/rss+xml" />
	<link>http://holyhandgrenade.org/blog/2009/11/more-on-centos-5-3-to-5-4/</link>
	<description>System administration from the trenches.</description>
	<lastBuildDate>Wed, 28 Jul 2010 05:10:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Jeff</title>
		<link>http://holyhandgrenade.org/blog/2009/11/more-on-centos-5-3-to-5-4/comment-page-1/#comment-50</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Mon, 16 Nov 2009 04:41:15 +0000</pubDate>
		<guid isPermaLink="false">http://holyhandgrenade.org/blog/?p=366#comment-50</guid>
		<description>I&#039;ve found this to be the case with certain upgrades, but RHEL/CentOS&#039;s minor releases have been pretty good to me in this regard -- this is actually the first time in all the time I&#039;ve been administering CentOS systems that I&#039;ve been burned by something like this. Major releases are another story; I&#039;ve found those to be especially problematic even going from one Fedora release to the next (Fedora 8-&gt;9 on my build system was a particular nightmare that broke pretty much everything about the system). But again, it&#039;s mostly my own fault for missing the CentOS-specific release notes -- I didn&#039;t experience anything that couldn&#039;t have been avoided by finding the correct documentation.

I still plan to update in this way for minor releases and update packs, as my only damage has been minor, hasn&#039;t affected any user-facing aspects of a system and is much quicker than doing clean reinstalls for the majority of systems. However, I&#039;m absolutely not denigrating your approach: I still absolutely am keeping all of my configuration and data backups on hand when facing OS upgrades like this. I keep most systems managed by Puppet, all system configurations in revision control, and everything&#039;s ready to go when a colorful object of choice hits the fan.

As we move more towards a virtualized infrastructure, where we can easily stand up clones of virtual machines to test upgrades, I suspect a lot of these problems will go away. As it stands today, though, I&#039;m glad we have at least a basic release management framework in place and were able to catch these problems before they made their way onto any important systems.

In any case, this is certainly a big motivation for me to move forward with finishing my Spacewalk deployment. Yum has definitely presented us with certain major issues in the release management process.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve found this to be the case with certain upgrades, but RHEL/CentOS&#8217;s minor releases have been pretty good to me in this regard &#8212; this is actually the first time in all the time I&#8217;ve been administering CentOS systems that I&#8217;ve been burned by something like this. Major releases are another story; I&#8217;ve found those to be especially problematic even going from one Fedora release to the next (Fedora 8->9 on my build system was a particular nightmare that broke pretty much everything about the system). But again, it&#8217;s mostly my own fault for missing the CentOS-specific release notes &#8212; I didn&#8217;t experience anything that couldn&#8217;t have been avoided by finding the correct documentation.</p>
<p>I still plan to update in this way for minor releases and update packs, as my only damage has been minor, hasn&#8217;t affected any user-facing aspects of a system and is much quicker than doing clean reinstalls for the majority of systems. However, I&#8217;m absolutely not denigrating your approach: I still absolutely am keeping all of my configuration and data backups on hand when facing OS upgrades like this. I keep most systems managed by Puppet, all system configurations in revision control, and everything&#8217;s ready to go when a colorful object of choice hits the fan.</p>
<p>As we move more towards a virtualized infrastructure, where we can easily stand up clones of virtual machines to test upgrades, I suspect a lot of these problems will go away. As it stands today, though, I&#8217;m glad we have at least a basic release management framework in place and were able to catch these problems before they made their way onto any important systems.</p>
<p>In any case, this is certainly a big motivation for me to move forward with finishing my Spacewalk deployment. Yum has definitely presented us with certain major issues in the release management process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Sears</title>
		<link>http://holyhandgrenade.org/blog/2009/11/more-on-centos-5-3-to-5-4/comment-page-1/#comment-49</link>
		<dc:creator>Ryan Sears</dc:creator>
		<pubDate>Sat, 14 Nov 2009 00:35:47 +0000</pubDate>
		<guid isPermaLink="false">http://holyhandgrenade.org/blog/?p=366#comment-49</guid>
		<description>Yeah, this is pretty much why I don&#039;t do upgrades en masse, its a LOT easier to just start fresh and move your settings from a backup. I can&#039;t really think of any time when I did a major upgrade and it ended well.</description>
		<content:encoded><![CDATA[<p>Yeah, this is pretty much why I don&#8217;t do upgrades en masse, its a LOT easier to just start fresh and move your settings from a backup. I can&#8217;t really think of any time when I did a major upgrade and it ended well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
