title: What is the benefit of convoy-glusterfs over pure glusterfs
body: <p>I have a problem to see the benefit of glusterfs with convoy over pure glusterfs</p>
  
  <p>Our starting position:</p>
  
  <ul>
  <li>we just use convoy of rancher, nothing else </li>
  <li>we have glusterfs setup for persistent data </li>
  </ul>
  
  <p>Setup without convoy</p>
  
  <ul>
  <li>Mount glusterfs volume on each docker host</li>
  <li>create services with docker swarm and mount them to the right directory on the host, which hosts in the background to glusterfs</li>
  </ul>
  
  <p>Setup with convoy</p>
  
  <ul>
  <li>Run the convoy deamon on ever dockerhost (which mounts the glusterfs volume in the background)</li>
  <li>create services with docker swarm and attach a volume to it over the convoy </li>
  <li>volume-driver, which is maped to a glusterfs directory in the background</li>
  </ul>
  
  <p>So, what is the benefit of starting a deamon (convoy), which does the mounting in the background, when I can do the mounting myself over /etc/fstab</p>