Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
cae6e93e
Commit
cae6e93e
authored
Oct 26, 2016
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add info about adding the SSH fingerprint to Geo nodes
parent
e45d0c76
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
27 additions
and
9 deletions
+27
-9
doc/gitlab-geo/configuration.md
doc/gitlab-geo/configuration.md
+27
-9
No files found.
doc/gitlab-geo/configuration.md
View file @
cae6e93e
...
...
@@ -8,10 +8,10 @@ After having installed GitLab Enterprise Edition in the instance that will serve
as a Geo node and set up the database replication, the next steps can be summed
up to:
-
c
onfigure the primary node
-
r
eplicate some required configurations between the primary and the secondaries
-
s
tart GitLab in the secondary node's machine
-
c
onfigure every secondary node in the primary's Admin screen
1.
C
onfigure the primary node
1.
R
eplicate some required configurations between the primary and the secondaries
1.
S
tart GitLab in the secondary node's machine
1.
C
onfigure every secondary node in the primary's Admin screen
After GitLab's instance is online and defined in
**Geo Nodes**
admin screen,
new data will start to be automatically replicated, but you still need to copy
...
...
@@ -191,11 +191,7 @@ user will act as a "normal user" who fetches from the primary Geo node.
1.
Copy them to the admin area of the
**primary**
node (
**Admin Area > Geo Nodes**
).
Remember to add your primary node to the
`known_hosts`
file of your
`git`
user.
You can find ssh key files and
`know_hosts`
at
`/var/opt/gitlab/.ssh/`
in
Omnibus installations or at
`/home/git/.ssh/`
when following the source
installation guide.
---
If for any reason you generate the key using a different name from the default
`id_rsa`
, or you want to generate an extra key only for the repository
...
...
@@ -217,6 +213,28 @@ Host example.com # The FQDN of the primary Geo node
IdentityFile ~/.ssh/mycustom.key
# The location of your private key
```
### Add the primary node to the `known_hosts` file of the secondary nodes
>**Note:**
This operation is only needed for the secondary nodes.
---
The secondary nodes need to know the SSH fingerprint of the primary node that
will be used for the Git clone/fetch operations. In order to add it to the
`known_hosts`
file, while in the terminal of a secondary node, run the
following command and type
`yes`
when asked:
```
sudo -u git -H ssh git@<primary-node-url>
```
Replace
`<primary-node-url>`
with the FQDN of the primary node. You can verify
that the fingerprint was added by checking:
-
`/var/opt/gitlab/.ssh/known_hosts`
for Omnibus installations or
-
`/home/git/.ssh/known_hosts`
for installations from source
## Troubleshooting
Setting up Geo requires careful attention to details and sometimes it's easy to
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment