Amrou Bellalouna

At Python Discord, we use Ansible to set up a part of our infrastructure.

A “bad” pattern we had is that we always tested these playbooks in production. I say “bad” because I think this can be a pretty controversial topic, and I’ve worked in a lot of companies who do this, or cheated their way around it, but that’s off-topic for now.

This led us to setting up a way to easily test our playbooks, but on a similar environment, without running the risk of unintentionally performing an undesired/destructive action or whatever.

Upgrading to RabbitMQ v4 threatened to break our entire usage of Celery, more specifically tasks with ETAs.

At 8M messages/day with zero downtime tolerance, we needed a migration strategy that preserves delayed task execution while switching from classic to quorum queues.