What does pve-rbd-storage-configure-keyring exactly do ?

rainer042

Well-Known Member
Dec 3, 2019
38
3
48
124
Hello,

I run two pve-clusters (8.4.11) . One named "D" which has ceph storage is running without VMs (too little RAM), but has a ceph storage cluster configured. The second cluster "A" has no own ceph cluster and so no own storage but many VMs. To bring both together cluster A is simply using ceph storage from cluster D which has several ceph-pools among them are two ceph-pools named D_a and D_verw. There are D_a.keyring and D_verw.keyring files in /etc/pve/priv/ceph/ on the ceph server cluster D.

On the ceph client side on cluster A there are /etc/pve/priv/ceph/D_a.keyring and D_verw.keyring files. These pools are then "imported" in /etc/pve/storage.cfg eg as:
rbd: D_verw
content images
data-pool D_verw-data
krbd 0
monhost <mon-host ip-list>
pool D_verw-metadata
username admin
rbd: D_a
....

This setup with a pve-ceph-cluster providing ceph storage for another ceph cluster is working fine. But pve8to9 when run on a node of the *ceph client* cluster "A" seems to detect an error and not knowing what a call of "pve-rbd-storage-configure-keyring" exactly does or even possibly could break I do not want to start it right away:
Here is what pve8to9 says:

Code:
...
# /usr/bin/pve8to9

NOTICE: Starting with PVE 9, externally managed RBD storages require that the 'keyring' option is configured in the storage's Ceph configuration.

You can run the following command to automatically set the option:


        /usr/share/pve-manager/migrations/pve-rbd-storage-configure-keyring


FAIL: The Ceph configuration of the following externally managed RBD storages needs to be updated:

        D_a, D_verw
...
So what exactly would pve-rbd-storage-configure-keyring do on the A-cluster that has no own ceph but uses storage from the "D"-Ceph-Cluster ?

Thanks
Rainer