[meta] New Geo Testbed
Updated plan with smaller issues
Azure - geo1.gitlab.com:
-
~1d Create terraform configuration for Azure - https://gitlab.com/gitlab-com/infrastructure/issues/3090 -
~2d Create new chef environment for Geo testbed - https://gitlab.com/gitlab-com/infrastructure/issues/3091 -
~2d Setup NFS storage for the geo testbed in Azure (copy of nfs shards) - https://gitlab.com/gitlab-com/infrastructure/issues/3092 -
~1d Setup Uploads/Attachments for the geo testbed in Azure - https://gitlab.com/gitlab-com/infrastructure/issues/3093 -
~1d Setup Database that is pseudo-anonimized and only contains projects for the nfs shards -https://gitlab.com/gitlab-com/infrastructure/issues/3094 -
~1d Setup monitoring and alarming for the Azure testbed - https://gitlab.com/gitlab-com/infrastructure/issues/3095 -
~1d Setup automatic deploys for the Azure testbed - https://gitlab.com/gitlab-com/infrastructure/issues/3096
Azure - geo2.gitlab.com:
-
~1d Create terraform configuration for Azure - #3203 (closed) -
~2d Create new chef environment for Geo testbed - #3204 (closed) -
~2d Setup NFS storage - #3205 (closed) -
~1d Setup Uploads/Attachments - #3206 (closed) -
~1d Setup Database with disk config as geo1 - #3207 (closed) -
~1d Setup monitoring and alarming - #3208 (closed) -
~1d Setup automatic deploys - #3209 (closed)
Original issue
Per discussions a few days ago, we'd like to have a new Geo testbed (or upgrade the existing one) so that it has GitLab running in HA mode on both the primary and secondary, with at least two web workers on each side, and load balancer in front, to make sure that none of the Geo code / functionality bugs out in an HA setup.
Edited by Alex Hanselka