<br><br><div class="gmail_quote">On Fri, Jul 1, 2011 at 11:25 AM, James Sumners <span dir="ltr"><<a href="mailto:james.sumners@gmail.com">james.sumners@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Fri, Jul 1, 2011 at 11:13 AM, Jim Kinney <<a href="mailto:jim.kinney@gmail.com">jim.kinney@gmail.com</a>> wrote:<br>
> Additionally, from a professional admin standpoint, I find it to be bad<br>
> practice to be upgrading a production system to a new set of libs. By<br>
> definition, a production system is not eligible for an upgrade. It is only<br>
> allowed security and bug fix patches. To perform an OS upgrade is to change<br>
> a production system into a test system which must then pass QA before<br>
> becoming. So from that standpoint, it doesn't matter if a particular OS<br>
> support rolling upgrades or not, the professional admin best practices are<br>
> to put new code on new system, test, QA, promote to production, verify again<br>
> and then roll old production machine to test status for the next cycle.<br>
<br>
</div>The VM I intend to change is not accessible by anyone other than<br>
myself and those who I allow by IP. It's one of a cluster of five.<br>
Since this application is such a pain to deal with in one install,<br>
maintaining a "production" and "test" environment just isn't worth it.<br>
So I keep one of the "production" installs reserved for "testing."<br>
<br>
I do have a test environment, but I only use it when I need to test<br>
something that would affect all servers in the cluster. E.g. testing<br>
to see if this stupid application can handle Tomcat session<br>
replication (which it couldn't).<br>
<br>
This being a VM, going back to a known working state is simple -- just<br>
restore the snapshot.<br>
<br>
It sounds like the answer to my original question is "upgrade to 5<br>
first and then to 6."<br></blockquote><div><br>If my end goal is RHEL6, and I understand that RHEL6 is quite different from RHEL5 in security areas, I would forgo the intermediate step to RHEL5. Time permitting, I would also work to automate the installation of the complicated app that runs on the stack. Maybe not so far as to package it into an rpm (although would allow certain OS-level options like rollbacks to previous version), but at least some auto-installing tarball stuff.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5"><br>
<br>
--<br>
James Sumners<br>
<a href="http://james.roomfullofmirrors.com/" target="_blank">http://james.roomfullofmirrors.com/</a><br>
<br>
"All governments suffer a recurring problem: Power attracts<br>
pathological personalities. It is not that power corrupts but that it<br>
is magnetic to the corruptible. Such people have a tendency to become<br>
drunk on violence, a condition to which they are quickly addicted."<br>
<br>
Missionaria Protectiva, Text QIV (decto)<br>
CH:D 59<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>-- <br>James P. Kinney III<br><br>As long as the general population is passive, apathetic, diverted to
consumerism or hatred of the vulnerable, then the powerful can do as
they please, and those who survive will be left to contemplate the
outcome.<br>- <i><i><i><i>2011 Noam Chomsky<br><br><a href="http://heretothereideas.blogspot.com/" target="_blank">http://heretothereideas.blogspot.com/</a><br></i></i></i></i><br>