Migrate Nova PostgreSQL workloads to Cosmos #120

Open
opened 2026-07-29 00:11:56 +01:00 by nimmo · 0 comments
Owner

Move the required PostgreSQL consumers from Nova's Docker PostgreSQL stack to
Cosmos over Nebula, then retire the Nova stack after validation and a rollback
window.

The full database inventory, live-consumer evidence, extension preflight,
cutover checklist, and rollback procedure are in Trilium:
https://notes.nimmog.uk/#root/oFrCkPmeUpeF/gfucXEji9FL6

Scope decisions: airtrail and mem0 are archive-only; do not restore them to
Cosmos. This removes the need to add pgvector for this migration.

Completion requires every remaining database to be classified as migrate or
archive-only, successful dump/restore and service validation for migrated
consumers, then removal of Nova's published PostgreSQL/Adminer stack after the
rollback window.

Move the required PostgreSQL consumers from Nova's Docker PostgreSQL stack to Cosmos over Nebula, then retire the Nova stack after validation and a rollback window. The full database inventory, live-consumer evidence, extension preflight, cutover checklist, and rollback procedure are in Trilium: https://notes.nimmog.uk/#root/oFrCkPmeUpeF/gfucXEji9FL6 Scope decisions: airtrail and mem0 are archive-only; do not restore them to Cosmos. This removes the need to add pgvector for this migration. Completion requires every remaining database to be classified as migrate or archive-only, successful dump/restore and service validation for migrated consumers, then removal of Nova's published PostgreSQL/Adminer stack after the rollback window.
Sign in to join this conversation.
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
nimmo/nixos-config#120
No description provided.