Fallout is a tool for running local or large scale remote based distributed correctness, verification and performance tests. Fallout is run in production at DataStax facilitating mission critical testing of Apache Cassandra (TM) and DSE.
This is a preview release of the Fallout project, intended to gauge external interest. The core framework and application are present, but many of the components used at DataStax have been removed due to their reliance on internal infrastructure. The components contained in this release are focused on the Kubernetes integration with Fallout for performance testing DataStax Kubernetes operator managed clusters.
You can learn more about Fallout by reading the docs. Example tests can be found under examples. There is also a recorded workshop which covers the project's intent, architecture, and simple examples.
dockerTagLatesttask, which will run
dockerto build a new docker image using
docker/Dockerfileand tag it as
generateDockerComposetask to update
docker-compose upon the updated
<RETURN> to terminate the server. (Can take a minute on linux)
docker-compose.yml defines two volumes to persist the fallout artifacts and cassandra data, so the next time you start, the data will still be there.
As explained in detail below, you can create an initial admin user by setting
FALLOUT_ADMIN_CREDS the first time you run fallout:
FALLOUT_AUTH_MODE=SINGLE_USER FALLOUT_ADMIN_CREDS=admin:firstname.lastname@example.org:admin ./gradlew runServerInDocker
Note that the docker image contains tools for running k8s-based testruns. These tools are downloaded and packaged by gradle in the
getExternalTools task. The downloads will be cached by the gradle build cache, so it should be possible to avoid repetitive downloads by sharing the build cache in CI.
KIND is not installed when building with docker, thus the
kind provisioner will not work. To use KIND, run Fallout in development mode as below.
You will need:
JAVA11_HOMEto point at this;
JAVA8_HOMEto point at this;
In addition, Fallout relies on external tools for some functionality. The following must be installed and executable by the user running Fallout:
Last you will need to define a simple configuration,
To run Fallout locally in development mode:
Register an account at
http://localhost:8080/a/pages/register.html and setup your user credentials.
In order to run tests on GKE, a service account json must be added to the user profile.
http://localhost:8080/tests/tools/create to create your first test. The editor is pre-populated with a default example test definition.
If you want to run Fallout proxied by nginx (which will be used to serve test artifacts instead of Fallout itself):
Run the tests like this:
Run individual tests using the
./gradlew :test --tests '*.JepsenHarnessTest.testFakes'
Tests will only be executed if the source has changed; override this with
./gradlew :cleanTest :test --tests '*.JepsenHarnessTest.testFakes'
When you start up fallout for the first time, there will be no users configured. To setup a default admin user, set the environment variable
<USERNAME>:<EMAIL>:<PASSWORD> the first time you run fallout; for example,
FALLOUT_ADMIN_CREDS='Charlie Mouse:email@example.com:chocolate-biscuit-machine' ./gradlew runServer
If you want to run the fallout docker image or the
docker-compose.yml manually, on macOS you will need to make sure that SSHAUTHSOCK is set correctly to handle the special forwarding mechanisms on docker-for-mac (see docker/entrypoint.sh for the full details). To run the docker image:
docker run -it -v /run/host-services/ssh-auth.sock:/ssh-agent -e SSH_AUTH_SOCK="/ssh-agent" datastax.com/fallout:latest
...(note that it expects a Cassandra server to be running at
$FALLOUT_CASSANDRA_HOST:$FALLOUT_CASSANDRA_PORT), and to run docker-compose:
SSH_AUTH_SOCK=/run/host-services/ssh-auth.sock docker-compose up
Contributions are welcome, please see CONTRIBUTING for guidance.
If you encounter any bugs, please file a GitHub issue.
Special thanks to:
© 2020 Anant Corporation, All Rights Reserved. All logos, trademarks and registered trademarks are the property of their respective owners. .