[
https://issues.apache.org/jira/browse/KUDU-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934532#comment-16934532
]
Alexey Serbin commented on KUDU-2609:
-------------------------------------
[[email protected]] yes, the idea is to make Kudu Jepsen tests working on
a Dockerized setup. Using jepsen-control would be an option, and it looks like
a good first step to make. In the long run, it would be great if Kudu
developers could run Jepsen tests out of the Kudu source tree to make sure
their recent changes didn't brake Kudu Jepsen tests.
Some time ago we had Kudu Jepsen tests successfully running on a
pre-provisioned VMs: 5 tablet server and 1 maaster node, where Jenkins jobs
used this script:
https://github.com/apache/kudu/blob/master/src/kudu/scripts/jepsen.sh
Information on how to Kudu Jepsen tests using kudu-jepsen package is available
at https://github.com/apache/kudu/tree/master/java/kudu-jepsen
> 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
> Assignee: Sandish Kumar HN
> Priority: Major
> Labels: newbie, test
>
> 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
(v8.3.4#803005)
