| commit | 8526ff2c536a668fd8447f6a14cc682e0cf3520a | [log] [tgz] |
|---|---|---|
| author | Marco Miller <marco.miller@ericsson.com> | Wed Jun 03 16:03:38 2020 -0400 |
| committer | Marco Miller <marco.miller@ericsson.com> | Wed Jun 03 18:08:10 2020 -0400 |
| tree | 3df3e823f6f97af773a3871610d9b83dd4b816b0 | |
| parent | ded1aad9b056c0aab234b91f28f0ffaa70d717ca [diff] |
CreateChangeUsingMultiGerrit: Fix 401 towards 8081 Make the DeleteChangeUsingMultiGerrit1 scenario use its own http password towards the 8081 gerrit. Make the CreateChangeUsingMultiGerrit scenario do the same upon injecting DeleteChangeUsingMultiGerrit1's test. The other CreateChangeUsingMultiGerrit steps still use 8080's own (cluster, 8082) http password for the admin test user. As usual with the core framework, this requires an http.password_replica entry in [1] locally; cf. [2]: [1] e2e-tests/src/test/resources/application.conf [2] https://gerrit-documentation.storage.googleapis.com/Documentation/3.0.9/dev-e2e-tests.html#_project_and_http_credentials Fixing the previous 401 'unauthorized' http error this way leads to DeleteChangeUsingMultiGerrit1 now failing with a 404 not-found error. That is likely because the change created from 8082 (8080) is not synchronized towards 8081 by the dockerised_local_env (new Issue 12863). Bug: Issue 12693 Change-Id: I81d0c8c2b464455340b1e9a6f8fa9b28e5fdf302
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] installDbModule = com.googlesource.gerrit.plugins.multisite.GitModule installModule = com.googlesource.gerrit.plugins.multisite.Module
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.