(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:js... 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. Ciao!
On Tue, Feb 2, 2016 at 6:19 PM, Dan Kenigsberg <danken@redhat.com> wrote:
(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
Or other stuff like porting to python 3. I'll leave the decision about this to Piotr.
- 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:js... would prefer using standard stomp client
I'm ok, with switching to our jsonrpc library. I'm not happy about the additional changes - the client was kind of rewritten from scratch.
- 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.
We also discussed the username - if we change the project name and the executables we probably want to change the vdsm user to something else (ovirt?). This may be a problem with existing file storage, using vdsm:kvm. I would like to avoid such changes.
- Nir has advocated trying to use https://trello.com/b/U3lsbVRU/maintenance to maintain the list of our pending tasks. Let's try.
Ciao! _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
----- Original Message -----
From: "Dan Kenigsberg" <danken@redhat.com> To: "devel" <devel@ovirt.org> Sent: Tuesday, February 2, 2016 5:19:12 PM Subject: [ovirt-devel] sync meeting - Vdsm 2.2
[...]
- Nir has advocated trying to use https://trello.com/b/U3lsbVRU/maintenance to maintain the list of our pending tasks. Let's try.
Good idea! For some reason I can't add new cards nor edit existing (virt) ones. Maybe account was not properly set (fault on my side) yet. Will solve issues ASAP and start updating stuff. Bests, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani
----- Original Message -----
From: "Dan Kenigsberg" <danken@redhat.com> To: "devel" <devel@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:js... 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@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
On Thu, Feb 4, 2016 at 10:54 AM, Martin Polednik <mpolednik@redhat.com> wrote:
----- Original Message -----
From: "Dan Kenigsberg" <danken@redhat.com> To: "devel" <devel@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:js... 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).
It is a wiki, you can do it. But note that the wiki is going to be replaced by https://github.com/oVirt/ovirt-site I'm not sure if the new side is taking automatically new changes from the wiki, so you may want to send also a pull request to the new site. Nir
[1] http://www.ovirt.org/Community
Ciao! _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
On 04/02/16 12:13 +0200, Nir Soffer wrote:
On Thu, Feb 4, 2016 at 10:54 AM, Martin Polednik <mpolednik@redhat.com> wrote:
----- Original Message -----
From: "Dan Kenigsberg" <danken@redhat.com> To: "devel" <devel@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:js... 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).
It is a wiki, you can do it.
No permissions for the community page. That's why it was a proposal.
But note that the wiki is going to be replaced by https://github.com/oVirt/ovirt-site
I'm not sure if the new side is taking automatically new changes from the wiki, so you may want to send also a pull request to the new site.
Good point!
Nir
[1] http://www.ovirt.org/Community
Ciao! _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
On Tue, Feb 2, 2016 at 6:19 PM, Dan Kenigsberg <danken@redhat.com> wrote:
(nir, piotr, danken) - Nir has advocated trying to use https://trello.com/b/U3lsbVRU/maintenance to maintain the list of our pending tasks. Let's try.
For some reason (probably mistake on my side), the team and the board were private. Now they are public so anyone can visit this board. All the current team members have admin role, so they can add new members and make any change. Cheers, Nir
participants (4)
-
Dan Kenigsberg -
Francesco Romani -
Martin Polednik -
Nir Soffer