Untitled

Adding one more Gitaly EC2 instance to a GitLab infrastructure involves several steps to ensure it integrates seamlessly with the existing setup. Below is a detailed guide on how to achieve this:

### Prerequisites:
1. **Existing GitLab Infrastructure**: You should have a functioning GitLab infrastructure with at least one Gitaly EC2 instance.
2. **Access to AWS Management Console**: Permissions to launch and configure EC2 instances.
3. **SSH Access**: Ability to SSH into your EC2 instances.
4. **GitLab Configuration Access**: Permissions to modify GitLab configuration files.

### Steps to Add a New Gitaly EC2 Instance:

1. **Launch a New EC2 Instance**:
    - Go to the AWS Management Console.
    - Navigate to the EC2 dashboard.
    - Launch a new instance with the desired OS (e.g., Amazon Linux, Ubuntu).
    - Ensure the instance is in the same VPC and subnet as your existing Gitaly instance for network connectivity.
    - Assign appropriate security groups that allow communication between GitLab components.

2. **Install Gitaly on the New Instance**:
    - SSH into the new EC2 instance.
    - Install dependencies and Gitaly software. You can follow the installation guide from GitLab's official documentation:
      ```bash
      sudo apt-get update
      sudo apt-get install -y git gitaly
      ```
    - Ensure Gitaly is installed in the same version as the existing instance to avoid compatibility issues.

3. **Configure Gitaly on the New Instance**:
    - Create and configure the `gitaly.config.toml` file. This includes specifying the storage paths and other configurations:
      ```toml
      [socket]
      path = "/var/opt/gitlab/gitaly/gitaly.socket"

      [[storage]]
      name = "default"
      path = "/var/opt/gitlab/git-data"
      ```
    - Ensure the `storage` path matches the configuration of your existing Gitaly instance.

4. **Update GitLab Configuration to Include the New Gitaly Instance**:
    - SSH into the GitLab instance (or load balancer, depending on your setup).
    - Open the `gitlab.rb` file for editing:
      ```bash
      sudo vim /etc/gitlab/gitlab.rb
      ```
    - Add the new Gitaly instance under the `gitaly` configuration. Example:
      ```ruby
      gitlab_rails['repositories_storages'] = {
        "default" => {
          "gitaly_address" => "unix:/var/opt/gitlab/gitaly/gitaly.socket"
        },
        "gitaly-1" => {
          "gitaly_address" => "tcp://<new_gitaly_instance_ip>:8075"
        }
      }
      ```
    - Replace `<new_gitaly_instance_ip>` with the actual IP address of your new Gitaly EC2 instance.
    - Save the changes and exit the editor.

5. **Reconfigure and Restart GitLab**:
    - Reconfigure GitLab to apply the changes:
      ```bash
      sudo gitlab-ctl reconfigure
      ```
    - Restart GitLab services to ensure the new configuration is loaded:
      ```bash
      sudo gitlab-ctl restart
      ```

6. **Verify the Setup**:
    - Check the status of Gitaly instances:
      ```bash
      sudo gitlab-ctl status
      ```
    - Ensure both the old and new Gitaly instances are listed and running.
    - Check the logs for any errors:
      ```bash
      sudo gitlab-ctl tail gitaly
      ```

### Additional Considerations:
- **Load Balancing**: If you have multiple Gitaly instances, consider setting up load balancing to distribute requests efficiently.
- **Monitoring**: Ensure proper monitoring is in place to track the performance and health of the new Gitaly instance.
- **Backups**: Regularly back up Gitaly data to prevent data loss.

By following these steps, you should be able to successfully add a new Gitaly EC2 instance to your GitLab infrastructure, enhancing its scalability and reliability.