commit | b92444bef3da87e1f8f767106849bdf6fbe3034a | [log] [tgz] |
---|---|---|
author | Marco Miller <marco.miller@ericsson.com> | Thu Apr 09 17:13:35 2020 -0400 |
committer | Marco Miller <marco.miller@ericsson.com> | Thu Apr 09 17:13:35 2020 -0400 |
tree | 1caae056fb0be287582de246f21c218e2aa90162 | |
parent | dc1871c2ef23f516b94429fe08c0d7404c3ff608 [diff] |
e2e-tests: Add the CreateProjectUsingMultiGerritTwice scenario Add the CreateProjectUsingMultiGerritTwice scenario to test if deleting a project carries over to the other HA Gerrit node. Adapt the CloneUsingMultiGerrit1 scenario to reuse it so. Make the create and delete project scenario names unique, so they can be used multiple times that way. Otherwise, Gatling won't allow duplicated scenario names in the same run. The added CreateProjectUsingMultiGerritTwice scenario is solely reusing existing scenarios, then. This is why its corresponding json test data file is empty. Each scenario that it aggregates ends up using their own json data, as the core framework prescribes. Change-Id: I64b86f0de0a33b0aaf30ce594612b6d4e0bb7c4c
This plugin allows to deploy a distributed cluster of multiple Gerrit masters each using a separate site without sharing any storage. The alignment between the masters happens using the replication plugin and an external message broker.
Requirements for the Gerrit masters are:
NOTE: The multi-site plugin will not start if Gerrit is not yet migrated to NoteDb.
Currently, the only mode supported is one primary read/write master and multiple read-only masters but eventually the plan is to support multiple read/write masters. The read/write master is handling any traffic while the read-only masters are serving the Gerrit GUI assets, the HTTP GET REST API and git fetch requests (git-upload-pack). The read-only masters are kept synchronized with the read/write master in order to be always ready to become a read/write master.
For more details on the overall multi-site design and roadmap, please refer to the multi-site plugin DESIGN.md document
This plugin is released under the same Apache 2.0 license and copyright holders as of the Gerrit Code Review project.
The multi-site plugin can only be built in tree mode, by cloning Gerrit and the multi-site plugin code, and checking them out on the desired branch.
Example of cloning Gerrit and multi-site for a stable-2.16 build:
git clone -b stable-2.16 https://gerrit.googlesource.com/gerrit git clone -b stable-2.16 https://gerrit.googlesource.com/plugins/multi-site cd gerrit/plugins ln -s ../../multi-site . rm external_plugin_deps.bzl ln -s multi-site/external_plugin_deps.bzl .
Example of building the multi-site plugin:
cd gerrit bazel build plugins/multi-site
The multi-site.jar plugin is generated to bazel-bin/plugins/multi-site/multi-site.jar
.
Example of testing the multi-site plugin:
cd gerrit bazel test plugins/multi-site:multi_site_tests
NOTE: The multi-site tests include also the use of Docker containers for instantiating and using a Kafka/Zookeeper broker. Make sure you have a Docker daemon running (/var/run/docker.sock accessible) or a DOCKER_HOST pointing to a Docker server.
Install the multi-site plugin into the $GERRIT_SITE/lib
directory of all the Gerrit servers that are part of the multi-site cluster. Create a symbolic link from $GERRIT_SITE/lib/multi-site.jar
into the $GERRIT_SITE/plugins
.
Add the multi-site module to $GERRIT_SITE/etc/gerrit.config
as follows:
[gerrit] installModule = com.googlesource.gerrit.plugins.multisite.Module
Create the $GERRIT_SITE/etc/multi-site.config
on all Gerrit servers with the following basic settings:
[kafka] bootstrapServers = <kafka-host>:<kafka-port> [kafka "publisher"] enabled = true [kafka "subscriber"] enabled = true [ref-database] enabled = true [ref-database "zookeeper"] connectString = "localhost:2181"
For more details on the configuration settings, please refer to the multi-site configuration documentation.
You also need to setup the Git-level replication between nodes, for more details please refer to the replication plugin documentation.