[runner-scale 2/3] feat(infra): IInfraProvider abstraction + runner-ops orchestration + CLI#2
Open
lilongen wants to merge 1 commit into
Open
Conversation
AwsInfraProvider/LocalProcessInfraProvider + factory; addSharedRunner/scaleDownRunner libs; CLI add/scale-down scripts + dev wrappers + test-setup; per-env backups-bucket config + release-repo/version overrides. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
lilongen
pushed a commit
that referenced
this pull request
May 29, 2026
Before: the local otel-collector exported every pipeline to `debug` (stdout) only, and the jaeger box's OTLP receiver wasn't host-mapped or fed by anything. Net result — the Jaeger UI at :26686 was always empty; traces sent to the collector died at the debug exporter. (Flagged in review by DorianZheng.) Fix (option a — keep the collector in the path for prod parity): - SPEC_JAEGER: host-map jaeger's OTLP gRPC receiver (26687 → box :4317). jaeger 1.67 all-in-one already has COLLECTOR_OTLP_ENABLED=true. - _OTEL_CONFIG → _otel_config(cfg): add an `otlp/jaeger` exporter (host.boxlite.internal:26687, tls insecure) and add it to the *traces* pipeline alongside debug. metrics/logs stay debug-only (Jaeger doesn't ingest them). - SPEC_OTEL: depends_on=["jaeger"] so the export target is up first. Verified end-to-end on a live stack: POST an OTLP/HTTP trace to the collector (:24318) → within 2s the Jaeger query API returns the service and the trace. 35 unit tests pass (topo sort handles the new otel→jaeger edge). Docs updated (README §Known-limitations #2, CONNECTIONS §6/§8) — the "Jaeger pipeline not connected" limitation is removed; the remaining gap is only the custom boxlite_exporter build (ClickHouse/api push-back). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
lilongen
pushed a commit
that referenced
this pull request
Jun 9, 2026
lilongen
pushed a commit
that referenced
this pull request
Jun 9, 2026
Before: the local otel-collector exported every pipeline to `debug` (stdout) only, and the jaeger box's OTLP receiver wasn't host-mapped or fed by anything. Net result — the Jaeger UI at :26686 was always empty; traces sent to the collector died at the debug exporter. (Flagged in review by DorianZheng.) Fix (option a — keep the collector in the path for prod parity): - SPEC_JAEGER: host-map jaeger's OTLP gRPC receiver (26687 → box :4317). jaeger 1.67 all-in-one already has COLLECTOR_OTLP_ENABLED=true. - _OTEL_CONFIG → _otel_config(cfg): add an `otlp/jaeger` exporter (host.boxlite.internal:26687, tls insecure) and add it to the *traces* pipeline alongside debug. metrics/logs stay debug-only (Jaeger doesn't ingest them). - SPEC_OTEL: depends_on=["jaeger"] so the export target is up first. Verified end-to-end on a live stack: POST an OTLP/HTTP trace to the collector (:24318) → within 2s the Jaeger query API returns the service and the trace. 35 unit tests pass (topo sort handles the new otel→jaeger edge). Docs updated (README §Known-limitations #2, CONNECTIONS §6/§8) — the "Jaeger pipeline not connected" limitation is removed; the remaining gap is only the custom boxlite_exporter build (ClickHouse/api push-back). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
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.
Part 2 of 3 of the runner-scale work.
IInfraProvider(AwsInfraProvider / LocalProcessInfraProvider / factory) + the 7-stage add-shared and 10-stage scale-down orchestration libs and their CLIs. Includes the runner-user-data builder.Stacked on #1 (base
feat/runner-scale-1-backup); review/merge PR1 first.