Upgrading the Base OS in an M3 Anvil! Cluster: Difference between revisions

From Alteeve Wiki
Jump to navigation Jump to search
Line 19: Line 19:
If you're doing a planned update, and all machines in the Anvil! cluster is online, you can use <span class="code">[[striker-update-cluster]]</span>.
If you're doing a planned update, and all machines in the Anvil! cluster is online, you can use <span class="code">[[striker-update-cluster]]</span>.


This is the scenario we will be covering in this tutorial. If you are replacing a failed machine, see:
This is the scenario we will be covering in this tutorial.  


* [[Replacing a Failed Machine in an M3 Anvil! Cluster]]
== If A Machine Has Failed ==
 
If you are replacing a failed machine, follow the "[[Replacing a Failed Machine in an M3 Anvil! Cluster]]" tutorial. You can rebuild the lost machine with the new OS version, so long as the new OS is one major version newer.
 
That is to say, if you have an [[EL]] 8 based M3 cluster, you can use [[EL]] 9 as the OS of the machine being replaced. However, if you do this, please proceed with this tutorial to upgrade the rest of the machines in the cluster as soon as possible after completing the replacement of the lost machine.


<span class="code"></span>
<span class="code"></span>

Revision as of 17:06, 16 August 2024

 Alteeve Wiki :: How To :: Upgrading the Base OS in an M3 Anvil! Cluster

Overview

This article covers rebuilding an Anvil! to upgrade or change the base operating system of all the machines in the cluster.

In short, the process will be to remove each machine from the cluster, reinstall the new OS, and integrate it back into the cluster. We'll do Strikers, Subnodes and a DR host.

This tutorial will also serve as a guide to rebuilding a machine that failed and was replaced. The only difference will be that the installed OS will stay the same.

For this tutorial, we will be updating from CentOS Stream 8 to AlmaLinux 9. The process should work between RHEL, as either the source and/or the destination OS.

Updating

Whether replacing a machine that failed, or upgrading, it is critically important to update the cluster first. This will ensure that the versions of applications installed on the rebuilt machine matches / is compatible with the versions to be installed on the rebuilt systems.

If All Machines Are Online

If you're doing a planned update, and all machines in the Anvil! cluster is online, you can use striker-update-cluster.

This is the scenario we will be covering in this tutorial.

If A Machine Has Failed

If you are replacing a failed machine, follow the "Replacing a Failed Machine in an M3 Anvil! Cluster" tutorial. You can rebuild the lost machine with the new OS version, so long as the new OS is one major version newer.

That is to say, if you have an EL 8 based M3 cluster, you can use EL 9 as the OS of the machine being replaced. However, if you do this, please proceed with this tutorial to upgrade the rest of the machines in the cluster as soon as possible after completing the replacement of the lost machine.


 

Any questions, feedback, advice, complaints or meanderings are welcome.
Alteeve's Niche! Enterprise Support:
Alteeve Support 		Community Support
© Alteeve's Niche! Inc. 1997-2024   Anvil! "Intelligent Availability®" Platform
legal stuff: All info is provided "As-Is". Do not use anything here unless you are willing and able to take responsibility for your own actions.
Retrieved from ‘https://alteeve.com/w/index.php?title=Upgrading_the_Base_OS_in_an_M3_Anvil!_Cluster&oldid=7966’