Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
G
Gitlab Backup
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to JiHu GitLab
Provide feedback
Keyboard shortcuts
?
What's new
5
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
gitlab-cn
Gitlab Backup
Commits
e5b4895f
Commit
e5b4895f
authored
2 years ago
by
Michael Lussier
Committed by
Achilleas Pipinellis
2 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Add AWS ENI configuration as solution for retaining hostnames
parent
9ae140ca
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/update/with_downtime.md
+11
-7
11 additions, 7 deletions
doc/update/with_downtime.md
with
11 additions
and
7 deletions
doc/update/with_downtime.md
+
11
−
7
View file @
e5b4895f
...
...
@@ -68,13 +68,17 @@ following principles when upgrading those servers:
If you're running Gitaly cluster, follow the
[
zero downtime process
](
zero_downtime.md#gitaly-or-gitaly-cluster
)
for Gitaly cluster.
If you are using Amazon Machine Images (AMIs) on AWS, the Gitaly nodes
**should not be upgraded via the AMI process**
. Gitaly nodes should
**only**
be upgraded using the package upgrade because:
-
Praefect tracks replicas of Git repositories by server hostname.
-
Redeployment using AMIs issues the nodes with new hostnames.
-
Even though the storage is the same, Gitaly cluster does not work after this.
If you are using Amazon Machine Images (AMIs) on AWS, you can either upgrade the Gitaly nodes
through the AMI process, or upgrade the package itself:
-
If you're using the
[
Elastic network interfaces (ENI)
](
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html
)
,
you can upgrade through the AMI process. With ENI, you can keep the private DNS names
through AMI instance changes, something that is crucial for Gitaly to work.
-
If you're
**not**
using ENI, you must upgrade Gitaly using the GitLab package.
This is because Gitaly Cluster tracks replicas of Git repositories by the server hostname,
and a redeployment using AMIs issues the nodes with new hostnames. Even though
the storage is the same, Gitaly Cluster does not work when the hostnames change.
The Praefect nodes, however, can be upgraded via an AMI redeployment process:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment