----- Original Message -----
From: "Michal Skrivanek" <michal.skrivanek@redhat.com> To: "Oved Ourfali" <oourfali@redhat.com> Cc: "devel" <devel@ovirt.org> Sent: Thursday, January 28, 2016 3:57:33 PM Subject: Re: [ovirt-devel] Changing the name of VDSM in oVirt 4.0. On 26 Jan 2016, at 19:13, Oved Ourfali < oourfali@redhat.com > wrote: I must agree with Martin here. In addition, I think the benefit here is low, and the efforts it will require and the risks are high. Upgrade issues? Compatibility ones? Effect on engine features such as host upgrade manager, different provisioning products that might rely on that such as puppet recipes, ansible modules, or others.. (can't say all mentioned stuff are relevant, and I guess there might be more implications than I've described).
IMHO, we should spend our time improving our project rather than spend a lot of developers, testers and integration people on these kind of tasks.
+1 I like vdsm. any variant with “agent” brings confusion with guest agent (let alone the fact we have three of them)
then maybe ovirt-vdsmd? :) -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani