<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Jan 28, 2016 at 11:16 AM, Martin Polednik <span dir="ltr"><<a href="mailto:mpolednik@redhat.com" target="_blank">mpolednik@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 27/01/16 09:53 +0200, Nir Soffer wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Jan 27, 2016 at 9:29 AM, Yedidyah Bar David <<a href="mailto:didi@redhat.com" target="_blank">didi@redhat.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, Jan 26, 2016 at 7:26 PM, Nir Soffer <<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, Jan 26, 2016 at 5:29 PM, Yaniv Dary <<a href="mailto:ydary@redhat.com" target="_blank">ydary@redhat.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I suggest for ease of use and tracking we change the versioning to align to<br>
the engine (4.0.0 in oVirt 4.0 GA) to make it easy to know which version was<br>
in which release and also change the package naming to something like<br>
ovirt-host-manager\ovirt-host-agent.<br>
</blockquote>
<br>
When we think about the names, we should consider all the components<br>
installed or running on the host. Here is the current names and future options:<br>
<br>
Current names:<br>
<br>
vdsmd<br>
supervdsmd<br>
vdsm-tool<br>
vdsClient<br>
(we have also two hosted engine daemons, I don't remember the names)<br>
<br>
Here are some options in no particular order to name these components:<br>
<br>
Alt 1:<br>
ovirt-hypervisor<br>
ovirt-hypervisor-helper<br>
ovirt-hypervisor-tool<br>
ovirt-hyperviosr-cli<br>
<br>
Alt 2:<br>
</blockquote>
<br>
Not sure it's that important. Still, how about:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
ovirt-host<br>
</blockquote>
<br>
ovirt-hostd<br>
</blockquote>
<br>
I like this<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
ovirt-host-helper<br>
</blockquote>
<br>
ovirt-priv-hostd<br>
</blockquote>
<br>
How about ovirt-privd?<br>
<br>
I like short names.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
ovirt-host-tool<br>
</blockquote>
<br>
ovirt-hostd-tool<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
ovirt-host-cli<br>
</blockquote>
<br>
ovirt-hostd-cli<br>
</blockquote>
<br>
I think we should use the example of systemd:<br>
<br>
systemd<br>
systemctl<br>
<br>
So ovirt-hostd, ovirt-hostctl ovirt-hostcli<br>
</blockquote>
<br></div></div>
I'd even suggest going simply with ovirtd and ovirtctl (maybe<br>
ovirtdctl to differentiate ovirt, ovirtd and ovirt-engine).<br>
<br>
Names like ovirt-host-agent possibly introduce abbreviation<br>
clashes - we would most likely end up abbreviating host-agent to HA<br>
and that could be mistaken for high availability in discussions.</blockquote><div><br></div><div>ohad (oVirt Host Agent Daemon, and that's also an Israeli name), or just oha (not to be confused with the Office of Hawaiian Affairs) </div><div>ohanha (oVirt Host Agent Not High Availability , and that's also an Israeli family name, mostly known for some past famous Israeli soccer player)</div><div>ohd (oVirt Host Daemon), far enough from OCD. <br></div><div><br></div><div>I think we are doing a bit of yak shaving here, but it is entertaining ;-)</div><div>Y.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Also we should get rid of '/rhev/' in start of mount points IMO. How<br>
about '/var/lib/ovirt-hostd/mounts/' or something like that?<br>
</blockquote>
<br>
We want to use /run/ovirt-host/storage/ for that, but this is hard change,<br>
since it breaks migration to from hosts using different vdsm versions.<br>
New vms expect the disks at /rhev/data-center and old vms at /rhev/data-center/<br>
<br>
Maybe we can change disks path during migartion on the destination, but<br>
migrating vms to older hosts will be impossible, as the vdsm on the older<br>
machine does not support such manipulation.<br>
<br>
Nir<br>
_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/devel</a><br>
</blockquote>
_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/devel</a><br>
</div></div></blockquote></div><br></div></div>