Make it easier to set up GitLab Geo with the GDK

Right now it's a bit challenging to set up a primary and secondary GitLab Geo with the GDK. The PostgreSQL replication instructions really helped, but there were additional steps on a brand new machine that had rbenv installed with the GDK:

1. Installed nginx on both primary and secondary machines via apt-get install nginx

2. Stopped the default system nginx via sudo systemctl stop nginx

3. Configured the nginx.conf on port 80 (SSL appears to be configured by default) to forward Workhorse connections (my EE is on port 3001, but nginx was in port 3000)

4. Enabled nginx in the GDK Procfile. Added a sudo step since I wanted nginx to listen on port 80.

5. Configured the GDK OpenSSH to listen on all interfaces on port 2222 (by default only listens to localhost:2222)

6. On both primary and secondary nodes, in gitlab.yml under the SSH configuration, replaced localhost with the full hostname.

7. Started up both GDKs.

8. Ran rake cache:clear on the primary to make the SSH config appear

9. Added a primary Geo Node in the GitLab UI with the public SSH key in /home/stanhu/gdk-ee/openssh/ssh_host_rsa_key.pub

10. Created an SSH key in my home directory

11. Added a secondary Geo Node in the GitLab UI with the public SSH key of my user's SSH key in /home/stanhu/.ssh/id_rsa.pub (notice the paths are quite different from step 9)

12. Attempted to test my SSH connection, but got:

    $ ssh stanhu@stanhu-geo-primary -p 2222
    PTY allocation request failed on channel 0
    /usr/bin/env: 'ruby': No such file or directory
    Connection to stanhu-geo-primary closed.

13. Realized I need to install the system ruby package instead of relying on rbenv via apt-get install ruby.

14. Had failures with system hooks. Copied config/secrets.yml from the primary to the secondary.

/cc: @brodock, @dbalexandre, @rspeicher

@stanhu I'm wondering if setting up an entirely separate machine is normal/expected for Geo development. I'd expect a setup that uses two separate GDK folders on the same machine to work as well.

@rspeicher That may be simpler indeed, but I put the two VMs in different continents to test how latency/downloads would actually work in practice.

@stanhu Ok, for that kind of testing that makes perfect sense.

I'm still anxious to find out how @brodock has things set up for two instances on the same development machine.

@rspeicher its taking longer than expected to have the extra time to migrate to GDK and I also lost the initial notes I've made so hope to get this done on Monday.

@rspeicher shall we close this?

@regisF We've still got https://gitlab.com/gitlab-org/gitlab-development-kit/merge_requests/258 to merge, and then I think we can close. I'll assign to myself until then.

assigned to @rspeicher

!258 (merged) was merged, closing this.

closed