<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""></blockquote><div class="">2(a). Can I just disable ovirt-imageio-proxy somewhere? Is this just supposed to make uploading ISO images simpler? I don't really need this.<br class=""></div><div class="">2(b). Do I need to have DWH enabled? I am not certain when this was added into my hosted-engine setup, but I don't think I need it.</div><div class=""><div class=""><br class=""></div><div class="">3. My vdsm.log is full of entries like, "JsonRpc (StompReactor)::ERROR::2016-08-18 12:59:56,783::betterAsyncore::113::vds.dispatcher::(recv) SSL error during reading data: unexpected eof"</div><div class=""><br class=""></div><div class="">4. Commands throwing deprecation warning. Example:</div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class="">[root@cultivar2 ~]# hosted-engine --vm-status</div></div><div class=""><div class="">/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py:15: DeprecationWarning: vdscli uses xmlrpc. since ovirt 3.6 xmlrpc is deprecated, please use vdsm.jsonrpcvdscli</div></div><div class=""><div class=""> import vdsm.vdscli</div></div></blockquote>or in the logs:</div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">Aug 18 13:56:17 cultivar3 ovirt-ha-agent: /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead.</div></blockquote><div class=""><div class=""><br class="webkit-block-placeholder"></div><div class="">5. This error in the console: "ETL service sampling has encountered an error. Please consult the service log for more details." ETL service sampling log? Where's that?</div><div class=""><br class=""></div><div class="">6. The host that is running the NFS server had network issues on Monday and I have had to remove it from the cluster. It was working fine up until I did the lastest yum updates. The networking just stopped working when vdsm restarted. Could this be related to my switching the cluster "Switch type" to OVS from Legacy? I have since switched it back to Legacy. I'm going to completely remove oVirt and reinstall/re-add it to the cluster. As it is the NFS server, I do need the network to continue to function throughout the process. Any advice would be appreciated.</div><div class=""><br class=""></div><div class="">Lastly... If I clear up the above, how feasible is it to GoGO GlusterFS instead of my existing straight NFS server setup that I have now? Any advice on how to best move my hosted_engine, data, ISO, export Storage Domains to Gluster?</div><div class=""><br class="webkit-block-placeholder"></div><div class=""><div id="signature" class="">Cheers,<br class="">Gervais<br class=""><br class=""><br class=""></div>
</div>
<br class=""></div></body></html>