[Task] Wave 0 ops health, readiness, and deployment profile surfaces #1

Closed
opened 2026-07-08 20:45:33 +02:00 by zemion · 1 comment
Owner

Goal

Give operators a clear Wave 0 view of deployment health, readiness, scaling posture, and profile-specific configuration gaps.

Scope

  • Surface core health/readiness, database, worker, queue/cache, storage, module, and installer daemon status.
  • Distinguish development, staging, pilot, and production profile warnings.
  • Link to PostgreSQL migration checks, module permutation checks, rollback drills, and deployment runbooks.
  • Keep ops display read-only unless a separate admin-controlled operation explicitly owns mutation.

Acceptance Criteria

  • Operators can tell whether the instance is ready for normal traffic, maintenance, or package changes.
  • Missing Redis/workers/PostgreSQL/storage/certificates are classified by profile and not as generic failures.
  • Health/deployment profile docs and UI use the same terminology.
  • The view works with partial module deployments.
  • govoplan-core#217 scalability profiles and autoscaling readiness.
  • govoplan-core#219 hardware sizing matrix and requirements calculator.
## Goal Give operators a clear Wave 0 view of deployment health, readiness, scaling posture, and profile-specific configuration gaps. ## Scope - Surface core health/readiness, database, worker, queue/cache, storage, module, and installer daemon status. - Distinguish development, staging, pilot, and production profile warnings. - Link to PostgreSQL migration checks, module permutation checks, rollback drills, and deployment runbooks. - Keep ops display read-only unless a separate admin-controlled operation explicitly owns mutation. ## Acceptance Criteria - Operators can tell whether the instance is ready for normal traffic, maintenance, or package changes. - Missing Redis/workers/PostgreSQL/storage/certificates are classified by profile and not as generic failures. - Health/deployment profile docs and UI use the same terminology. - The view works with partial module deployments. ## Related - govoplan-core#217 scalability profiles and autoscaling readiness. - govoplan-core#219 hardware sizing matrix and requirements calculator.
Author
Owner

Implemented and verified.

  • Ops status/readiness surfaces database, module, installer, worker/queue/cache, storage, profile, and deployment-security signals.
  • Added profile-aware deployment_security classification: inactive for local/test, warning for non-prod gaps, readiness-critical only for production profile blockers.
  • UI/API terminology and docs are aligned in govoplan-ops/docs/SCALABILITY_PROFILES.md.
  • Focused checks: ops route py-compile and the core ops smoke test passed.
Implemented and verified. - Ops status/readiness surfaces database, module, installer, worker/queue/cache, storage, profile, and deployment-security signals. - Added profile-aware `deployment_security` classification: inactive for local/test, warning for non-prod gaps, readiness-critical only for production profile blockers. - UI/API terminology and docs are aligned in `govoplan-ops/docs/SCALABILITY_PROFILES.md`. - Focused checks: ops route py-compile and the core ops smoke test passed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-ops#1
No description provided.