You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Alexey Serbin (JIRA)" <ji...@apache.org> on 2018/10/17 23:55:00 UTC

[jira] [Created] (KUDU-2609) Dockerize kudu-jepsen tests

Alexey Serbin created KUDU-2609:
-----------------------------------

             Summary: Dockerize kudu-jepsen tests
                 Key: KUDU-2609
                 URL: https://issues.apache.org/jira/browse/KUDU-2609
             Project: Kudu
          Issue Type: Improvement
          Components: jepsen, test
            Reporter: Alexey Serbin


As described in {{$KUDU_ROOT/java/kudu-jepsen/README.adoc}}, current setup for Kudu Jepsen tests requires running those against pre-provisioned Debian Linux machines. As of now, it's possible to use {{$KUDU_ROOT/src/kudu/scripts/jepsen.sh}} in various scripted scenarios (e.g., Jenkins jobs) to build everything from source and run the kudu-jepsen tests. However, that script doesn't do any provisioning and assumes that Jepsen DB and control nodes are already provisioned and running.

It would be nice to leverage Docker support for Jepsen (see [https://github.com/jepsen-io/jepsen/tree/master/docker] as a starting point) and make it possible to run kudu-jepsen tests in a dockerized environment.

Ideally, it should be possible to run the kudu-jepsen tests at Linux (of any supported flavor) and macOS developer's machines as just another set of tests. All necessary steps should be scripted and automated. That would help to spot relevant issues when updating Java code in kudu-client other related sub-projects.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)