<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>
<div><br></div><div>What he said</div><div><br></div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757">Happy Connecting. Sent from my Sprint Samsung Galaxy S® 5</div></div><br><br>-------- Original message --------<br>From: Scott Worthington <scott.c.worthington@gmail.com> <br>Date: 02/18/2015 2:03 PM (GMT-07:00) <br>To: Donny D <donny@cloudspin.me> <br>Subject: Re: [ovirt-users] ovirt and glusterfs setup <br><br>> I did not have a good experience putting both gluster and virt on the same<br>> node. I was doing hosted engine with replicate across two nodes, and one day<br>> it went into split brain hell... i was never able to track down why. However<br>> i do have a gluster with distribute and replica setup on its own with a<br>> couple nodes, and it has given me zero problems in the last 60 days. It<br>> seems to me that gluster and virt need to stay seperate for now. Both are<br>> great products and both work as described, just not on the same node at the<br>> same time.<br>><br><br>The issue, as I perceive it, is newbies find Jason Brook's blog:<br> http://community.redhat.com/blog/2014/11/up-and-running-with-ovirt-3-5-part-two/<br><br>And then newbies think this Red Hat blog is production quality. In my<br>opinion, the blog how-to is okay (not really, IMHO) for a lab, but not for<br>production.<br><br>Since fencing is important in oVirt, having gluster on the hosts is a no-no<br>since a non-responsive host could be fenced at any time -- and the engine<br>could fence multiple hosts (and bork a locally hosted gluster file system and<br>then screw up the entire gluster cluster).<br><br>--ScottW<br></body></html>