Please add new issues directly to https://gitlab.com/gitlab-org/gitlab-ee/issues/new and add the ~Geo label, ping @jramsay and/or @ernstvn 

Youtube link https://www.youtube.com/watch?v=eLu1SHlzgFM

Public url http://bit.ly/2AgbgTn 

Not done yet:

1. Vision https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2978
2. Store password https://gitlab.com/gitlab-org/gitlab-ee/issues/4253 10.5
3. Non geo work on links https://gitlab.com/gitlab-org/gitlab-ee/issues/4149 10.4

Notes

1. DONE Graphic in docs: server instead of team, people have moved :-)

1. https://gitlab.com/gitlab-org/gitlab-ee/issues/4106 

2. DONE Apt-get update missing from install docs https://about.gitlab.com/installation/#ubuntu 

1. sudo apt-get update
2. MR!8342 on www Sid: looks good

3. DONE Assume http if not specified when providing FQDN as arg to omnibus install

1. Dev ⇒ https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2969 , tentatively scheduled for 10.3
2. https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/2090 

4. (non-geo) Forgot password should be last tab

1. Dev => https://gitlab.com/gitlab-org/gitlab-ce/issues/40366 

5. DONE Add the license **on** the primary? (https://docs.gitlab.com/ee/gitlab-geo/README.html#using-omnibus-gitlab)

1. MR !3485 Sid: Looks good

6. DONE 20:45 mins: Docs typo: has already a replicator (./database.md)

1. MR !3485 Sid: Looks good

7. DONE 27:45 - 29:30 mins TLS db: "Unclear what can be skipped"...  (this should not be skipped in most cases)

1. docs: https://gitlab.com/gitlab-org/gitlab-ee/issues/4117 (closed) and https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2925 (10.3)
2. Choice will be removed with https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3547 (10.3)

8. DONE 29:58 mins Numbering restarts in db docs

1. MR !3485 Sid: Looks good

9. DONE Doc DB: inconsistent use of single and double quotes

1. MR !3485 Sid: Looks good

10. DONE add inline comment to make it clear which are primary and secondary IP for `md5_auth_cidr_addresses` and `trust_auth_cidr_addresses`

1. initial pass: docs https://gitlab.com/gitlab-org/gitlab-ee/issues/4116, but needs further attention.
2. Follow up in https://gitlab.com/gitlab-org/gitlab-ee/issues/4264 

11. IN ISSUE 38:30 mins Doc: add command to check they can connect to each other

1. docs and dev  "Firewall rules", step 5 "check to make sure your firewall rules are set so that the secondary nodes can access port..." https://gitlab.com/gitlab-org/gitlab-ee/issues/4150
2. Done in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3538/diffs  
3. => Sid: as discussed this should use a simple unix tool ⇒ new issue https://gitlab.com/gitlab-org/gitlab-ee/issues/4263 

12. DONE Doc: fix english about the fact reconfigure will fail and pg needs to be manually restarted

1. MR !3485 Sid: Looks good

13. DONE Doc: if it works on both external and internal IP choose a neutral term and be consistent

1. DONE docs https://gitlab.com/gitlab-org/gitlab-ee/issues/4137 scheduled for 10.3, but FYI:
2. further work done and needed on external vs internal IP; rather than being neutral, we'll focus on documenting objectively what we know about how this works for different providers.
3. Ernst: This is now a duplicate of 10.b., so will mark this as done.

14. DONE Interface: move the checkbox below the URL because the primary checkbox applies to the URL

1. https://gitlab.com/gitlab-org/gitlab-ee/issues/4113 

15. DONE Doc: Add comment: After adding the node will be “Unhealthy”, this is not a problem

1. docs https://gitlab.com/gitlab-org/gitlab-ee/issues/4138
2. Even better: solved entirely thanks to https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2797  

16. DONE Doc: help people check if ntp sync is enabled

1. MR !3485 Sid: Looks good

17. DONE Doc: use example.com rather than my.domain.com

1. MR !3485 Sid: Looks good

18. DONE Usability: provide a bypass for the 30 second wait

1. Ernst: my understanding is there is a bypass, but perhaps needs to be called out earlier in docs? => James: Sid was proposing that there would be a bypass command that could be executed during the 30 second wait so that if someone misses the
2. dev https://gitlab.com/gitlab-org/gitlab-ee/issues/4118

19. IN ISSUE Feedback: feels like doing the same step over and over again (terminal on primary, interface on primary, terminal on secondary),

1. Vision: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2978 

20. DONE Feedback: really work on making internal and external IP addresses clearer

1. Did https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3520
2. Will mark this one as DONE, because of duplication with 10 and 13. 

21. IN ISSUE Sid: I'm very confused what is in Omnibus, what is in the web interface, and what is on the command line.

1. Ernst: is this a documentation issue? => James: Partially yes. I think should help give the user a clearer overview of what they will be doing when. Secondarily we should try to prevent asking the user to jump in and out of the terminal and the web interface.
2. James: Ideally, the sys admin would be able to do everything in the the terminal for the primary, then everything in the secondary, then check the web interface.
3. Vision: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2978 

22. IN ISSUE Sid: (on the secondary) Why do I need to supply the replication user password again and again? Why can't it store that.

1. James: I think it makes sense that we don’t store it when the command fails.
2. Issue: https://gitlab.com/gitlab-org/gitlab-ee/issues/4253 not scheduled.

23. DONE Feedback: not clear that the replication error is saying the secondary is not permitted to read the primary db, looks like the error maybe relates to config on the secondary. Maybe add a tip: “check your trust addresses” => Sid: more explicit, check gitlab.rb on the primary for xxxxxxxxx postgresql[listen_addresss] => Sid: I didn’t buy pg, I bought GitLab. I don’t want to become pg expert

1. Issue: dev https://gitlab.com/gitlab-org/gitlab-ee/issues/4119 scheduled for 10.3
2. MR: https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/2120  

24. DONE Sid: Give command to check the connection between the machines (VPC, firewall). 

1. Ernst: duplicate of item 11 in this doc (minute 38:30). https://gitlab.com/gitlab-org/gitlab-ee/issues/4150 

25. DONE Doc: make secondary slot name look less like a domain name since it isn’t and colons etc are prohibited characters

1. MR !3485 Sid: Looks good

26. DONE Doc: confusing to have the list on every page and then send people back to the list of steps.

1. MR !3485 Sid: Looks good

27. DONE Doc: we should make sure none of the cli snippets contains leading spaces when copy/pasting

1. MR !3485 Sid: Looks good

28. DONE Doc: copy db into gitlab.rb, path to gitlab rb should be monospace formatted

1. MR !3485 Sid: Looks good

29. IN ISSUE 1:20:00 - 1:23:00 In /admin list repositories in statistics above forks

1. dev https://gitlab.com/gitlab-org/gitlab-ce/issues/40492  

30. IN ISSUE 1:23:55 Admin: link ‘Geo’ on the dashboard to ‘Geo Nodes’ admin page - and the same for other items

1. dev https://gitlab.com/gitlab-org/gitlab-ee/issues/4149 

31. DONE Ilya: maybe we can document how to export ip addresses to specific variables, and then let users copy paste a precreated `sed -i 's/match/replacement/'` commands with those variables? So that the whole "edit the file" can be avoided?

1. Ernst: No action, because seems that ideas in https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2978 will replace this. Ernst: Marking as DONE.

32. DONE Stan: ideally we should just have a primary and secondary IP list and then figure out these settings? => Sid: yes, should change gitlab.rb and add the server to the list in the interface.

1. https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2978  Ernst: Marking as DONE since issue made and duplicates other requests around making the setup much easier.

33. IN ISSUE Sid: Why did the new repository not show up in the interface? If that is caching how do we fix it? https://gitlab.slack.com/archives/C32LCGC1H/p1511211840000571 => https://gitlab.com/gitlab-org/gitlab-ee/issues/4126 ⇒ closed in favor of https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2925 
34. IN ISSUE Sid: Why do we have 3 mentions of 'NTP-compatible' in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3485/diffs ?

1. Ernst: actually it is 4. In https://docs.gitlab.com/ee/gitlab-geo/database.html#step-1-configure-the-primary-server, step 11 it is checked on the primary. Then it is also done on the secondary in step 7 of https://docs.gitlab.com/ee/gitlab-geo/database.html#step-3-configure-the-secondary-server. Similarly there is some duplication of these instructions in database_source.md.
2. Dry up the docs between database.md and database_source.md, made https://gitlab.com/gitlab-org/gitlab-ee/issues/4265 

35. IN ISSUE Sid: Can we stick to 'look up authorized ssh keys in the database' as the title everywhere?

1. Configure SSH authorizations to use the database https://docs.gitlab.com/ee/gitlab-geo/ 
2. GitLab Geo SSH access  https://docs.gitlab.com/ee/gitlab-geo/ssh.html
3. Speed up ssh https://docs.gitlab.com/ee/administration/operations/speed_up_ssh.html 
4. DONE: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3529
5. TODO: Rewrite / rename https://docs.gitlab.com/ee/administration/operations/speed_up_ssh.html so it refers to looking up authorized ssh keys in the database and does less explaining of the why.
6. Doc issue: https://gitlab.com/gitlab-org/gitlab-ee/issues/4267 

36. DONE Sid: https://docs.gitlab.com/ee/gitlab-geo/configuration.html feels like it is duplicating stuff from https://docs.gitlab.com/ee/gitlab-geo/#setup-instructions 

1. configuration pages greatly simplified in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3599 

37. DONE Sid: Get rid of the 'next steps' everywhere https://docs.gitlab.com/ee/gitlab-geo/ssh.html 

1. https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3529 

38. NOT DONE Sid: Link to https://docs.gitlab.com/ee/gitlab-geo/ssh.html should be a link to https://docs.gitlab.com/ee/administration/operations/speed_up_ssh.html 

1. https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3529 

39. DONE Sid: This isn't 'after setup', it is 'using a Geo server' https://docs.gitlab.com/ee/gitlab-geo/after_setup.html 

1. https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3528 

40. Please do not add more here, instead make issues in https://gitlab.com/gitlab-org/gitlab-ee/issues/new, add the ~Geo label, and ping @jramsay and/or @ernstvn.