photoncloud-monorepo/docs/por/T026-practical-test/task.yaml
centra a7ec7e2158 Add T026 practical test + k8shost to flake + workspace files
- Created T026-practical-test task.yaml for MVP smoke testing
- Added k8shost-server to flake.nix (packages, apps, overlays)
- Staged all workspace directories for nix flake build
- Updated flake.nix shellHook to include k8shost

Resolves: T026.S1 blocker (R8 - nix submodule visibility)
2025-12-09 06:07:50 +09:00

94 lines
2.8 KiB
YAML

id: T026
name: MVP-PracticalTest
goal: Validate MVP stack with live deployment smoke test (FlareDB→IAM→k8shost)
status: active
priority: P0
owner: peerB (implementation)
created: 2025-12-09
depends_on: [T025]
blocks: [T027]
context: |
MVP-K8s achieved (T025 complete). Before production hardening, validate the
integrated stack with live deployment testing.
PROJECT.md emphasizes 実戦テスト (practical testing) - this task delivers that.
Standard engineering principle: validate before harden.
Smoke test reveals integration issues early, before investing in HA/monitoring.
acceptance:
- All 9 packages build successfully via nix
- NixOS modules load without error
- Services start and pass health checks
- Cross-component integration verified (FlareDB→IAM→k8shost)
- Configuration unification validated
- Deployment issues documented for T027 hardening
steps:
- step: S1
name: Environment Setup
done: NixOS deployment environment ready, all packages build
status: in_progress
owner: peerB
priority: P0
notes: |
Prepare clean NixOS deployment environment and verify all packages build.
Tasks:
1. Build all 9 packages via nix flake
2. Verify NixOS modules load without error
3. Attempt to start systemd services
4. Document any build/deployment issues
Success Criteria:
- 9 packages build: chainfire, flaredb, iam, plasmavmc, novanet, flashdns, fiberlb, lightningstor, k8shost
- Command: nix build .#chainfire .#flaredb .#iam .#plasmavmc .#novanet .#flashdns .#fiberlb .#lightningstor .#k8shost
- NixOS modules load without syntax errors
- Services can be instantiated (even if they fail health checks)
Non-goals:
- Service health checks (deferred to S2-S4)
- Cross-component integration (deferred to S5)
- Configuration tuning (handled as issues found)
- step: S2
name: FlareDB Smoke Test
done: FlareDB starts, accepts writes, serves reads
status: pending
owner: peerB
priority: P0
- step: S3
name: IAM Smoke Test
done: IAM starts, authenticates users, issues tokens
status: pending
owner: peerB
priority: P0
- step: S4
name: k8shost Smoke Test
done: k8shost starts, creates pods with auth, assigns IPs
status: pending
owner: peerB
priority: P0
- step: S5
name: Cross-Component Integration
done: Full stack integration verified end-to-end
status: pending
owner: peerB
priority: P0
- step: S6
name: Config Unification Verification
done: All components use unified configuration approach
status: pending
owner: peerB
priority: P0
blockers: []
evidence: []
notes: |
T027 (Production Hardening) is BLOCKED until T026 passes.
Smoke test first, then harden.