Contributors
| Contributors |
|---|
...
From: Greg Matza [mailto:greg@scylladb.com]
Sent: Wednesday, 24 October 2018 03:58
To: Keong Lim <Keong.Lim@huawei.com>
Subject: Re: ScyllaDBKeong,
Google Alert notified me of your posting on the ONAP site. From that notification, I saw your notes on our conversation and learned a bit more about your project.
We are excited by the prospect of inclusion in the ONAP AAI project. Our co-founders - Dor Laor and Avi Kivity are well experienced with Linux Foundation projects, as they are the creator and early manager of the KVM Hypervisor. So working with OSS Foundations is in our company's DNA. In addition, telecom are among the early adopters of Scylla - AT&T, Verizon, Huawei, Comcast, T-mobile are all either running Scylla in Production or are in POC.
As you continue to research the viability of Scylla for AAI, I'd like to make our technical and executive resources available to you. From a technical perspective, we are available to help with any POC or evaluation. (Installation, hardware recommendations, monitoring setup, or other practical questions). From an executive perspective, we'd be happy to discuss any potential questions with roadmap, licensing or other 'vision'-type questions.
Let me know if/when you are ready to engage with our technical or executive resources.
Greg
From: Greg Matza [mailto:greg@scylladb.com]
Sent: Tuesday, 11 December 2018 13:01
To: Keong Lim <Keong.Lim@huawei.com>
Cc: stephen.terrill@ericsson.com; jf2512@att.com; Maheedhar Gunturu <maheedhar@scylladb.com>
Subject: Re: ScyllaDBKeong,
Unfortunately, we don't have a public demo lab that you can point your application at. The closest we have is the Scylla Test Drive, which spins up a cluster on AWS and gives you SSH access to the nodes, but the cluster only runs for an hour, and you are mostly stuck with cassandra-stress. (https://www.scylladb.com/test-drive/) Better than nothing, but not perfect.
For your testing, we are happy to share all the necessary instructions on how to get started using Scylla with Kubernetes and give you access to our Helm Charts and stateful sets. We are also happy to make ourselves available over Slack and/or web conferences to help set everything up.
Hardware requirements are https://docs.scylladb.com/getting-started/system-requirements/. Scylla will probably run on your laptop, but the official testing and Production recommendations are:
Installation
Cores
Memory
Disk
Network
Test, minimal
4
2 GB
Single plain SSD
1 Gbps
Production
20 cores - 2 socket, 10 cores each
128 GB
RAID-0, 4 SSDs, 1-5TBs
10 Gbps
Ultimately, if you can share workload specs with us, we can make hardware sizing recommendations.
Slack invitations are available at http://slack.scylladb.com. Binaries are at https://www.scylladb.com/download/#binary (or https://www.scylladb.com/download/#docker). Let us know when you have the cycles to do some testing.
Greg
On Mon, Dec 10, 2018 at 4:35 PM Keong Lim <Keong.Lim@huawei.com> wrote:
Hi Greg,
To that end, do you have some public demo lab available that runs Scylla in a Kubernetes cluster, where we could push some data and queries through to observe the behavior and collect stats?
What would be the min/max/default CPU/RAM resources to configure in the pods?
ONAP project has its own Cassandra clusters running in various test labs, so a virtual-side-by-side comparison might provide an interesting data point to consider.
Keong
From: Greg Matza [mailto:greg@scylladb.com]
Sent: Tuesday, 11 December 2018 11:02
To: Keong Lim <Keong.Lim@huawei.com>
Cc: stephen.terrill@ericsson.com; jf2512@att.com
Subject: Re: ScyllaDBSounds good.
Of course, Jackson vulnerabilities may be the bleeding wound that needs to be patched up most urgently. But there are also other benefits of Scylla vs. Cassandra. Namely, easier maintenance (no JVM tuning, no cache tuning, etc.), and typically cheaper/better performance on fewer nodes.
I just mention this because the idea of Scylla as a wholesale replacement for all the C* throughout AAI (and even ONAP) came up on your last discussion. (I listened to the recording) Obviously, we'd encourage that! We think our software is awesome! But, beyond our boosterism, there might be real value to users, beyond the Security aspects.
Look forward to hearing from you,
Greg
On Mon, Dec 10, 2018 at 3:56 PM Keong Lim <Keong.Lim@huawei.com> wrote:
Hi Greg,
The issue of replacing Jackson libraries came up again from a security standpoint, so there may be some appetite to look at a Cassandra replacement as part of that work.
The discussion right now is about which use cases will be included in the next release, but priorities have not been agreed yet.
Will keep Scylla in mind when the topic does come up again!
Keong
From: Greg Matza [mailto:greg@scylladb.com]
Sent: Tuesday, 11 December 2018 10:28
To: Keong Lim <Keong.Lim@huawei.com>
Subject: Re: ScyllaDBKeong,
Congrats on the Casablanca release.
We're here to assist with any testing or discussion, once the Cassandra/Scylla question comes up again, as part of Dublin. Any thoughts on when that might be?
Greg
ScyllaDB as replacement for Cassandra
...
VF2F December 2018
- Mentioned again for S3P requirements at https://wiki.onap.org/pages/viewpage.action?pageId=45293323Dublin release S3P requirements at ONAP Project Developers Event, Dec 10 - 12, 2018, (Virtual Webinars)
Conclusion So Far
For AAI project:
...
From: Greg Matza [mailto:greg@scylladb.com]
Sent: Tuesday, 11 December 2018 13:01
To: Keong Lim <Keong.Lim@huawei.com>
Cc: stephen.terrill@ericsson.com; jf2512@att.com; Maheedhar Gunturu <maheedhar@scylladb.com>
Subject: Re: ScyllaDB
Keong,
Unfortunately, we don't have a public demo lab that you can point your application at. The closest we have is the Scylla Test Drive, which spins up a cluster on AWS and gives you SSH access to the nodes, but the cluster only runs for an hour, and you are mostly stuck with cassandra-stress. (https://www.scylladb.com/test-drive/) Better than nothing, but not perfect.
For your testing, we are happy to share all the necessary instructions on how to get started using Scylla with Kubernetes and give you access to our Helm Charts and stateful sets. We are also happy to make ourselves available over Slack and/or web conferences to help set everything up.
Hardware requirements are https://docs.scylladb.com/getting-started/system-requirements/. Scylla will probably run on your laptop, but the official testing and Production recommendations are:
Installation | Cores | Memory | Disk | Network |
Test, minimal | 4 | 2 GB | Single plain SSD | 1 Gbps |
Production | 20 cores - 2 socket, 10 cores each | 128 GB | RAID-0, 4 SSDs, 1-5TBs | 10 Gbps |
Ultimately, if you can share workload specs with us, we can make hardware sizing recommendations.
Slack invitations are available at http://slack.scylladb.com. Binaries are at https://www.scylladb.com/download/#binary (or https://www.scylladb.com/download/#docker). Let us know when you have the cycles to do some testing.
Greg
On Mon, Dec 10, 2018 at 4:35 PM Keong Lim <Keong.Lim@huawei.com> wrote:
Hi Greg,
To that end, do you have some public demo lab available that runs Scylla in a Kubernetes cluster, where we could push some data and queries through to observe the behavior and collect stats?
What would be the min/max/default CPU/RAM resources to configure in the pods?
ONAP project has its own Cassandra clusters running in various test labs, so a virtual-side-by-side comparison might provide an interesting data point to consider.
Keong
From: Greg Matza [mailto:greg@scylladb.com]
Sent: Tuesday, 11 December 2018 11:02
To: Keong Lim <Keong.Lim@huawei.com>
Cc: stephen.terrill@ericsson.com; jf2512@att.com
Subject: Re: ScyllaDB
Sounds good.
Of course, Jackson vulnerabilities may be the bleeding wound that needs to be patched up most urgently. But there are also other benefits of Scylla vs. Cassandra. Namely, easier maintenance (no JVM tuning, no cache tuning, etc.), and typically cheaper/better performance on fewer nodes.
I just mention this because the idea of Scylla as a wholesale replacement for all the C* throughout AAI (and even ONAP) came up on your last discussion. (I listened to the recording) Obviously, we'd encourage that! We think our software is awesome! But, beyond our boosterism, there might be real value to users, beyond the Security aspects.
Look forward to hearing from you,
Greg
On Mon, Dec 10, 2018 at 3:56 PM Keong Lim <Keong.Lim@huawei.com> wrote:
Hi Greg,
The issue of replacing Jackson libraries came up again from a security standpoint, so there may be some appetite to look at a Cassandra replacement as part of that work.
The discussion right now is about which use cases will be included in the next release, but priorities have not been agreed yet.
Will keep Scylla in mind when the topic does come up again!
Keong
From: Greg Matza [mailto:greg@scylladb.com]
Sent: Tuesday, 11 December 2018 10:28
To: Keong Lim <Keong.Lim@huawei.com>
Subject: Re: ScyllaDB
Keong,
Congrats on the Casablanca release.
We're here to assist with any testing or discussion, once the Cassandra/Scylla question comes up again, as part of Dublin. Any thoughts on when that might be?
Greg