commit | 5d70d7e73dfbe1b7135db53c52d2236d218910c0 | [log] [tgz] |
---|---|---|
author | Fabio Ponciroli <ponch78@gmail.com> | Fri Jun 12 10:48:05 2020 +0200 |
committer | Luca Milanesio <luca.milanesio@gmail.com> | Tue Jun 16 23:24:04 2020 +0000 |
tree | c1bf59bbea16fa877dc90347dde04235df2b4e79 | |
parent | 90bc0995a1576238fba20d3582f3a998092e7f24 [diff] |
Better resource assignment for dual master Default instance type (m4.2xlarge) have 8192 vCPU units each. Assign more resource for a more realistic setup: Master 1: 3072 Master 2: 3072 Load balancer: 1024 Sidecar logs: 256 Slave: 3072 Git daemon: 256 Ssh agent: 256 With this assignemt the containers will be spreaded on all the nodes of the cluster. Feature: Issue 12916 Change-Id: I4007184aedd741aa70fba2f02d6e5d8821502a6b
Those are a collection of AWS CloudFormation templates and scripts to deploy Gerrit in AWS.
The aim is to provide some guidelines and example on how to deploy different Gerrit setups in the Cloud using AWS as provider.
The goal of Gerrit AWS Templates is to provide fully-functional Gerrit installations to helps users deploying Gerrit on AWS by providing out-of-the-box templates.
With Gerrit AWS Templates, developers and administrator can create a production-ready installation on the cloud in minutes and in a repeatable way, allowing them to focus on fine tuning of the Gerrit configuration to suit the user needs.
The provided CloudFormation templates automate the entire creation and deployment of the infrastructure and the application.
To manage your AWS services via command line you will need to install AWS CLI and set it up to point to your account.