The RESTBase cluster is using a custom build of the Cassandra 3.11.0 release. Currently tagged in our fork as wmf/3.11.0-wmf5 (see: https://github.com/wikimedia/cassandra/compare/cassandra-3.11.0...wmf/3.11.0-wmf5).
Debian packages are on rutherfordium:
These packages are signed by my key (same one in used in the Debian keyring):
pub rsa4096 2009-07-12 [SC] C4965EE9E3015D192CCCF2B6F758CE318D77295D uid [ full ] Eric Evans <firstname.lastname@example.org> uid [ full ] Eric Evans <email@example.com> uid [ full ] Eric Evans <firstname.lastname@example.org> uid [ full ] Eric Evans <email@example.com> uid [ unknown] Eric Evans <firstname.lastname@example.org> sub rsa4096 2009-07-12 [E]
The current version in the repository is 2.2.6-wmf1, which is the version in use by both the AQS and maps clusters. Simply upgrading the version to this one would be problematic for them. While RESTBase is deployed on jessie, these packages are arch independent and should be compatible with stretch; Would it be possible to have these added under stretch using the new structure, component/cassandra311 perhaps?