[ovirt-devel] do we even handle volume metadata in the engine?

2020-02-18 Thread Amit Bawer
You could check Volume.getInfo output: # vdsm-client Volume getInfo storagepoolID=None storagedomainID=91630622-c645-4397-a9fe-9ddf26690500 imageID=9f36c5ff-2ed1-4d1a-a7ad-365e5e1fb7b6 volumeID=4093e21a-73f7-451a-90d1-2b8d41685164 { "apparentsize": "3489660928", "capacity": "6442450944", "childre

[ovirt-devel] do we even handle volume metadata in the engine?

2020-02-18 Thread Fedor Gavrilov
Hi, It seems I was able to get my setup working for NFS storage, thanks for your advices! Now I'm afraid I am stuck again: what I need to do is to add validation for volume metadata to a certain command (to be exact, that VOLTYPE is LEAF). But I can't find examples of us dealing with this data