diff options
author | Sytse Sijbrandij <sytse@gitlab.com> | 2016-12-28 14:37:54 +0300 |
---|---|---|
committer | Sytse Sijbrandij <sytse@gitlab.com> | 2016-12-28 14:37:54 +0300 |
commit | 850ee2eb96937429ca1c91c22093cf1b3e0e9f0a (patch) | |
tree | e1c8d45be7084a139b8b4310c159277e3bbd08b3 | |
parent | c918f3fdd92858927e245c6a9ba78e20d020e25d (diff) |
Flatten plan.
-rw-r--r-- | README.md | 7 |
1 files changed, 4 insertions, 3 deletions
@@ -101,9 +101,10 @@ We use our issues board for keeping our work in progress up to date in a single 1. [Absorb gitlab_git](https://gitlab.com/gitlab-org/gitlab-ce/issues/24374) 1. [Milestone 0.0.1](https://gitlab.com/gitlab-org/gitaly/milestones/2) 1. [Move more functions in accordance with the iterate process, starting with the ones with have the highest impact.](https://gitlab.com/gitlab-org/gitaly/issues/13) -1. [Move to Git RPC, we should already have Gitaly calls everywhere but move from a local socket to non-local one.](https://gitlab.com/gitlab-org/gitaly/issues/30) -1. [Move Gitaly where the file servers that become git servers, halving the amount of IOPS, reducing latency greatly, and allowing workers to keep serving requests.](https://gitlab.com/gitlab-org/gitaly/issues/26) -1. [No longer mount the NFS shares](https://gitlab.com/gitlab-org/gitaly/issues/27) +1. [Change the connection on the workers from a unix socket to an actual TCP socket to reach Gitaly](https://gitlab.com/gitlab-org/gitaly/issues/29) +1. [Build Gitaly fleet that will have the NFS mount points and will run Gitaly](https://gitlab.com/gitlab-org/gitaly/issues/28) +1. [Move to GitRPC model where GitLab is not accessing git directly but through Gitaly](https://gitlab.com/gitlab-org/gitaly/issues/30) +1. [Remove the git NFS mount points from the worker fleet](https://gitlab.com/gitlab-org/gitaly/issues/27) 1. [Remove gitlab git from Gitlab Rails](https://gitlab.com/gitlab-org/gitaly/issues/31) 1. [Move to active-active with Git Ketch, with this we can read from any node, greatly reducing the number of IOPS on the leader.](https://gitlab.com/gitlab-org/gitlab-ee/issues/1381) 1. [Move to the most performant and cost effective cloud](https://gitlab.com/gitlab-com/infrastructure/issues/934) |