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

Jon Haddad edited comment on CASSANDRASC-23 at 7/21/20, 12:10 AM:
------------------------------------------------------------------

I've updated the patch to use Kubernetes instead of Docker directly since it 
seems to be more ubiquitous.  I've run the tests on my mac with minikube, and 
microk8s in CircleCI.  I've provided environment variables to support different 
configurations as well as a setup script which will guide developers through 
initial setup of their machines.

https://github.com/apache/cassandra-sidecar/pull/14

CircleCI runs here: 
https://app.circleci.com/pipelines/github/rustyrazorblade/cassandra-sidecar


was (Author: rustyrazorblade):
I've updated the patch to use Kubernetes instead of Docker directly since it 
seems to be more ubiquitous.  I've run the tests on my mac with minikube, and 
microk8s in CircleCI.  I've provided environment variables to support different 
configurations as well as a setup script which will guide developers through 
initial setup of their machines.

https://github.com/apache/cassandra-sidecar/pull/14

> Set up structure for handling multiple Cassandra versions
> ---------------------------------------------------------
>
>                 Key: CASSANDRASC-23
>                 URL: https://issues.apache.org/jira/browse/CASSANDRASC-23
>             Project: Sidecar for Apache Cassandra
>          Issue Type: Improvement
>          Components: Configuration
>            Reporter: Jon Haddad
>            Assignee: Jon Haddad
>            Priority: Normal
>
> The first sidecar release will be for Cassandra 4.0, but one of the project 
> goals is to be able to handle multiple versions.  This will be especially 
> important in mixed version clusters, or even mixed version 1:N sidecar to C* 
> nodes (see CASSANDRASC-17).
> This JIRA is to lay the foundational work for supporting multiple Cassandra 
> versions. 
> Each Cassandra version (for example \{{cassandra40}}, \{{cassandra50}}, will 
> be in a separate Gradle subproject, implementing a common interface defined 
> in a \{{common}} subproject.  A common cassandra integration testing 
> framework will be able to test every version to ensure each version adheres 
> to the expected interface.
> Each module will define the minimum compatibility it supports, so if someone 
> (for example) wants to implement a Cassandra30 module for their own cluster, 
> they will have the ability to do so.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to