[ovirt-devel] [vdsm] New schema format proposal

Vinzenz Feenstra vfeenstr at redhat.com
Tue Jan 19 09:56:52 UTC 2016


> On Jan 19, 2016, at 10:45 AM, Piotr Kliczewski <piotr.kliczewski at gmail.com> wrote:
> 
> I would like to propose new format for schema that we use in vdsm. I
> started to work on a patch [1] where I explore how the new file should
> look like. I have couple of goals which I would like to achieve by
> doing this transformation:
> 1. I would like to use this file to verify engine code. Currently we
> check only vdsm which leads to compatibility issues.
> 2. I would like to base new jsonrpc based replacement for vdsClient on
> it. I want to create dynamic client which would use new format
> (description used as help when calling verbs)
> 3. Simplify Bridge.py
> 4. Extend the schema to add events
> 5. Explore ideas around api evolution and contract definition.

+1 on the general direction

YAML is much more friendly to write by hand

nitpick on the format:


values: ['status', 'on', 'off', 'reboot'] 

vs 

values:
	- status
	- on
	- off
	- reboot

The result of the latter is also a list of strings which I find personally much more readable
Having to put there quotes is just a pain I really disliked about the JSON style description of our API schema

Anyway thanks :-)

> 
> Once we agree on the format I will work on script which will translate
> one format to the other.
> 
> Thanks,
> Piotr
> 
> [1] https://gerrit.ovirt.org/#/c/52404
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel




More information about the Devel mailing list