[kudu-CR] [kudu-jepsen] added Jenkins script

[Alexey Serbin (Code Review)]

Alexey Serbin has submitted this change and it was merged.

Change subject: [kudu-jepsen] added Jenkins script
..


[kudu-jepsen] added Jenkins script

Added a shell script to build Kudu and run kudu-jepsen tests from a
Jenkins job.

Currently, the set of nodes to run Kudu cluster should be provisioned
prior to running the test. The test uses the Jenkins slave as the
Jepsen control node, running the control logic and the freshly built
Kudu Java client there. Since the clients are run there too, the
bandwidth and latency between the Jepsen and the DB nodes
should be taken into consideration while running the tests.

All Jepsen control operations on the DB nodes (i.e. Kudu master and
tserver nodes) are run via SSH. Appropriate SSH key should be deployed
prior to running the test.

Restriction:
  The Kudu jepsen cluster and the jenkins slave must run recent
  Debian-based distros. The kudu-jepsen test currently requires Debian
  and the jenkins slave must be able to build compatible binaries.

Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
Reviewed-on: http://gerrit.cloudera.org:8080/5624
Reviewed-by: David Ribeiro Alves 
Tested-by: Kudu Jenkins
---
A src/kudu/scripts/jepsen.sh
1 file changed, 140 insertions(+), 0 deletions(-)

Approvals:
  David Ribeiro Alves: Looks good to me, approved
  Kudu Jenkins: Verified



-- 
To view, visit http://gerrit.cloudera.org:8080/5624
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-MessageType: merged
Gerrit-Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
Gerrit-PatchSet: 9
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Alexey Serbin 
Gerrit-Reviewer: Adar Dembo 
Gerrit-Reviewer: Alexey Serbin 
Gerrit-Reviewer: David Ribeiro Alves 
Gerrit-Reviewer: Jean-Daniel Cryans 
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Mike Percy 
Gerrit-Reviewer: Todd Lipcon 

[kudu-CR] [kudu-jepsen] added Jenkins script

[David Ribeiro Alves (Code Review)]

David Ribeiro Alves has posted comments on this change.

Change subject: [kudu-jepsen] added Jenkins script
..


Patch Set 8: Code-Review+2

-- 
To view, visit http://gerrit.cloudera.org:8080/5624
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
Gerrit-PatchSet: 8
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Alexey Serbin 
Gerrit-Reviewer: Adar Dembo 
Gerrit-Reviewer: Alexey Serbin 
Gerrit-Reviewer: David Ribeiro Alves 
Gerrit-Reviewer: Jean-Daniel Cryans 
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Mike Percy 
Gerrit-Reviewer: Todd Lipcon 
Gerrit-HasComments: No

[kudu-CR] [kudu-jepsen] added Jenkins script

[Alexey Serbin (Code Review)]

Alexey Serbin has posted comments on this change.

Change subject: [kudu-jepsen] added Jenkins script
..


Patch Set 6:

(1 comment)

http://gerrit.cloudera.org:8080/#/c/5624/6//COMMIT_MSG
Commit Message:

PS6, Line 21: The Kudu cluster should consist of Linux machines of the same
:  architecture and OS distro as the Jenkins slave
> What I mostly mean, is that if jepsen must run on Debian, and the jenkins s
This sounds good to me -- updated.  Thanks!


-- 
To view, visit http://gerrit.cloudera.org:8080/5624
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
Gerrit-PatchSet: 6
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Alexey Serbin 
Gerrit-Reviewer: Adar Dembo 
Gerrit-Reviewer: Alexey Serbin 
Gerrit-Reviewer: David Ribeiro Alves 
Gerrit-Reviewer: Jean-Daniel Cryans 
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Mike Percy 
Gerrit-Reviewer: Todd Lipcon 
Gerrit-HasComments: Yes

[kudu-CR] [kudu-jepsen] added Jenkins script

[Alexey Serbin (Code Review)]

Hello Kudu Jenkins,

I'd like you to reexamine a change.  Please visit

http://gerrit.cloudera.org:8080/5624

to look at the new patch set (#7).

Change subject: [kudu-jepsen] added Jenkins script
..

[kudu-jepsen] added Jenkins script

Added a shell script to build Kudu and run kudu-jepsen tests from a
Jenkins job.

Currently, the set of nodes to run Kudu cluster should be provisioned
prior to running the test. The test uses the Jenkins slave as the
Jepsen control node, running the control logic and the freshly built
Kudu Java client there. Since the clients are run there too, the
bandwidth and latency between the Jepsen and the DB nodes
should be taken into consideration while running the tests.

All Jepsen control operations on the DB nodes (i.e. Kudu master and
tserver nodes) are run via SSH. Appropriate SSH key should be deployed
prior to running the test.

Restrictions:
  1. The Kudu cluster should consist of Linux machines of the same
 architecture and OS distro as the Jenkins slave. This is because
 the test copies and runs the newly built Kudu server-side binaries
 and the 'kudu' CLI utility on corresponding Kudu cluster nodes.

  2. The kudu-jepsen test supports recent Debian/Ubuntu distros only.
 This is because Jepsen lacks support for other Linux distros.

Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
---
A src/kudu/scripts/jepsen.sh
1 file changed, 140 insertions(+), 0 deletions(-)


  git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/24/5624/7
-- 
To view, visit http://gerrit.cloudera.org:8080/5624
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-MessageType: newpatchset
Gerrit-Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
Gerrit-PatchSet: 7
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Alexey Serbin 
Gerrit-Reviewer: Adar Dembo 
Gerrit-Reviewer: Alexey Serbin 
Gerrit-Reviewer: David Ribeiro Alves 
Gerrit-Reviewer: Jean-Daniel Cryans 
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Mike Percy 
Gerrit-Reviewer: Todd Lipcon 

[kudu-CR] [kudu-jepsen] added Jenkins script

[David Ribeiro Alves (Code Review)]

David Ribeiro Alves has posted comments on this change.

Change subject: [kudu-jepsen] added Jenkins script
..


Patch Set 6:

(4 comments)

http://gerrit.cloudera.org:8080/#/c/5624/6//COMMIT_MSG
Commit Message:

PS6, Line 12:  
nit: extra space


PS6, Line 13: and the freshly built
: Kudu Java client there.
should mention that the test clients run there too, not just the control logic 
(bandwidth/latency issues between the jenkins slave and the nodes under test 
may arise)


PS6, Line 21: The Kudu cluster should consist of Linux machines of the same
:  architecture and OS distro as the Jenkins slave
aren't the jenkins slaves running centos or something? I though the jepsen 
nodes needed to run debian? this seems to go against restriction 2.


http://gerrit.cloudera.org:8080/#/c/5624/6/src/kudu/scripts/jepsen.sh
File src/kudu/scripts/jepsen.sh:

PS6, Line 63: release
this should accept an override. actually not sure if we shouldn't be using 
debug, by default


-- 
To view, visit http://gerrit.cloudera.org:8080/5624
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
Gerrit-PatchSet: 6
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Alexey Serbin 
Gerrit-Reviewer: Adar Dembo 
Gerrit-Reviewer: David Ribeiro Alves 
Gerrit-Reviewer: Jean-Daniel Cryans 
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Mike Percy 
Gerrit-Reviewer: Todd Lipcon 
Gerrit-HasComments: Yes

[kudu-CR] [kudu-jepsen] added Jenkins script

[Alexey Serbin (Code Review)]

Hello Kudu Jenkins,

I'd like you to reexamine a change.  Please visit

http://gerrit.cloudera.org:8080/5624

to look at the new patch set (#6).

Change subject: [kudu-jepsen] added Jenkins script
..

[kudu-jepsen] added Jenkins script

Added a shell script to build Kudu and run kudu-jepsen tests.

Currently, the set of nodes to run Kudu cluster should be provisioned
prior to running the test.  The test uses the Jenkins slave as the
Jepsen control node, running the control logic and the freshly built
Kudu Java client there.

All Jepsen control operations on the DB nodes (i.e. Kudu master and
tserver nodes) are run via SSH.  The private SSH key should be set prior
to running the test.

Restrictions:
  1. The Kudu cluster should consist of Linux machines of the same
 architecture and OS distro as the Jenkins slave.  This is because
 the test copies and runs the newly built Kudu server-side binaries
 and the 'kudu' CLI utility on corresponding Kudu cluster nodes.

  2. The kudu-jepsen test supports recent Debian distros only.
 This is because Jepsen lacks support for other Linux distros.

Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
---
A src/kudu/scripts/jepsen.sh
1 file changed, 134 insertions(+), 0 deletions(-)


  git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/24/5624/6
-- 
To view, visit http://gerrit.cloudera.org:8080/5624
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-MessageType: newpatchset
Gerrit-Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
Gerrit-PatchSet: 6
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Alexey Serbin 
Gerrit-Reviewer: Adar Dembo 
Gerrit-Reviewer: David Ribeiro Alves 
Gerrit-Reviewer: Jean-Daniel Cryans 
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Mike Percy 
Gerrit-Reviewer: Todd Lipcon 

[kudu-CR] [kudu-jepsen] added Jenkins script

[Alexey Serbin (Code Review)]

Hello Kudu Jenkins,

I'd like you to reexamine a change.  Please visit

http://gerrit.cloudera.org:8080/5624

to look at the new patch set (#5).

Change subject: [kudu-jepsen] added Jenkins script
..

[kudu-jepsen] added Jenkins script

Added a shell script to build Kudu and run kudu-jepsen tests.

Currently, the set of nodes to run Kudu cluster should be provisioned
prior to running the test.  The test uses the Jenkins slave as the
Jepsen control node, running the control logic and the freshly built
Kudu Java client there.

All Jepsen control operations on the DB nodes (i.e. Kudu master and
tserver nodes) are run via SSH.  The private SSH key should be set prior
to running the test.

Restrictions:
  1. The Kudu cluster should consist of Linux machines of the same
 architecture and OS distro as the Jenkins slave.  This is because
 the test copies and runs the newly built Kudu server-side binaries
 and the 'kudu' CLI utility on corresponding Kudu cluster nodes.

  2. The kudu-jepsen test supports recent Debian distros only.
 This is because Jepsen lacks support for other Linux distros.

Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
---
A src/kudu/scripts/jepsen.sh
1 file changed, 134 insertions(+), 0 deletions(-)


  git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/24/5624/5
-- 
To view, visit http://gerrit.cloudera.org:8080/5624
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-MessageType: newpatchset
Gerrit-Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
Gerrit-PatchSet: 5
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Alexey Serbin 
Gerrit-Reviewer: Adar Dembo 
Gerrit-Reviewer: David Ribeiro Alves 
Gerrit-Reviewer: Jean-Daniel Cryans 
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Mike Percy 
Gerrit-Reviewer: Todd Lipcon 

[kudu-CR] [kudu-jepsen] added Jenkins script

[Alexey Serbin (Code Review)]

Hello Kudu Jenkins,

I'd like you to reexamine a change.  Please visit

http://gerrit.cloudera.org:8080/5624

to look at the new patch set (#4).

Change subject: [kudu-jepsen] added Jenkins script
..

[kudu-jepsen] added Jenkins script

Added a shell script to build Kudu and run kudu-jepsen tests.

Currently, the set of nodes to run Kudu cluster should be provisioned
prior to running the test.  The test uses the Jenkins slave as the
Jepsen control node, running the control logic and the freshly built
Kudu Java client there.

All Jepsen control operations on the DB nodes (i.e. Kudu master and
tserver nodes) are run via SSH.  The private SSH key should be set prior
to running the test.

Restrictions:
  1. The Kudu cluster should consist of Linux machines of the same
 architecture and OS distro as the Jenkins slave.  This is because
 the test copies and runs the newly built Kudu server-side binaries
 and the 'kudu' CLI utility on corresponding Kudu cluster nodes.

  2. The kudu-jepsen test supports recent Debian distros only.
 This is because Jepsen lacks support for other Linux distros.

Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
---
A src/kudu/scripts/jepsen.sh
1 file changed, 129 insertions(+), 0 deletions(-)


  git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/24/5624/4
-- 
To view, visit http://gerrit.cloudera.org:8080/5624
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-MessageType: newpatchset
Gerrit-Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
Gerrit-PatchSet: 4
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Alexey Serbin 
Gerrit-Reviewer: Adar Dembo 
Gerrit-Reviewer: David Ribeiro Alves 
Gerrit-Reviewer: Jean-Daniel Cryans 
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Todd Lipcon 

[kudu-CR] [kudu-jepsen] added Jenkins script

[Alexey Serbin (Code Review)]

Hello Kudu Jenkins,

I'd like you to reexamine a change.  Please visit

http://gerrit.cloudera.org:8080/5624

to look at the new patch set (#3).

Change subject: [kudu-jepsen] added Jenkins script
..

[kudu-jepsen] added Jenkins script

Added a shell script to build Kudu and run kudu-jepsen tests.

Currently, the set of nodes to run Kudu cluster should be provisioned
prior to running the test.  The test uses the Jenkins slave as the
Jepsen control node, running the control logic and the freshly built
Kudu Java client there.

All Jepsen control operations on the DB nodes (i.e. Kudu master and
tserver nodes) are run via SSH.  The private SSH key should be set prior
to running the test:

  1. The public part of the SSH key should be added into the
 'authorized_keys' file for the root user on all cluster nodes.

  2. The private part of the SSH key should be provided to the test
 either by:
   * adding the key into the SSH agent on the control node
   * specifying the path to the key via environment variable

Restrictions:
  1. The Kudu cluster should consist of Linux machines of the same
 architecture and OS distro as the Jenkins slave.  This is because
 the test copies and runs the newly built Kudu server-side binaries
 and the 'kudu' CLI utility on corresponding Kudu cluster nodes.

  2. The kudu-jepsen test supports recent Debian distros only.
 This is because Jepsen lacks support for other Linux distros.

Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
---
A src/kudu/scripts/jepsen.sh
1 file changed, 129 insertions(+), 0 deletions(-)


  git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/24/5624/3
-- 
To view, visit http://gerrit.cloudera.org:8080/5624
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-MessageType: newpatchset
Gerrit-Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
Gerrit-PatchSet: 3
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Alexey Serbin 
Gerrit-Reviewer: Adar Dembo 
Gerrit-Reviewer: David Ribeiro Alves 
Gerrit-Reviewer: Jean-Daniel Cryans 
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Todd Lipcon 

[kudu-CR] [kudu-jepsen] added Jenkins script

[Alexey Serbin (Code Review)]

Alexey Serbin has uploaded a new patch set (#2).

Change subject: [kudu-jepsen] added Jenkins script
..

[kudu-jepsen] added Jenkins script

Added a shell script to build Kudu and run kudu-jepsen tests.

Currently, the set of nodes to run Kudu cluster should be provisioned
prior to running the test.  The test uses the Jenkins slave as the
Jepsen control node, running the control logic and the freshly built
Kudu Java client there.

All Jepsen control operations on the DB nodes (i.e. Kudu master and
tserver nodes) are run via SSH.  The private SSH key should be set prior
to running the test:

  1. The public part of the SSH key should be added into the
 'authorized_keys' file for the root user on all cluster nodes.

  2. The private part of the SSH key should be provided to the test
 either by:
   * adding the key into the SSH agent on the control node
   * specifying the path to the key via environment variable

Restrictions:
  1. The Kudu cluster should consist of Linux machines of the same
 architecture and OS distro as the Jenkins slave.  This is because
 the test copies and runs the newly built Kudu server-side binaries
 and the 'kudu' CLI utility on corresponding Kudu cluster nodes.

  2. The kudu-jepsen test supports recent Debian distros only.
 This is because Jepsen lacks support for other Linux distros.

Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
---
A src/kudu/scripts/jepsen.sh
1 file changed, 129 insertions(+), 0 deletions(-)


  git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/24/5624/2
-- 
To view, visit http://gerrit.cloudera.org:8080/5624
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-MessageType: newpatchset
Gerrit-Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
Gerrit-PatchSet: 2
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Alexey Serbin 
Gerrit-Reviewer: Kudu Jenkins

[kudu-CR] [kudu-jepsen] added Jenkins script

[Alexey Serbin (Code Review)]

Alexey Serbin has uploaded a new change for review.

  http://gerrit.cloudera.org:8080/5624

Change subject: [kudu-jepsen] added Jenkins script
..

[kudu-jepsen] added Jenkins script

Added a shell script to build Kudu and run kudu-jepsen tests.

Currently, the set of nodes to run Kudu cluster should be provisioned
prior to running the test.  The test uses the Jenkins slave as the
Jepsen control node, running the control logic and the freshly built
Kudu Java client there.

All Jepsen control operations on the DB nodes (i.e. Kudu master and
tserver nodes) are run via SSH.  The private SSH key should be set prior
to running the test:

  1. The public part of the SSH key should be added into the
 'authorized_keys' file for the root user on all cluster nodes.

  2. The private part of the SSH key should be provided to the test
 either by:
   * adding the key into the SSH agent on the control node
   * specifying the path to the key via environment variable

Restrictions:
  1. The Kudu cluster should consist of Linux machines of the same
 architecture and OS distro as the Jenkins slave.  This is because
 the test copies and runs the newly built Kudu server-side binaries
 and the 'kudu' CLI utility on corresponding Kudu cluster nodes.

  2. The kudu-jepsen test supports recent Debian distros only.
 This is because Jepsen lacks support for other Linux distros.

Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
---
A src/kudu/scripts/jepsen.sh
1 file changed, 129 insertions(+), 0 deletions(-)


  git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/24/5624/1
-- 
To view, visit http://gerrit.cloudera.org:8080/5624
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-MessageType: newchange
Gerrit-Change-Id: I36a7e890baabb5427b22daa3aeee58ed894b83d6
Gerrit-PatchSet: 1
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Alexey Serbin