Run Cassandra storage backend with production data

To make sure nothing unexpected happens

---

Migrated from T2033 (view on Phabricator)

assigned to @vlorentz

marked this issue as related to #1892

added Storage manager priority:Low labels

mentioned in commit swh/infra/puppet/puppet-swh-site@2eee9282

mentioned in commit swh/infra/puppet/puppet-environment@4ce88b7b

mentioned in commit swh/infra/swh-sysadmin-provisioning@d24116df

A cassandra cluster has been deployed on cassandra[01-06].euwest.azure.internal.softwareheritage.org.

The deployment, done via terraform and puppet, follows the best practices from https://docs.microsoft.com/en-us/azure/architecture/best-practices/cassandra

added state:wip label

marked this issue as related to #2214 (closed)

marked this issue as related to swh/infra/sysadm-environment#2498 (closed)

changed title from Run Cassandra storage draft with production data to Run Cassandra storage backend with production data

changed milestone to %Cassandra in production as primary storage [Roadmap - Tooling and infrastructure]

added activity::Epic label

unassigned @vlorentz

closing this issue in favor of swh/infra/sysadm-environment#4811 (closed)

closed

removed state:wip label