[
https://issues.apache.org/jira/browse/CASSANDRA-19978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890038#comment-17890038
]
João Reis commented on CASSANDRA-19978:
---------------------------------------
I've been discussing with [~ribaraka] offline to better understand how
testcontainers work with multiple node clusters and apparently it works fine on
Linux because it relies on the host being able to connect to the container IPs
on a bridge network. However, this probably doesn't work on Windows or macOS
because there is a NAT in these two OS (I tested Windows not macOS).
This would effectively be a downgrade for macOS contributors as they are
currently able to run ccm natively just fine atm. For Windows it's not really a
downgrade since ccm doesn't work for C* 4.0+ anyway (C* 4.0 dropped windows
support) but using ccm on a VM is possible while I'm not sure if using
testcontainers(docker) on a VM will cause issues. I remember reading about
issues trying to run docker on some VM environments.
> Rewrite integration test setup in Go
> ------------------------------------
>
> Key: CASSANDRA-19978
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19978
> Project: Cassandra
> Issue Type: Task
> Components: Client/gocql-driver
> Reporter: João Reis
> Priority: Normal
>
> {quote}Currently integration tests use ccm to setup a Cassandra cluster for
> testing.
> It is not easy to simulate things like topology changes, nodes joining,
> leaving, re-joining with a different IP address, etc.
> We could rewrite integration test runner using Docker API directly or using a
> library like testcontainers-go.
> {quote}
>
> https://github.com/apache/cassandra-gocql-driver/issues/1686
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
