| commit | 95eec26b0a90904ddd608106414e092bb7f9c4fb | [log] [tgz] |
|---|---|---|
| author | Fabio Ponciroli <ponch78@gmail.com> | Tue Jun 02 13:04:56 2020 +0200 |
| committer | Fabio Ponciroli <ponch78@gmail.com> | Thu Jun 04 17:23:49 2020 +0000 |
| tree | 7b8305607ebc0c54f4d7abf0780598a1f2d00cd1 | |
| parent | 907b7e3bbff201195f39c5c9b4a1b27fcc56971b [diff] |
Allow slave to run on multiple EC2 instances Currently git daemon, ssh agent and Gerrit are part of different tasks. When scaling up the number of instances in the cluster, the containers running the different services might end up in different EC2 instances. This wouldn't allow them to share the git volumes, preventing the slave service as a whole to work. This change group all the tasks together and adds a wait loop in the Gerrit startup script. This is not ideal, but it is the change with minimum impact on the current architecture. Bug: Issue 12848 Change-Id: Ia7b150b32554d025ebd48c69a3264477c23cf5dc
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.