You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (Jira)" <ji...@apache.org> on 2021/01/11 10:42:00 UTC

[jira] [Updated] (IGNITE-13466) Isolate ducktape cluster from ducktape runner

     [ https://issues.apache.org/jira/browse/IGNITE-13466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anton Vinogradov updated IGNITE-13466:
--------------------------------------
    Sprint:   (was: Ducktape Sprint 1)

> Isolate ducktape cluster from ducktape runner
> ---------------------------------------------
>
>                 Key: IGNITE-13466
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13466
>             Project: Ignite
>          Issue Type: New Feature
>            Reporter: Maksim Timonin
>            Assignee: Maksim Timonin
>            Priority: Major
>              Labels: IEP-56, ducktape
>
> Currently it's possible to run any test code on ducktape runner (for example run thin client, or establish jdbc connection with cluster). But runner should be responsible for orchestration only and can have different configuration as cluster nodes have, it should not run test logic that are different from start services by ssh, and collecting logs. 
> So, we should restrict cluster, and forbid any connection between cluster and runner except ssh. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)