3 ms·

Thanks, you can indeed do HA this way. When Gitaly 1.0 lands you won't have to mount the NFS volumes on the application servers anymore as everything will go o

by sytse 8y ago

Thanks, you can indeed do HA this way. When Gitaly 1.0 lands you won't have to mount the NFS volumes on the application servers anymore as everything will go over gRPC.

avar 8y ago
That just splits up the task of application server & git executor into two, it doesn't get rid of the dependency on a monolithic storage backend. I understand that this is something gitlab.com is working towards and excited about, presumably because it'll allow for provisioning web workers unrelated to the CPU you're spending on running git, but for us I don't see it being useful. I hope GitLab eventually gets something like GitHub Spokes[1] which'll allow for provisioning the entire setup on a bunch of dumb boxes with RAID 0. 1. https://githubengineering.com/introducing-dgit/ https://githubengineering.com/introducing-dgit/
- sytse 8y ago
  The advantage is that if one storage nose is offline the rest of the site can still function. Spokes is more elaborate can can deal with node failure. We plan to rely on cloud storage so we can quickly attach a new VM with Gitaly.