[technique] Mise a jour du cluster proxmox/ceph en version 9.0

[Laurent GUERBY]

Bonjour,

Le cluster proxmox/ceph de tetaneutral.net va être mis a jour en version 9.0 cette apres-midi :

https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_9.0

https://www.proxmox.com/en/about/company-details/press-releases/proxmox-virtual-environment-9-0

Cela implique reboot de chaque hyperviseur pour passer en kernel 6.14

Grace a la "live" migration aller/retour des VMs cela ne devrait pas avoir d'impact sur les 227 VMs du cluster.

Note : 

- nous allons utiliser "pvecontrol" https://github.com/enix/pvecontrol qui a une fonctionalité "evacuate" avec un respect de limite en RAM libre, cf ci-apres.

- ceph est deja a la derniere version 19.2.3, nous avons juste équilibré l'usage disque des OSD avec :

ceph config set mgr mgr/balancer/upmap_max_deviation 3
# avant : MIN/MAX VAR: 0.85/1.11  STDDEV: 3.61
# apres : MIN/MAX VAR: 0.88/1.06  STDDEV: 2.51


Sincèrement,

Laurent

$ uvx --from pvecontrol pvecontrol  -c g1 node evacuate --dry-run g1 \
g2 g3 g20 g21 g22 g23
INFO:root:Proxmox cluster: g1
Migrating VM 112 (gozdata.tetaneutral.net) from g1 to g21
Migrating VM 139 (gitoyen.tetaneutral.net) from g1 to g21
Migrating VM 150 (snowflake.tetaneutral.net) from g1 to g21
Migrating VM 187 (vm-lab.tetaneutral.net) from g1 to g21
Migrating VM 211 (resistra.tetaneutral.net) from g1 to g21
Migrating VM 212 (minhiriath.tetaneutral.net) from g1 to g21
Migrating VM 215 (agrion.tetaneutral.net) from g1 to g21
Migrating VM 216 (vmpg.tetaneutral.net) from g1 to g21
Migrating VM 217 (vmtavpa.tetaneutral.net) from g1 to g21
Migrating VM 227 (cej.tetaneutral.net) from g1 to g21
Migrating VM 259 (probe-04.teta.neutri.net) from g1 to g21
Migrating VM 267 (glouton.crapouillou.net) from g1 to g2
Migrating VM 278 (rodo.tetaneutral.net) from g1 to g2
Migrating VM 281 (cafai.tetaneutral.net) from g1 to g21
Migrating VM 287 (chatons1.tetaneutral.net) from g1 to g2
Migrating VM 291 (id2ndr-bullseyes.tetaneutral.net) from g1 to g21
Migrating VM 293 (cine2000.tetaneutral.net) from g1 to g21
Migrating VM 300 (funchs.tetaneutral.net) from g1 to g2
Migrating VM 301 (vmrichmond.tetaneutral.net) from g1 to g21
Migrating VM 302 (alogik.tetaneutral.net) from g1 to g2
Migrating VM 305 (goa.tetaneutral.net) from g1 to g2
Migrating VM 306 (burban.tetaneutral.net) from g1 to g2
Migrating VM 307 (cubran.tetaneutral.net) from g1 to g21
Migrating VM 308 (hybridlab.tetaneutral.net) from g1 to g2
Migrating VM 309 (narglatch.tetaneutral.net) from g1 to g2
Migrating VM 310 (ptijean.tetaneutral.net) from g1 to g2
Migrating VM 311 (virtauzan.tetaneutral.net) from g1 to g2
Migrating VM 312 (mimir.tetaneutral.net) from g1 to g2
Migrating VM 313 (pstat.tetaneutral.net) from g1 to g2
Migrating VM 314 (vmnaar.tetaneutral.net) from g1 to g2
Migrating VM 316 (zoe.tetaneutral.net) from g1 to g2
Migrating VM 317 (zoe2.tetaneutral.net) from g1 to g2
Migrating VM 318 (euronode.tetaneutral.net) from g1 to g2
Migrating VM 326 (tools) from g1 to g22
Migrating VM 327 (wireguard) from g1 to g2
Migrating VM 329 (vaultwarden-test) from g1 to g2
Migrating VM 334 (stalwart.tetaneutral.net) from g1 to g22
Migrating VM 340 (nixos01.tetaneutral.net) from g1 to g2
Migrating VM 349 (commu.tetaneutral.net) from g1 to g22
Migrating VM 351 (rt-misc.tetaneutral.net) from g1 to g22

$ cat ~/.config/pvecontrol/config.yaml
node:
  # Overcommit CPU factor 1 = no overcommit
  cpufactor: 4
  # Memory to reserve for the system on a node (in bytes)
  memoryminimum: 25769803776
clusters:
  - name: g1
    host: g1.tetaneutral.net
...