[ovirt-devel] sync meeting - Vdsm 2.2

Martin Polednik mpolednik at redhat.com
Thu Feb 4 08:54:02 UTC 2016



----- Original Message -----
> From: "Dan Kenigsberg" <danken at redhat.com>
> To: "devel" <devel at ovirt.org>
> Sent: Tuesday, February 2, 2016 5:19:12 PM
> Subject: [ovirt-devel] sync meeting - Vdsm 2.2
> 
> (nir, piotr, danken)
> 
> - splitting supervdsmServer:
>   I think that its a good idea, and that https://gerrit.ovirt.org/#/c/52875/
>   is a good start.
>   It would give a nice separation of responsibility, and may serve as a
>   "teaser" for how Vdsm's public API can be broken apart.
> 
>   Nir is worried that it would introduce instability for no immediate gain,
>   while distracting us from solving the supervdsmServer memory leak, or
>   possible security concens
> 
> - schema conversion: Piotr presented his https://gerrit.ovirt.org/#/c/52864/
>   which would convert the json-based schema into a cleaner yaml-based one,
>   which would be easier to version, validate, and obsolete.
> 
> - Nir was unhappy with recent changes to the contrib client:
>   https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:jsonrpc-client
>   would prefer using standard stomp client
> 
> - name discussion is stalling. some people are worried that a rename may
>   turn out to be expensive (release engineering, outher packages,
>   interal module and function name). Still, it would be fun to foresake
>   the non-pronounceable name "vdsm". ovirt-hostd seems like a front
>   runner at the moment.
> 
> - Nir has advocated trying to use https://trello.com/b/U3lsbVRU/maintenance
> to
>   maintain the list of our pending tasks. Let's try.

Awesome idea! I propose that we add the board to community section of
our wiki[1] since the board is public and great first stop for potential
contributors (or project newcomers).

[1] http://www.ovirt.org/Community

> Ciao!
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
> 



More information about the Devel mailing list