feature(packaging): debian and rpm packaging

[CodeLieutenant]

Adding Debian and RPM Packaging

Tasks

Preview Give feedback

1. RPM
2. Debian
3. Fat Jar instead of multiple jar libraries
4. Github Action on release to publish .deb and .rpm

[mykaul]

What's the value of packaging it, if a container works great?

[CodeLieutenant]

What's the value of packaging it, if a container works great?

@mykaul We need it without a container, container works great, but we want to test it on bare metal.
It's bad for performance testing, just to avoid the overhead that we have with containers,
and also customers want to run it without docker. Cassandra stress was supplied with .deb and .rpm before, in scylla-tools-java so we are bringing the support back

[mykaul]

What's the value of packaging it, if a container works great?

@mykaul We need it without a container, container works great, but we want to test it on bare metal. It's bad for performance testing, just to avoid the overhead that we have with containers, and also customers want to run it without docker. Cassandra stress was supplied with .deb and .rpm before, in scylla-tools-java so we are bringing the support back

This isn't true. Containers work at 99-99.9% of the performance of bare metal.

I haven't heard of a customer asking to run non-containerized cassandra-stress. They may want to, they can use older versions that are still available. We have more important tasks (IMHO) to focus on that we can bring value to customers with.
(Random examples - move to newer Java - which will be faster most likely; move away from cassandra-stress to newer tools, using more modern drivers and architecture; extend c-s with more feature to provide more realistic workload simulations).

[fruch]

What's the value of packaging it, if a container works great?

@mykaul We need it without a container, container works great, but we want to test it on bare metal. It's bad for performance testing, just to avoid the overhead that we have with containers, and also customers want to run it without docker. Cassandra stress was supplied with .deb and .rpm before, in scylla-tools-java so we are bringing the support back

This isn't true. Containers work at 99-99.9% of the performance of bare metal.

It's close, if you use the correct options
Our throughput test so show a difference, and we still keeps the option of running without docker cause of it.

I haven't heard of a customer asking to run non-containerized cassandra-stress. They may want to, they can use older versions that are still available. We have more important tasks (IMHO) to focus on that we can bring value to customers with.

You didn't heard, cause there isn't any release without it yet.

(Random examples - move to newer Java - which will be faster most likely; move away from cassandra-stress to newer tools, using more modern drivers and architecture; extend c-s with more feature to provide more realistic workload simulations).

Not sure how those examples are counter to have other delivery option but docker ?

I can give one actual example, I know of a user (inside Scylla) that was given the docker image, he extracted the jar files from it, and replace them with installed c-s version he had.

I think it's a bit too soon to assume what users need in that regards.

We as users in SCT of c-s stress, need a debian package as well.

[mykaul]

Not sure how those examples are counter to have other delivery option but docker ?

Matter of priorities. If we do this, we don't do them.

[fruch]

Not sure how those examples are counter to have other delivery option but docker ?

Matter of priorities. If we do this, we don't do them.

there is not list of those other things you mentioned, hence they are not taken into any priority making