[ovirt-devel] summary for vdsm sync meeting 15\12

[Dan Kenigsberg]

On Tue, Dec 15, 2015 at 05:58:48PM +0200, Yaniv Bronheim wrote:
> Hi,
> We re-initiate vdsm sync meeting, you are all welcome to join and raise
> your patches, ideas and concerns. Or just listen and be updated with the
> plans .
> Joined: nsoffer, fromani, pkliczew, alitke, ybronhei
> 
> 1. pioter raised contact definition work (also part of schema for events) -
> https://gerrit.ovirt.org/#/c/50032/
>  - direction to verify api schema and enforce it in server side
>  - takes care of verisoining differences to keep backward compatibility

I love the idea of moving to a cleaner yaml schema, as well as
validating input/output. We should add a warning when we report a value
that does not fit the schema, so we can fix either the schema of Vdsm.

It is a bit harder when it comes to validating input: we would like to
allow forward compatibility, and silently ignore unknown arguments of a
newer version. But we do want to see that in a specific version, we
actually consume everything that Engine throws at us.

> 2.  https://gerrit.ovirt.org/#/c/48268/ - Functional tests effort
>  - virt, network and storage functional tests are broken - we need to
> stabilize it before enable automation for it. the work will continue until
> having it passes the current testings suite we have, or part of them.

I see that most network tests have been marked with a general "fails in
CI" decoration. This effectively disables them, despite passing rather
nicely in a human-controlled setup.

Can you share the traceback and logs of a single such failure?
I beleive that Edy (CCed) can find out how to clean the slave prior to
running the tests. One thing that should surely be gone is bond0 device,
which confuses our functional tests.

> 3. Francesco share "What's new in virt" in the list - many patches ready
> for review
>  - reviews  will be appreciate for
> https://gerrit.ovirt.org/#/q/topic:cpuinfo
> 4. Nir's cleanup vdsm exceptions -
> https://gerrit.ovirt.org/#/q/topic:exceptions waits for comments and acks
> 5. We discussed about the need for nicer jsoncli client. currently we have
> duplication in documentation between schema, vdsclient and the code.

The xml-based vdsClient must die in 4.0. We should have an introspective
tool that parses the schema, and convert command line to jsonrpc calls.
Such a tool would be useful for QA and debugging of Vdsm.

Regards,
Dan.