<div dir="ltr">Hello!<div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 25, 2017 at 1:40 PM, Ralf Schenk <span dir="ltr"><<a href="mailto:rs@databay.de" target="_blank">rs@databay.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p><font face="Helvetica, Arial, sans-serif">Hello,<br>
</font></p>
<p><font face="Helvetica, Arial, sans-serif">I'm using the DNS Balancing
gluster hostname for years now, not only with ovirt. No software
so far had a problem. And setting the hostname to only one Host
of course breaks one advantage of a distributed/replicated
Cluster File-System like loadbalancing the connections to the
storage and/or failover if one host is missing. In earlier ovirt
it wasn't possible to specify something like "backupvolfile-server"
for a High-Available hosted-engine rollout (which I use).</font></p></div></blockquote><div><br></div><div>As far as i know, <span style="color:rgb(0,0,0);white-space:pre-wrap">backup-volfile-servers is a recommended way to keep you filesystem mountable in case of server failure. While fs is mounted, gluster will automatically provide failover. And you definitely can specify </span><span style="color:rgb(0,0,0);white-space:pre-wrap">backup-volfile-servers in the storage domain configuration.</span></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">
<p><font face="Helvetica, Arial, sans-serif">I already used live
migration in such a setup. This was done with pure libvirt
setup/virsh and later using OpenNebula.</font></p><p><font face="Helvetica, Arial, sans-serif"><br></font></p></div></blockquote><div>Yes, but it was based on a accessing gluster volume as a mount filesystem, not directly... And i would like to exclude that from list of possible causes.</div></div><br></div></div>