[Google] GitLab Geo Deployment Storage and Network considerations in GCP
Note: Please scrub any customer reference and/or sensitive user information in this issue. Currently this is a public issue.
@fabian Wanted to give you a heads up, I have an inbound joint opportunity with a customer that have Geo set up in their POC running on Google Cloud.
We are engaged and looking for a technical consultation form GitLab PM regarding storage requirements/configurations for Geo across multiple sites. Looping you into the email thread now but hope to track progress in this thread for future reference if anyone else finds the discussion useful.
Wanted to check here first if there is a reference architecture that focuses around storage config/requirements for cloud deployments. Here is the ask as I understand it. We want to slate a call to discuss further:
-
Partner wants to talk about the GCS + Gitlab design especially around replication and how this work with Geo and also some tips on performance tuning to take advantage of the GCP backbone.
-
For the POC we want to validate GCS integration for LFS objects and also fine tune the file replication. So far with TCP tuning @ os level we were able to get .5 Gb/sec , whereas the VM's can technically handle 2Gb/sec`
cc - @Nico @mcesario do you have a link to the SFDC opportunity by chance?