The whole CI is refactored. The following problems are solved:

1. Couldn't test base image locally without overriding the old one.

The testing stage is run in two ways depending on whether some
of the docker-related files were changed.

If they didn't (most likely), testing stage is run on the `latest`
docker image as it used to.

Otherwise, the docker image is rebuilt locally and tested. This is done
by using `image:pull_policy` option, see [1].

It also makes a problem of using protected credentials irrelevant.

2. Gitlab caching used to be slow

Stupid gitlab caching (see [2]) wasted on (un)zipping cache 4 minutes
(of 6 total). Now it's replaced with a manual one: an archive (tar) is
placed in a docker volume on a self-hosted gitlab runner with no
compression.

3. Speed up fetching git.

The tarantool-sys submodule requires a tag to be built correctly, but
using shallow clones prevented that. We used to work-around it by
specifying `GIT_DEPTH: 0`, but that's sub-optimal too. This patch
introduces an elegant yet reliable solution:

```
until git describe; do git fetch --deepen 100; done
```

4. No fine-grained time tracking was available

Gitlab only shows the total time of `step_script` without splitting it
into particular commands. This problem is solved by incorporating
collapsible log sections feature, see [3]. It makes logs fancy too.

Refs:

- [1] https://docs.gitlab.com/ee/ci/yaml/#imagepull_policy
- [2] https://gitlab.com/gitlab-org/gitlab-runner/-/issues/3523
- [3] https://docs.gitlab.com/ee/ci/jobs/#custom-collapsible-sections

Alexey Protsenko authored 2 years ago and Yaroslav Dynnikov committed 2 years ago

Move build base on Ubuntu 22.04

Cases covered:
- when someone goes offline
- whenever vshard gets reconfigured

Georgy Moshkin authored 2 years ago and Georgy Moshkin committed 2 years ago

Currently stores:
- replicset_id
- replicaset_uuid
- sharding weight
- replication master id

Yaroslav Dynnikov authored 2 years ago and Yaroslav Dynnikov committed 2 years ago

Only a few functions are allowed in signal handlers (see `man 7
signal-safety`). Both `println!()` and `std::process::exit()` are not
acceptable. In our case `std::process::exit()` resulted in a dead lock
when called concurrently.

This patch fixes it, and also enhances some other aspects of the supervisor.

See also: https://stackoverflow.com/questions/44865737/println-panics-when-called-concurrently

Yaroslav Dynnikov authored 2 years ago and Yaroslav Dynnikov committed 2 years ago

This commit slignly changes the order of entries in the raft log:
ConfChange now comes at the first place before other Ops, but that's ok.

Yaroslav Dynnikov authored 2 years ago and Yaroslav Dynnikov committed 2 years ago

Do it only when the governor tells to. When `_G.vshard == nil`, it's
more alike `traft::node::global()` which reurns either `Ok` or
`Err(Uninitialized)`.

Yaroslav Dynnikov authored 2 years ago and Yaroslav Dynnikov committed 2 years ago

It produces better error messages.

Before this commit:

```
tarantool> vshard.router.call()
---
- error: '[string "local log = require(''log'')..."]:575: attempt to
    compare number with nil'
...
```

With this commit:

```
- error: 'vshard/router/init.lua:575: attempt to compare number with
    nil'
```