You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
RabbitMQ as a Service kind: one node or a cluster of three #502
Requested by: @romamo (filed by an agent on his instruction, 2026-11-17)
Spec: docs/specs/023-rabbitmq-service.md, approved and merged in #500.
Problem
A fleet whose application passes its work through RabbitMQ operates it by hand: the package and its pin, the Erlang it needs, the data volume, the memory watermark, the cluster and its shared cookie, TLS between the nodes, one user per virtual host, the copy of each queue on the other nodes, and a backup of what a broker holds besides messages.
Cloudfall cannot describe any of it today:
Service kinds are postgresql, redis, elasticsearch and mariadb only
config validate, audit, backup run and backup verify know nothing about a RabbitMQ node, so an agent has no operation to propose for it
Nothing declares a cluster of equal nodes that needs a majority
Proposal
serviceKind: rabbitmq with an exact pinned and held version of a series in community support, a declared memory watermark and a data volume
One node or three in one Service. The nodes are equals, so there is no primary, no promotion and no failover; two nodes are refused
One node configured as a cluster that waits for two more, with quorum queues by default, so growing is adding servers and converging
Virtual hosts with an owner whose password reaches the nodes only as a hash (D-9); guest and / are removed
Rolling version changes, inside a series and to the next one
Replacing a lost node by naming the new server; a node that holds data is never emptied, and none is forced to continue without a majority
Definitions export behind backup run and an import into a scratch node behind backup verify; a backup holds no message, and the receipt says so
Audit and metrics as for the other kinds, plus the state of the cluster and of its quorum queues
Out of scope
A backup of messages, two nodes or more than three, streams, the management plugin and every plugin but the Prometheus one, topology in the declaration, Erlang from another source than the Debian release, moving in from a server Cloudfall does not manage. Connections with a generated user per connection stay with #216.
Triage: feature. Serves: G-1, G-3. RabbitMQ as a fourth Service kind (one node, or three equal nodes in a cluster) is new behaviour, not a bug fix or a contract tweak.
The spec is docs/specs/023-rabbitmq-service.md, approved and merged in #500. Its build is split into eight issues, recorded in the spec's Issues section by #513 and linked here as sub-issues:
Activity
shipmill-romamo commentedon Nov 17, 2026
Triage: feature. Serves: G-1, G-3. RabbitMQ as a fourth
Servicekind (one node, or three equal nodes in a cluster) is new behaviour, not a bug fix or a contract tweak.The spec is
docs/specs/023-rabbitmq-service.md, approved and merged in #500. Its build is split into eight issues, recorded in the spec's Issues section by #513 and linked here as sub-issues:This issue closes once the last of them does and the spec reads
status: builtwith every criterion verified.