280cd23c13
Fixes #18903 Adds a "transitional" internode encryption mode, under which all _outgoing_ RPC connections will use TLS, but we will still accept any incoming non-tls connection. This allows an operator to perform a move to TLS RPC without cluster downtime: 1. For each server, add certificate etc options to server_encryption_options + internode_encryption=none + set ssl_storage_port + restart (rolling) 2. For each server, set internode_encryption=transitional + RR 3. For each server, set internode_encryption=all + RR Closes scylladb/scylladb#18939 * github.com:scylladb/scylladb: test::topology: Add test for TLS upgrade and downgrade of internode encryption docs: Add internode_encryption=transitional documentation messaging_service: Add "transitional" internode encryptipn mode messaging_service: Create TLS connector even if internode_enc=none when certs set
Scylla in-source tests.
For details on how to run the tests, see docs/dev/testing.md
Shared C++ utils, libraries are in lib/, for Python - pylib/
alternator - Python tests which connect to a single server and use the DynamoDB API unit, boost, raft - unit tests in C++ cql-pytest - Python tests which connect to a single server and use CQL topology* - tests that set up clusters and add/remove nodes cql - approval tests that use CQL and pre-recorded output rest_api - tests for Scylla REST API Port 9000 scylla-gdb - tests for scylla-gdb.py helper script nodetool - tests for C++ implementation of nodetool
If you can use an existing folder, consider adding your test to it. New folders should be used for new large categories/subsystems, or when the test environment is significantly different from some existing suite, e.g. you plan to start scylladb with different configuration, and you intend to add many tests and would like them to reuse an existing Scylla cluster (clusters can be reused for tests within the same folder).
To add a new folder, create a new directory, and then
copy & edit its suite.ini.