| commit | fab72542afd4b12d76d77cc4a873e152bbd523cd | [log] [tgz] |
|---|---|---|
| author | Antonio Barone <syntonyze@gmail.com> | Mon Oct 04 18:09:56 2021 +0200 |
| committer | Antonio Barone <syntonyze@gmail.com> | Wed Oct 06 11:50:42 2021 +0200 |
| tree | d570e62a0ff3d6cc6ec51bc92da18ad422e511dd | |
| parent | c9ff592a14d2b99a4dcb93a4be1ea66858072618 [diff] |
Add active-active network load balancer Register both gerrit-1 and gerrit-2 behind the same network load balancer to allow serving traffic in an active-active architecture. To allow so, both gerrit-1 and gerrit-2 needs to expose the same host ports in order to allow traffic forwarding from the same SSH and HTTP listeners. For this reason the HTTP_HOST_PORT_PRIMARY and SSH_HOST_PORT_PRIMARY variables have been removed, as effectively redundant. A new PRIMARIES_GERRIT_SUBDOMAIN variable has been introduced so that the active-active subdomain can be configured. Note that whilst the haproxy is still installed and available, the ultimate goal is to remove it and to allow _only_ active/active traffic to go through the newly introduced load balancer. Before doing that however a global-refdb needs to be introduced and target groups need to be configured to maintain sticky sessions. Bug: Issue 15128 Change-Id: I0ba035d4570ca77b1193c46bb612b2c6ea28d0fb
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.
To build gerrit and related-components' images Docker
To manipulate aws cloudformation outputs jq
This is a list of external services that you might need to setup your stack and some suggestions on how to easily create them.
If you need to setup a SMTP service Amazon Simple Email Service can be used. Details how setup Amazon SES can be found here.
To correctly setup email notifications Gerrit requires ssl protocol on default port 465 to be enabled on SMTP Server. It is possible to setup Gerrit to talk to standard SMTP port 25 but by default all EC2 instances are blocking it. To enable port 25 please follow this link.
If you need a testing LDAP server you can find details on how to easily create one in the LDAP folder.
All recipes stream every log to CloudWatch. This always includes sshd_log, httpd_log and gc_log.
The ‘error_log’ might or might not be available depending on which version of gerrit is being deployed. From gerrit 3.3 it will always be available. Prior to that it will be available from:
When the error_log is not available, Gerrit will still output the same content to standard error. Refer to the standard error section.
Different recipes deploy different services to ECS (please refer to the documentation of each recipe for details on what services are actually deployed).
Every ECS service will stream anything outputted to stderr to cloudwatch, to a stream name that will take the form of:
{environmentName}/{serviceName}/{taskId}
For example, given the gerrit-primary service running task bb21cb504ca44150b770ca05e922e332, on the test environment, the stderr will be streamed to:
test/gerrit-primary/bb21cb504ca44150b770ca05e922e332
The task name can be found in the Amazon ECS console's Task section.
A set of utilities to perform operational tasks is also provided. Refer to the relevant documentation for details on this.