Hi
We have private cloud install of Edge, also all components running on seperate nodes.
We need to patch our OS each month (redhat 7)
What is best practice with patching and rebooting servers ? We are trying to make this can be done our of hours and scripted.
Do we need to have servers go down and up in certain orders ?
Solved! Go to Solution.
hi @Paul Stilgoe assuming you are running a high-available topology then it won't matter what order you do the OS patching. You maintain full service availability by doing the rollout progressively:
I also wanted to offer an alternative approach particularly as you are talking about scripting, commonly referred to as pets vs. cattle model. Instead of the above where each instance is upgraded (a.k.a pets model) you could look to implement something along the lines of the so called cattle model.
In this model, you don't worry about maintaining the currently running instances. You create machine images for each type of instance and then, when needed, you quickly instantiate a new instance using the image.
In the above example, you would:
The advantage of the above model is you can also reuse this approach to address other issues, for example if there are underlying hardware failures or some other issue that is impacting a single node.
If I've answered your question please click the Accept link or alternatively let us know how we can further help.