mvp v6 phase D pre-work: workload + freshness probes + multi-stage overlay - #294
Merged
Merged
Conversation
…erlay Pre-work for v6's Phase D (workload + freshness wiring) — these are static input files Phase E's driver will consume. No code coupling; zero overlap with v5-author or v6-Phase-B which are in flight. deploy/configs/mvp-v6-workload.yaml Four entries covering the three canonical query classes (window, label, combined) plus an ad-hoc cold-fallback probe targeting the Gorilla archive tier. Schema mirrors workloads.yaml; controller's L1→L5 pipeline plans against this. deploy/configs/mvp-v6-freshness-probes.yaml Schema for three timestamp-encoded synthetic counters (raw / warm / archive). Replay client computes Δ = poll_ts − observed_value. Plumbing note flagged for Phase E: fake-exporter needs a small extension to emit these three metrics. deploy/docker-compose/mvp-v6-multi-stage.yml 10 fake-exporters (5+5 → agent-a/agent-b) → 1 gateway → 1 backend topology, with a `b0` profile that brings up real Prometheus for the baseline. Cardinality knobs (PER_AGENT_CARDINALITY × 10 producers) match the production-pyramid pattern from the v6 spec. Placeholder agent + gateway configs default to v4's overlays until Phase B's controller-emitted YAMLs are ready to drop in. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
zzylol
added a commit
that referenced
this pull request
May 6, 2026
* mvp v6: gateway placeholder config + controller workload mount Two follow-ons to the Phase D pre-work overlay (#294): deploy/configs/sketchcol-gateway-mvp-v6-placeholder.yaml Gateway sketchcol config the multi-stage overlay references. Shape-correct (OTLP receiver / memory_limiter / batch / OTLP-backend exporter) so the gateway stands up; sketch-merge processors are intentionally absent until Phase B's emit_gateway_yaml replaces this YAML with the controller's plan. deploy/docker-compose/mvp-v6-multi-stage.yml Mount mvp-v6-workload.yaml into the controller container as /etc/asap/mvp-v6-workload.yaml; set CONTROLLER_WORKLOADS env so the controller reads it at startup. Set USE_TYPED_STAGE_SPLIT=1 so when Phase B's emitter is wired the typed stage-split path fires automatically. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * mvp v6: mount workload manifest into controller container Follow-up to the gateway placeholder commit — the actual mvp-v6-workload.yaml mount + CONTROLLER_WORKLOADS env-var setting landed here instead of the prior commit (Edit needed a prior Read). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Static inputs for v6 Phase D wiring — files only, no code coupling. Builds the substrate Phase E driver consumes.
Files
deploy/configs/mvp-v6-workload.yaml— 4 entries: 3 query classes (window-per-series quantile, label-at-instant sum-by, combined window+label) + 1 ad-hoc cold-fallback probedeploy/configs/mvp-v6-freshness-probes.yaml— schema for 3 timestamp-encoded counters (raw / warm / archive); flags a small fake-exporter extension Phase E will needdeploy/docker-compose/mvp-v6-multi-stage.yml— 10 producer / 2 agent / 1 gateway / 1 backend / optional Prometheus topology following the v6 specWhy
v5-author (#51) and v6-Phase-B (#53) are in flight; this work is in different files (no overlap) so it's free productivity time. When Phase B lands its emitter, Phase C will drop the controller-emitted YAMLs into the agent/gateway config slots in this overlay.
Test plan
yamllintwould pass)docker compose config -f base.yml -f mvp-v6-multi-stage.yml— verified separately)🤖 Generated with Claude Code