User Tools

Site Tools


wiki:ai:gaudi-configuration-consistency

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

wiki:ai:gaudi-configuration-consistency [2026/07/21 17:34] – created swilsonwiki:ai:gaudi-configuration-consistency [2026/07/21 17:34] (current) swilson
Line 1: Line 1:
 ====== Keeping Configuration Consistent ====== ====== Keeping Configuration Consistent ======
  
-Nodes drift out of spec over time — someone applies a manual fix, a package updates unexpectedly, a setting gets changed by hand. We catch this with a **weekly automated compliance scan** that checks every Gaudi node against the approved baseline:+Nodes drift out of spec over timesomeone applies a manual fix, a package updates unexpectedly, a setting gets changed by hand. We catch this with a **weekly automated compliance scan** that checks every Gaudi node against the approved baseline:
  
   * Kernel version   * Kernel version
Line 9: Line 9:
   * Hardening controls from [[gaudi-os-patching-hardening|OS Patching and Hardening]]   * Hardening controls from [[gaudi-os-patching-hardening|OS Patching and Hardening]]
  
-If drift is found in the driver or firmware, we fix it through the standard upgrade process (see [[gaudi-software-firmware|Keeping Software and Firmware Current]]) with a change ticket. If the OS/kernel itself has drifted, the node gets re-imaged from scratch rather than patched live — it's faster and more reliable than trying to reconcile a broken state by hand.+If drift is found in the driver or firmware, we fix it through the standard upgrade process (see [[gaudi-software-firmware|Keeping Software and Firmware Current]]) with a change ticket. If the OS/kernel itself has drifted, the node gets re-imaged from scratch rather than patched live it's faster and more reliable than trying to reconcile a broken state by hand.
  
 ---- ----
wiki/ai/gaudi-configuration-consistency.1784655252.txt.gz · Last modified: by swilson