Migrate Nova PostgreSQL workloads to Cosmos #120
Labels
No labels
host:electra
host:fleet
host:lyra
host:vega
host:vega
phase:cutover
phase:deploy
phase:mcp
phase:module
phase:packaging
phase:prep
phase:validation
project:attic-postgres-lyra-rollout
project:auto-update-reliability
project:declarative-purity-cleanup
project:external-review
project:host-facts-refactor
project:lyra-nixos-deploy
project:lyra-service-stack-migration
project:nebula-mesh-network
project:security-hardening
project:service-stack-migration
project:vega-sillytavern-cutover
service:auto-update
service:mem0
service:sillytavern
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
nimmo/nixos-config#120
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.