You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Sandish Kumar HN (Jira)" <ji...@apache.org> on 2019/09/19 22:02:00 UTC
[jira] [Comment Edited] (KUDU-2609) Dockerize kudu-jepsen tests
[ https://issues.apache.org/jira/browse/KUDU-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16933795#comment-16933795 ]
Sandish Kumar HN edited comment on KUDU-2609 at 9/19/19 10:01 PM:
------------------------------------------------------------------
[~aserbin] I was looking into [https://github.com/jepsen-io/jepsen/tree/master/docker]
Correct me if wrong on implementing the docker based for kudu-Jepsen tests.
should jepsen containers "container_name: jepsen-n1, container_name: jepsen-n2, container_name: jepsen-n3" node containers kudu tserver's ? and kudu master's?
jepsen-control would be running the the kudu-jepsen tests ?
was (Author: sanysandish@gmail.com):
[~aserbin] I was looking into [https://github.com/jepsen-io/jepsen/tree/master/docker]
Correct me if wrong on implementing the docker based on kudu-Jepsen tests.
should jepsen containers "container_name: jepsen-n1, container_name: jepsen-n2, container_name: jepsen-n3" node conatins kudu tserver ? and kudu master?
jepsen-control would be running the the kudu-jepsen tests ?
> 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)