Skip to content

RabbitMQ as a Service kind: one node or a cluster of three #502

Open
4 of 9 issues completed
Open

Description

@shipmill-romamo

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

  1. serviceKind: rabbitmq with an exact pinned and held version of a series in community support, a declared memory watermark and a data volume
  2. 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
  3. One node configured as a cluster that waits for two more, with quorum queues by default, so growing is adding servers and converging
  4. Virtual hosts with an owner whose password reaches the nodes only as a hash (D-9); guest and / are removed
  5. Rolling version changes, inside a series and to the next one
  6. 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
  7. 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
  8. 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.

Depends on #505

Depends on #506

Depends on #507

Depends on #508

Depends on #509

Depends on #510

Depends on #511

Depends on #512

Depends on #543

Activity

  1. shipmill-romamo commented on Nov 17, 2026

    @shipmill-romamo
    ContributorAuthor

    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:

    This issue closes once the last of them does and the spec reads status: built with every criterion verified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions