<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 25, 2016 at 2:44 PM, Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed, Feb 24, 2016 at 05:36:35PM +0100, Fabian Deutsch wrote:<br>
> Hey,<br>
><br>
> IIUIC host-deploy is currently installing some packages manually:<br>
><br>
> <a href="https://gerrit.ovirt.org/gitweb?p=ovirt-host-deploy.git;a=blob;f=src/plugins/ovirt-host-deploy/vdsm/packages.py;hb=HEAD" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/gitweb?p=ovirt-host-deploy.git;a=blob;f=src/plugins/ovirt-host-deploy/vdsm/packages.py;hb=HEAD</a><br>
><br>
> Can't these dependencies moved to vdsm - or if not - can't they be<br>
> moved to a ovirt-host package?<br>
> Then we'd have all package related informations in one place.<br>
><br>
> I find it odd that host-deploy is taking care of package installation,<br>
> imo it should be sufficient to install a single package and have a<br>
> host ready.<br>
><br>
> host-deploy can then focus on just configuring the existing packages.<br>
><br>
> Thoughts?<br>
<br>
</span>Everything that vdsm requires should be explicitly expressed in<br>
vdsm.spec. vdsm-cli not being their was a bug. If there's anything else<br>
missing, it should be added.<br>
<br>
However, we may have softer requirement: qemu-kvm-tool is nice to have<br>
for deep debugging, but not reallly necessary. In the future, I'd like<br>
ovirt-host-deploy to conditionally not pull iscsi packages if the<br>
datacenter does not require it. Thus I prefer keeping things as they<br>
are, even though it means that ovirt-node largely duplicates the list of<br>
packages from ovirt-host-deploy.<br>
<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div><br></div><div>Just a reminder that ovirt-host-deploy is not installed on the target host, it's just executed there through ssh after having it copied there as a tarball.</div><div>So the installation of the packages can't be done in a different manner. On Node, you should have ovirt-host-deploy-offline installed: it should pull in all needed deps without installing anything else "manually".</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888">
Dan.<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org">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><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Sandro Bonazzola<br>Better technology. Faster innovation. Powered by community collaboration.<br>See how it works at <a href="http://redhat.com" target="_blank">redhat.com</a><br></div></div></div></div>
</div></div>