Skip to content

Ordering Message Queues

We provision and operate the RabbitMQ cluster for you. Once the cluster exists, you manage your own users, virtual hosts, permissions, queues, exchanges, bindings and policies with the Messaging Topology Operator resources. This page describes how to order a cluster and which options you can choose.

How to Order

Open a ticket in our Service Desk. State that you want a Message Queues (RabbitMQ) cluster and include the information below.

Information to Include

Field Required Description Example
Cluster Yes The Contain Platform cluster the RabbitMQ cluster runs in. prod1-dc4
Namespace Yes The namespace we provision the RabbitmqCluster in. Your topology resources reference it from the same namespace. your-application-namespace
Cluster name No The name of the RabbitmqCluster resource. We choose one if you leave it out. my-rabbitmq-cluster
Environment Yes Production or non-production. This decides the default size and availability. Production
Size Yes The node count, compute and storage you need. See Options. 3 nodes, small
Expected load No Message rate, message size, number of queues and connections. We use this to validate the size. 500 msg/s, 50 queues
Plugins No RabbitMQ plugins you need beyond the defaults. rabbitmq_shovel
Technical contact Yes The person we contact about the cluster. Name and email

Options

Option Choices Guidance
Node count 1 or 3 Use 1 node for development and test only. Use 3 nodes for production. Quorum queues and streams replicate across nodes and need 3 nodes to tolerate the loss of one.
Compute per node Small, medium or large CPU and memory reserved for each node. RabbitMQ blocks publishers when memory use passes its high watermark, so size memory for the backlog you expect.
Storage per node Size in GiB Disk for persistent messages and quorum queue logs.
RabbitMQ version Current supported version Some features depend on the version. For example, defaultQueueType on a Vhost needs RabbitMQ 3.11.12 or later.
Plugins Default set, plus requested plugins Name any plugin your applications depend on.

What You Receive

When the cluster is ready, we tell you the name of the RabbitmqCluster resource. You set it in spec.rabbitmqClusterReference.name on every topology resource you create.

Changes and Cancellation

To resize, upgrade or remove a cluster, open a new Service Desk ticket that names the cluster and the change you need. Topology resources are your own, so you change them in your GitOps repository without a ticket.

Next Steps

  • Getting Started shows how to create a user, virtual host, permission and queue.
  • The reference/ pages list every field on the topology resources, starting with Reference: User.