(RRD Schema Changes in 2025) pve2/2.3-{type} vs pve-{type}-9.0 handling; ds & cf values; data migration?

[linux]

Hey,

Looks like with the changes to RRD, there is a new data upgrade process, and some partially-reverted changes.

Is someone able to please publish the ds/cf values for the below variants, that would be great.

• pve2-{type}

vs

• pve2.3-{type}

vs

• pve-{type}-9.0

It seems pve2-{type} no longer in-code, despite still being current on some hosts on latest v8.4.14 PVE.

We have some machines on v8.4.x which only have pve2-{type} options, and others which have been upgraded.
Can we force said upgrade? How? It seems inconsistent which 8.x and 9.x hosts have been upgraded to new schema, or not.

root@PVE-DEV:/var/lib/rrdcached/db# ls -l
total 12
drwxr-x--- 2 root root 4096 Dec 26  2023 pve2-node
drwxr-x--- 4 root root 4096 Dec 26  2023 pve2-storage
drwxr-x--- 2 root root 4096 Oct 29  2024 pve2-vm
root@PVE-DEV:/var/lib/rrdcached/db# pveversion
pve-manager/8.4.14/b502d23c55afcba1 (running kernel: 6.8.12-16-pve)

API Viewer doesn't list options for ds nor cf, and even just 2 weeks ago there are further tweaks to this, so I am dubious whether it's stable.

There's been a lot of change around this:

• Change History: https://github.com/proxmox/pve-manager/commits/master/PVE/API2Tools.pm
  • Now, it prefers the pve-{type}-9.0 schema, however doesn't seem to be very cleanly handling cases of old/mixed data.
• "pve2.3-vm has been introduced with commit 3b6ad3ac back in 2013.
  By now there should not be any combination of clustered nodes that still send the old pve2-vm variant."
  • Which doesn't align with some of our machines not having pve2.3 present, only pve2, even though they are on PVE v8.4.x.
• pve9 changed to pve-{type}-9.0 alongside introduction of pressures and so on.
  There is a little bit of information within the mailing list referring to the tooling etc.
• pve2 schema removed entirely from the code-base it seems.
  pve2.3 schema ear-marked for removal in PVE10.

Our requests are being handled as if they are pve-{type}-9.0 with maxmem and mem, etc, coming back as invalid ds.

It is interpreting cf as a ds, too, when it routes in trying to fetch from 9.0 data sources when laid out as a pve2 request, etc.

What would be the simplest way to move from pve2 to pve2.3 to the pve-{type}-9.0 upgraded schema? Is this all documented?

Hopefully someone is able to assist with this, so we can try to reliably adjust to accommodate hosts in all mixed states, as they seem to be!

Thank you!