Skip to content

RabbitMQ service: definitions backup and the restore drill (S-023-16, S-023-17) #511

Closed

Description

@shipmill-romamo

Builds part of spec S-023, docs/specs/023-rabbitmq-service.md: the acceptance criteria below. Each needs a test that names its id (test_s023_<k>_..., or a proves: S-023-16 comment line).

Scope: cloudfall-rabbitmq-backup behind backup run (the export, its mode, retention, a receipt that states the backup holds no messages) and cloudfall-rabbitmq-restore-check behind backup verify (the scratch node, the comparison, its removal).

  • S-023-16: cloudfall backup run rabbitmq-main writes one export, 0600 and root-owned, and a BackupReceipt that states the backup holds no messages; cloudfall backup verify rabbitmq-main imports the export into a scratch node, finds the same virtual hosts, users, queues, exchanges, bindings and policies, removes the scratch node and its directory, and writes its receipt; with no export it fails and says so; the scratch node is never a member of the cluster, and no process or listener of it is left
  • S-023-17: Exports older than retentionDays are gone after the next backup run, and the newest is kept

Depends on #506

Activity

  1. shipmill-romamo commented on Nov 17, 2026

    @shipmill-romamo
    ContributorAuthor

    Triage: implement. Serves: G-1, G-3.

    Builds S-023-16 and S-023-17 of spec 023 (docs/specs/023-rabbitmq-service.md, approved in #500), for #502: the definitions export behind backup run and the import into a scratch node behind backup verify, with a receipt that says a backup holds no message, as the body above scopes it.

    It starts once #506 (one node converged) closes; its Depends on line holds it until then. I'll link the PR here.

  2. shipmill-romamo commented on Nov 18, 2026

    @shipmill-romamo
    ContributorAuthor

    PR: #540. It installs cloudfall-rabbitmq-backup (the definitions export, root-owned and 0600, retention by retentionDays, never the newest) and cloudfall-rabbitmq-restore-check (a scratch node with its own name, cookie, data directory and loopback ports, compared with the export, then stopped and removed on every path) on spec.server, each with a timer; backup.yml writes holdsMessages: false in the receipt for RabbitMQ.

    Proven by tests: S-023-17 in full, and S-023-16 against stand-in RabbitMQ tools and backup.yml on localhost. Not verified on a real host: RabbitMQ 4.x importing an export at start without creating guest and / (the drill fails and names them if it does), the scratch node's real listeners and processes, and the Debian paths it calls. The live run that proves spec 023 covers them.

    The receipt's field name and the scratch node's fixed values are on the PR as decided comments. The guide (docs/rabbitmq-service-guide.md) had no build issue: filed separately.

  3. added a commit that references this issue on Nov 18, 2026
    135ae28
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