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
0
Merge Requests
0
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
Boxiang Sun
gitlab-ce
Commits
cc735352
Commit
cc735352
authored
Dec 11, 2018
by
Jacob Vosmaer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document gitaly network architecture
parent
18a48e34
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
19 additions
and
0 deletions
+19
-0
doc/administration/gitaly/index.md
doc/administration/gitaly/index.md
+19
-0
No files found.
doc/administration/gitaly/index.md
View file @
cc735352
...
@@ -49,6 +49,25 @@ Starting with GitLab 11.4, Gitaly is a replacement for NFS except
...
@@ -49,6 +49,25 @@ Starting with GitLab 11.4, Gitaly is a replacement for NFS except
when the
[
Elastic Search indexer
](
https://gitlab.com/gitlab-org/gitlab-elasticsearch-indexer
)
when the
[
Elastic Search indexer
](
https://gitlab.com/gitlab-org/gitlab-elasticsearch-indexer
)
is used.
is used.
### Network architecture
-
gitlab-rails shards repositories into "repository storages"
-
gitlab-rails/config/gitlab.yml contains a map from storage names to
(Gitaly address, Gitaly token) pairs
-
the
`storage name`
-
\>
`(Gitaly address, Gitaly token)`
map in
gitlab.yml is the single source of truth for the Gitaly network
topology
-
a (Gitaly address, Gitaly token) corresponds to a Gitaly server
-
a Gitaly server hosts one or more storages
-
Gitaly addresses must be specified in such a way that they resolve
correctly for ALL Gitaly clients
-
Gitaly clients are: unicorn, sidekiq, gitlab-workhorse,
gitlab-shell, and Gitaly itself
-
special case: a Gitaly server must be able to make RPC calls
**
to
itself
**
via its own (Gitaly address, Gitaly token) pair as
specified in gitlab-rails/config/gitlab.yml
-
Gitaly servers must not be exposed to the public internet
Gitaly network traffic is unencrypted so you should use a firewall to
Gitaly network traffic is unencrypted so you should use a firewall to
restrict access to your Gitaly server.
restrict access to your Gitaly server.
...
...
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