<div dir="ltr">Thanks to everyone for the answers. That helps clarify some basics for me. I prefer to try and implement ovirt-node for the reasons stated above (small, defined OS with a smaller security/management footprint), but now I debate using CentOS 6 or RHEL 6. I feel that oVirt-node is very important to being able to get an environment up and running securely without too much overhead, but perhaps I need to consider minimal OS installs + latest gluster release + 3.5 oVirt at this time.<div><br></div><div>One thing I was curious about is gluster support in oVirt-node. What is the current status as far as glusterfs version and saving settings, etc.?</div><div><br></div><div>Thanks again!</div><div><br></div><div>Chris</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 14, 2014 at 6:30 AM, Fabian Deutsch <span dir="ltr"><<a href="mailto:fdeutsch@redhat.com" target="_blank">fdeutsch@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="">----- Original Message -----<br>
> I sincerely hope that this is not answered elsewhere as I've done several<br>
> searches and have yet to find a solid answer. I have three (what I believe<br>
> to be) basic questions (with perhaps some subs there):<br>
><br>
> 1) What is the latest oVirt-node release and where would one download it<br>
> (I appear to only see 3.4 -based releases of the ISO available)? It is<br>
> 3.5-based and/or is there an upgrade path? Which glusterfs release is<br>
> currently included with oVirt-node?<br>
<br>
</span>Hey,<br>
<br>
there are some 3.5 pre-release isos available here:<br>
<a href="http://resources.ovirt.org/pub/ovirt-3.5-pre/iso/" target="_blank">http://resources.ovirt.org/pub/ovirt-3.5-pre/iso/</a><br>
<br>
They are quite old. The reason why there is still no Node, is that we are experiencing<br>
installation problems after CentOS 6.6 got released.<br>
<br>
That is why there is no Node for 3.5 yet, becuase we don't want to provide<br>
a Node which is dead on arrival. This ain't fun for anyone.<br>
<span class=""><br>
> 2) As I understand it, newer releases of oVirt-node allow you to do an<br>
> installation of the self-hosted engine at this time. Is that correct?<br>
<br>
</span>Yes, that will work. Due to problems mentioned above, we still need to do some<br>
fixes to the hosted-engine part of Node, but once they land, HE will work on Node.<br>
<span class=""><br>
> 3) Is there any functionality that one would be losing out on by deploying<br>
> oVirt via oVirt-node vs. using full-OS installation? Which is the more<br>
> recommended?<br>
<br>
</span>Yes, ovirt-node is not as customizable as a regular host.<br>
I.e. you can not (easily) modify the boot process, or install custom rpms.<br>
<br>
Sometimes this is seen as a restriction, other see this as a well defined<br>
environment.<br>
<span class=""><br>
> Again, I apologize if these questions are covered somewhere, but I felt<br>
> like asking them in a direct fashion so as to clear up my own ignorance. I<br>
> appreciate any feedback and information that you could share.<br>
<br>
</span>No, no worries. There weren't any Node updates (besides the weekly meeting minutes)<br>
for a while.<br>
<br>
We still traget to release Node for oVirt 3.5 ASAP.<br>
<br>
- fabian<br>
<br>
<br>
> Thanks,<br>
><br>
> Chris<br>
<div class="HOEnZb"><div class="h5">><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
><br>
</div></div></blockquote></div><br></div>