On Tue, Dec 15, 2015 at 05:58:48PM +0200, Yaniv Bronheim wrote: 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. 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. 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.