Re: [ovirt-devel] [vdsm] Engine XML: metadata and devices from XML

Please note that the approach described here is outdated, because xmlpickle was too easy to use and too generic: that lead to bloated XML and too high risk of misusing metadata; the new approach (https://gerrit.ovirt.org/#/c/74206/) tries to balance things making usage convenient but disallowing

Re: [ovirt-devel] [vdsm] Engine XML: metadata and devices from XML

On 03/18/2017 01:14 PM, Nir Soffer wrote: > > > On Fri, Mar 17, 2017 at 4:58 PM Francesco Romani > wrote: > > On 03/16/2017 08:03 PM, Francesco Romani wrote: > > On 03/16/2017 01:26 PM, Francesco Romani wrote: > >> On 03/16/2017 11:47 AM, Michal Skrivanek wro

Re: [ovirt-devel] [vdsm] Engine XML: metadata and devices from XML

On 03/20/2017 09:05 AM, Francesco Romani wrote: > On 03/17/2017 11:07 PM, Michal Skrivanek wrote: >>> On 17 Mar 2017, at 15:57, Francesco Romani wrote: >>> >>> On 03/16/2017 08:03 PM, Francesco Romani wrote: On 03/16/2017 01:26 PM, Francesco Romani wrote: > On 03/16/2017 11:47 AM, Michal

Re: [ovirt-devel] [vdsm] Engine XML: metadata and devices from XML

On 03/17/2017 11:07 PM, Michal Skrivanek wrote: >> On 17 Mar 2017, at 15:57, Francesco Romani wrote: >> >> On 03/16/2017 08:03 PM, Francesco Romani wrote: >>> On 03/16/2017 01:26 PM, Francesco Romani wrote: On 03/16/2017 11:47 AM, Michal Skrivanek wrote: >> On 16 Mar 2017, at 09:45, Franc

Re: [ovirt-devel] [vdsm] Engine XML: metadata and devices from XML

On Wed, Mar 15, 2017 at 2:28 PM Francesco Romani wrote: > Hi everyone, > > This is both a report of the current state of my Vdsm patches for Engine > XML support, and a proposal to how move forward and solve > the current open issues. > > TL;DR: > 1. we can and IMO should reuse the current JSON s

Re: [ovirt-devel] [vdsm] Engine XML: metadata and devices from XML

On Wed, Mar 15, 2017 at 2:28 PM Francesco Romani wrote: Hi everyone, This is both a report of the current state of my Vdsm patches for Engine XML support, and a proposal to how move forward and solve the current open issues. TL;DR: 1. we can and IMO should reuse the current JSON schema to descr

Re: [ovirt-devel] [vdsm] Engine XML: metadata and devices from XML

On Fri, Mar 17, 2017 at 4:58 PM Francesco Romani wrote: > On 03/16/2017 08:03 PM, Francesco Romani wrote: > > On 03/16/2017 01:26 PM, Francesco Romani wrote: > >> On 03/16/2017 11:47 AM, Michal Skrivanek wrote: > On 16 Mar 2017, at 09:45, Francesco Romani > wrote: > > We talked ab

Re: [ovirt-devel] [vdsm] Engine XML: metadata and devices from XML

On 03/16/2017 08:03 PM, Francesco Romani wrote: > On 03/16/2017 01:26 PM, Francesco Romani wrote: >> On 03/16/2017 11:47 AM, Michal Skrivanek wrote: On 16 Mar 2017, at 09:45, Francesco Romani wrote: We talked about sending storage device purely on metadata, letting Vdsm rebuild

Re: [ovirt-devel] [vdsm] Engine XML: metadata and devices from XML

On 03/16/2017 01:26 PM, Francesco Romani wrote: > On 03/16/2017 11:47 AM, Michal Skrivanek wrote: >>> On 16 Mar 2017, at 09:45, Francesco Romani wrote: >>> >>> We talked about sending storage device purely on metadata, letting Vdsm >>> rebuild them and getting the XML like today. >>> >>> In the ot

Re: [ovirt-devel] [vdsm] Engine XML: metadata and devices from XML

On 03/16/2017 11:47 AM, Michal Skrivanek wrote: >> On 16 Mar 2017, at 09:45, Francesco Romani wrote: >> >> We talked about sending storage device purely on metadata, letting Vdsm >> rebuild them and getting the XML like today. >> >> In the other direction, Vdsm will pass through the XML (perhaps o

Re: [ovirt-devel] [vdsm] Engine XML: metadata and devices from XML

> On 16 Mar 2017, at 09:45, Francesco Romani wrote: > > We talked about sending storage device purely on metadata, letting Vdsm > rebuild them and getting the XML like today. > > In the other direction, Vdsm will pass through the XML (perhaps only > parts of it, e.g. the devices subtree) like b

Re: [ovirt-devel] [vdsm] Engine XML: metadata and devices from XML

We talked about sending storage device purely on metadata, letting Vdsm rebuild them and getting the XML like today. In the other direction, Vdsm will pass through the XML (perhaps only parts of it, e.g. the devices subtree) like before. This way we can minimize the changes we are uncertain of, a

[ovirt-devel] [vdsm] Engine XML: metadata and devices from XML

Hi everyone, This is both a report of the current state of my Vdsm patches for Engine XML support, and a proposal to how move forward and solve the current open issues. TL;DR: 1. we can and IMO should reuse the current JSON schema to describe the structure (layout) and the types of the metadata s