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

well, a disk is a chain, so there has to be only one leaf On Wed, Feb 19, 2020 at 9:58 AM Fedor Gavrilov <fgavrilo(a)redhat.com&gt; wrote: > > Amit, Benny, thanks for your help! > > So does that mean that there can only be at most one leaf in the chain at any moment? Do we also expect at least one leaf? > > Fedor > > ----- Original Message ----- > From: "Benny Zlotnik" <bzlotnik(a)redhat.com&gt; > To: "Fedor Gavrilov" <fgavrilo(a)redhat.com&gt; > Cc: "devel" <devel(a)ovirt.org&gt; > Sent: Wednesday, February 19, 2020 8:50:00 AM > Subject: Re: [ovirt-devel] do we even handle volume metadata in the engine? > > Whether a volume is a leaf can be easily computed since it's the last > volume in the chain, see[1] > > > [1] https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules... > > On Tue, Feb 18, 2020 at 5:14 PM Fedor Gavrilov <fgavrilo(a)redhat.com&gt; wrote: > > > > 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 in the engine part at all. I understand this is in the end executed by VDSM, but nevertheless - in what format are we even reading and writing volume metadata? Even class/method name would be helpful. > > > > Thanks, > > Fedor > > _______________________________________________ > > Devel mailing list -- devel(a)ovirt.org > > To unsubscribe send an email to devel-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/EBNNYCDNFV3... >