kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ewen Cheslack-Postava (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-1748) Decouple system test cluster resources definition from service definitions
Date Mon, 03 Nov 2014 20:04:34 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195006#comment-14195006
] 

Ewen Cheslack-Postava commented on KAFKA-1748:
----------------------------------------------

Updated reviewboard https://reviews.apache.org/r/27536/diff/
 against branch origin/trunk

> Decouple system test cluster resources definition from service definitions
> --------------------------------------------------------------------------
>
>                 Key: KAFKA-1748
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1748
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8.1.1
>            Reporter: Ewen Cheslack-Postava
>            Assignee: Ewen Cheslack-Postava
>         Attachments: KAFKA-1748.patch, KAFKA-1748_2014-11-03_12:04:18.patch
>
>
> Currently the system tests use JSON files that specify the set of services for each test
and where they should run (i.e. hostname). These currently assume that you already have SSH
keys setup, use the same username on the host running the tests and the test cluster, don't
require any additional ssh/scp/rsync flags, and assume you'll always have a fixed set of compute
resources (or that you'll spend a lot of time editing config files).
> While we don't want a whole cluster resource manager in the system tests, a bit more
flexibility would make it easier to, e.g., run tests against a local vagrant cluster or on
dynamically allocated EC2 instances. We can separate out the basic resource spec (i.e. json
specifying how to access machines) from the service definition (i.e. a broker should run with
settings x, y, z). Restricting to a very simple set of mappings (i.e. map services to hosts
with round robin, optionally restricting to no reuse of hosts) should keep things simple.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message