Merge branch 'docs/geo' into 'master'

Documentation updates for new Geo features

See merge request !1470

doc/gitlab-geo/configuration.md

@@ -187,10 +187,28 @@ The two most obvious issues that replication can have here are:
 ### Step 5. Replicating the repositories data
 
 Getting a new secondary Geo node up and running, will also require the
-repositories directory to be synced from the primary node.
+repositories data to be synced.
 
-With GitLab **8.14** you can start the syncing process by clicking the
-"Backfill all repositories" button on `Admin > Geo Nodes` screen. 
+With GitLab **9.0** the syncing process starts automatically from the
+secondary node after the **Add Node** button is pressed.
+
+Currently, this is what is synced:
+
+* Git repositories
+* Wikis
+* LFS objects
+
+You can monitor the status of the syncing process on a secondary node
+by visiting the primary node's **Admin Area ➔ Geo Nodes** (`/admin/geo_nodes`)
+in your browser.
+
+![GitLab Geo dashboard](img/geo-node-dashboard.png)
+
+Disabling a secondary node stops the syncing process.
+
+With GitLab **8.14** this process is started manually from the primary node.
+You can start the syncing process by clicking the "Backfill all repositories"
+button on `Admin > Geo Nodes` screen.
 
 On previous versions, you can use `rsync` for that:
 

doc/gitlab-geo/faq.md

@@ -12,12 +12,12 @@ manually [promote a secondary node](disaster-recovery.md) into primary.
 
 ## What data is replicated to a secondary node?
 
-We currently replicate project repositories and the whole database. This
-means user accounts, issues, merge requests, groups, project data, etc.,
-will be available for query.
+We currently replicate project repositories, LFS objects and the whole
+database. This means user accounts, issues, merge requests, groups, project
+data, etc., will be available for query.
 We currently don't replicate user generated attachments / avatars or any
-other file in `public/upload`. We also don't replicate LFS or
-artifacts data (`shared/folder`).
+other file in `public/upload`. We also don't replicate artifact data
+data (`shared/folder`).
 
 ## Can I git push to a secondary node?
 

doc/gitlab-geo/troubleshooting.md

@@ -49,3 +49,14 @@ where you have to fix (all commands and path locations are for Omnibus installs)
         ```
         # remove old entries to your primary gitlab in known_hosts
         ssh-keyscan -R your-primary-gitlab.example.com
+
+Visit the primary node's **Admin Area ➔ Geo Nodes** (`/admin/geo_nodes`) in
+your browser. We perform the following health checks on each secondary node
+to help identify if something is wrong:
+
+- Is the node running?
+- Is the node's secondary tracking database configured?
+- Is the node's secondary tracking database connected?
+- Is the node's secondary tracking database up-to-date?
+
+![GitLab Geo health check](img/geo-node-healthcheck.png)