You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ariel Weisberg (JIRA)" <ji...@apache.org> on 2018/05/29 18:10:00 UTC
[jira] [Updated] (CASSANDRA-14449) Support cluster backends other
then ccm when running dtests
[ https://issues.apache.org/jira/browse/CASSANDRA-14449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ariel Weisberg updated CASSANDRA-14449:
---------------------------------------
Summary: Support cluster backends other then ccm when running dtests (was: Support cluster backends other than ccm when running dtests)
> Support cluster backends other then ccm when running dtests
> -----------------------------------------------------------
>
> Key: CASSANDRA-14449
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14449
> Project: Cassandra
> Issue Type: Improvement
> Components: Testing
> Reporter: Jordan West
> Assignee: Jordan West
> Priority: Trivial
> Attachments: 14449.patch
>
>
> While ccm is a great orchestration tool to run Cassandra clusters locally, it may be desirable to run dtests against clusters running remotely, which may be orchestrated by some tool other than ccm.
> Dtest is heavily tied to CCM but with a few minor changes its possible to support plugging in other backends that maintain a similar (duck-typed) interface.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org