Hi, Sorry for the delay, I wasn't properly subscribed to the mailing list and got it forwarded to me.
To your question, you are right, the original backend supported was AWS. However, GCE and OpenStack support for Scylla were added in few days of work. We can help if you have any question. Roy -------- Forwarded Message -------- Subject: Re: Using SCT to test cassandra clusters Date: Mon, 16 Oct 2017 11:02:14 +0000 From: kurt greaves <k...@instaclustr.com> <k...@instaclustr.com> Reply-To: dev@cassandra.apache.org To: dev@cassandra.apache.org Thanks Roy, this actually looks pretty interesting. It seems that only AWS is supported for Cassandra, and a lot of the code is obviously geared towards scylla (e.g nemesis). Do you have any idea how much works w.r.t Cassandra? On 8 October 2017 at 17:00, Roy Dahan <r...@scylladb.com> <r...@scylladb.com> wrote: > Hi, > My name is Roy and I'm one of the maintainers of SCT > <https://github.com/scylladb/scylla-cluster-tests> > <https://github.com/scylladb/scylla-cluster-tests>, a framework to deploy > and test Scylla & Cassandra clusters on various backends like (AWS, GCE, > OpenStack and libvirt). > > In general: > > - scdm.cluster: Contains cluster/node abstractions > > > - scdm.nemesis: Cluster disruption procedures > > > - scdm.remote: SSH library > > > - scdm.tester: Contains base test class > > > We regularly add more type of Nemesis (cluster disrupters) and tests. > > Important to note, It doesn't replace dtest but it's a useful framework to > test the cluster as a whole for longer period of time with various > scenarios. > > Feel free to use and contribute back. > > Roy > - QA Manager, Scylla >
