<div dir="ltr">Hi Alessandro,<div><br></div><div>That will address the failover issue but it will not address configuring the glusterfs client to connect to the brick over TLS. I would be happy to be wrong. I was only able to get both by specifying that in the config file. What&#39;s curious is why the config file doesn&#39;t handle replication the same way as when its mounted with the mount command. I&#39;d figure they should be the same.</div><div><br></div><div>Here&#39;s my config file if anyone is interested. Perhaps I don&#39;t have something set properly?</div><div><br></div><div>







<p class="gmail-p1"><span class="gmail-s1"> volume gv0-client-0</span></p>
<p class="gmail-p1"><span class="gmail-s1">     type protocol/client</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option ping-timeout 42</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option remote-host host1</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option remote-subvolume /data/glusterfs/gv0/brick1/brick</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option transport-type socket</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option transport.address-family inet</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option send-gids true</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option transport.socket.ssl-enabled on</span></p>
<p class="gmail-p1"><span class="gmail-s1"> end-volume</span></p>
<p class="gmail-p1"><span class="gmail-s1"> volume gv0-client-1</span></p>
<p class="gmail-p1"><span class="gmail-s1">     type protocol/client</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option ping-timeout 42</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option remote-host host2</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option remote-subvolume /data/glusterfs/gv0/brick1/brick</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option transport-type socket</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option transport.address-family inet</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option send-gids true</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option transport.socket.ssl-enabled on</span></p>
<p class="gmail-p1"><span class="gmail-s1"> end-volume</span></p>
<p class="gmail-p1"><span class="gmail-s1"> volume gv0-client-2</span></p>
<p class="gmail-p1"><span class="gmail-s1">     type protocol/client</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option ping-timeout 42</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option remote-host host3</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option remote-subvolume /data/glusterfs/gv0/brick1/brick</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option transport-type socket</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option transport.address-family inet</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option send-gids true</span></p>
<p class="gmail-p1"><span class="gmail-s1">     option transport.socket.ssl-enabled on</span></p>
<p class="gmail-p1"><span class="gmail-s1"> end-volume</span></p>
<p class="gmail-p1"><span class="gmail-s1"> volume gv0-replicate-0</span></p>
<p class="gmail-p1"><span class="gmail-s1">    type cluster/replicate</span></p>
<p class="gmail-p1"><span class="gmail-s1">    subvolumes gv0-client-0 gv0-client-1 gv0-client-2</span></p>
<p class="gmail-p1"><span class="gmail-s1"> end-volume</span></p></div><div><br></div><div>Joe </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 24, 2017 at 11:40 AM, Alessandro Briosi <span dir="ltr">&lt;<a href="mailto:ab1@metalit.com" target="_blank">ab1@metalit.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000"><span class="">
    <div class="m_3468891159034752708moz-cite-prefix">Il 24/02/2017 14:50, Joseph Lorenzini
      ha scritto:<br>
    </div>
    <blockquote type="cite">
      <div>1. I want the mount /etc/fstab to be able to fail over to any
        one of the three servers that I have. so if one server is down,
        the client can still mount from servers 2 and 3.</div>
    </blockquote>
    </span><strong>backupvolfile-server </strong>option<br>
    <strong><br>
    </strong>should do the work or use the config file.<br>
    <br>
    It&#39;s mentioned in the blog you linked...<br>
    <br>
    If you need more dynamic failover probably rrdns could be a
    solution.<span class="HOEnZb"><font color="#888888"><br>
    <br>
    <div class="m_3468891159034752708moz-signature"><br>
      Alessandro</div>
  </font></span></div>

</blockquote></div><br></div>