Greetings!
I'm now recently in charge on an (olderish?) Proxmox cluster. It is a little behind in updates and want to confirm at a high level a step or two as I plan to start getting this setup current.
Hardware - we have 4 of these
Supermicro SSG-110P-NTR10
Single Intel(R) Xeon(R) Gold 6312U
512GB of memory
3.84TBx6 Kioxia drives per node
Current PVE is 7.2-11 - here is the full `pveversion` for full details:
Since this is running ceph - this document is a key piece for the upgrade since I'm currently on 16.2.9 and need to get to 17:
https://pve.proxmox.com/wiki/Ceph_Pacific_to_Quincy
Question I have is... Should I upgrade Ceph first, or should I get to PVE 7.4 before doing ceph? Any known issues or gotchas?
There is a PBS server in the mix too. That is 2.2-6 and I need to keep that into consideration.
Thanks!
~Jordan
I'm now recently in charge on an (olderish?) Proxmox cluster. It is a little behind in updates and want to confirm at a high level a step or two as I plan to start getting this setup current.
Hardware - we have 4 of these
Supermicro SSG-110P-NTR10
Single Intel(R) Xeon(R) Gold 6312U
512GB of memory
3.84TBx6 Kioxia drives per node
Current PVE is 7.2-11 - here is the full `pveversion` for full details:
Code:
# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.60-2-pve)
pve-manager: 7.2-11 (running version: 7.2-11/b76d3178)
pve-kernel-helper: 7.2-13
pve-kernel-5.15: 7.2-12
pve-kernel-5.15.60-2-pve: 5.15.60-2
pve-kernel-5.15.60-1-pve: 5.15.60-1
pve-kernel-5.15.53-1-pve: 5.15.53-1
pve-kernel-5.15.39-4-pve: 5.15.39-4
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph: 16.2.9-pve1
ceph-fuse: 16.2.9-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 10.2-ubuntu1~focal1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-3
libpve-guest-common-perl: 4.1-3
libpve-http-server-perl: 4.1-4
libpve-storage-perl: 7.2-10
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
pve-firmware: 3.5-4
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-3
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1
Since this is running ceph - this document is a key piece for the upgrade since I'm currently on 16.2.9 and need to get to 17:
https://pve.proxmox.com/wiki/Ceph_Pacific_to_Quincy
Question I have is... Should I upgrade Ceph first, or should I get to PVE 7.4 before doing ceph? Any known issues or gotchas?
There is a PBS server in the mix too. That is 2.2-6 and I need to keep that into consideration.
Thanks!
~Jordan
Last edited: