[
https://issues.apache.org/jira/browse/KAFKA-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14967415#comment-14967415
]
Ewen Cheslack-Postava commented on KAFKA-2644:
----------------------------------------------
[~rsivaram] To be honest, I do not know nearly enough about those tools to
offer much guidance. From ducktape's perspective, there probably isn't much
difference since all ducktape cares about is that you can write a Service class
to wrap it.
Is MiniKDC enough of a replacement for a full setup to write all the system
tests we'd want to? If it is, we'd probably just need to make sure there's an
easy way to run it standalone since you want to run it as a separate service,
not in a test harness class.
If we already have MiniKDC setup for our code, I'd say the things to consider
are:
1. Can we get away with only MiniKDC? Are there any tests where it won't be
sufficient?
2. Is MiniKDC realistic enough? Any limitations in functionality or anything
like that which would limit our ability to write tests?
If we end up needing KDC, then you'd just want to integrate the installation
into the Vagrant "provisioner" scripts so the necessary jars are available on
the VMs in a fixed location that the system tests can use. Depending on the
sort of manual testing people might want to do with a Vagrant test-bed, it
might be handy to have that setup regardless of which one the system tests use!
> Run relevant ducktape tests with SASL_PLAINTEXT and SASL_SSL
> ------------------------------------------------------------
>
> Key: KAFKA-2644
> URL: https://issues.apache.org/jira/browse/KAFKA-2644
> Project: Kafka
> Issue Type: Sub-task
> Components: security
> Reporter: Ismael Juma
> Assignee: Rajini Sivaram
> Priority: Critical
> Fix For: 0.9.0.0
>
>
> We need to define which of the existing ducktape tests are relevant. cc
> [~rsivaram]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
