Add support for running GitLab Geo tracking database

Secondary Geo Nodes will need a separate PostgreSQL tracking database to store progress. This MR depends on https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1197.

/cc: @brodock, @dbalexandre

added 1 commit

• a25a387e - Add missing bootstrap-geo script

Compare with previous version

added 1 commit

• 89023c09 - Fix paths for GitLab Geo DB example file

Compare with previous version

added 1 commit

• 2b7f34bd - Use geo:db:setup instead of geo:db:create

Compare with previous version

added 1 commit

• 42267cbc - Don't attempt to run other PostgreSQL tasks in geo-setup task

Compare with previous version

mentioned in merge request !270 (merged)

assigned to @rspeicher

added 56 commits

• 42267cbc...d1e3b49e - 50 commits from branch master
• aaf47c7b - Add support for running GitLab Geo tracking database
• 9d620ffd - Add missing bootstrap-geo script
• 88ad250c - Fix paths for GitLab Geo DB example file
• d6544162 - Use geo:db:setup instead of geo:db:create
• b0feff0f - Fix typo in Procfile fix
• cc3c55df - Don't attempt to run other PostgreSQL tasks in geo-setup task

Compare with previous version

Rebased to bring in changes from https://gitlab.com/gitlab-org/gitlab-development-kit/merge_requests/270 and resolved conflicts in Makefile.

@stanhu How does this behave when the GDK is using the CE source rather than EE?

@rspeicher I think even if the DB is enabled, CE won't even try to talk to it, so there are no issues there. I think geo-setup should probably be an optional step, not a mandatory one.

@stanhu I agree, in which case I should move it out of all and add a manual step to the guide for setting up Geo, right?

@rspeicher Yes.

mentioned in issue #195 (closed)

added 2 commits

• f244a8d3 - Ignore postgresql-geo folder created by geo-setup target
• 3b339c4b - The geo-setup target is now an optional/manual step

Compare with previous version

Currently this is only performed in the secondary (gdk-geo) instance, but I'm not sure if that's correct.

How does the replica get set up?

@stanhu That's part of the next instruction, where they follow the replication guide.

Do we need to do this after replication setup?

Just noticed the intro for that guide is missing some information, opened https://gitlab.com/gitlab-org/gitlab-development-kit/merge_requests/285 to address.

@stanhu Updated to make geo-setup optional, please take a look.

assigned to @stanhu

Looks good.

enabled an automatic merge when the pipeline for 3b339c4b succeeds

merged

mentioned in commit 66776ba9