coordinator: operator actions, throughput and external reach before adopters run it live

未关闭
#2,724 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
postgresql, prometheus, rust

调研方向

This issue groups several independent operating gaps, and it names crates/registry-coordinator/src/service.rs, crates/registry-coordinator/src/external_http.rs, and products/coordinator/scripts/test-breg-action.py as starting points. Read the linked operate guide's Held runs section and inspect the existing Coordinator API and BReg CI setup. Choose a single item with maintainer guidance; done means that item's behavior or guidance is implemented and verified, since the issue does not define one shared acceptance target.

由索引模型根据 Issue 内容生成。

描述

Registry Coordinator is promised at 1.0. These are the operating gaps an adopter meets once runs are live. Two are tracked already: #2365 (binary, image, clients and source-free tutorial) and #2498 (in-place store migrations from 1.0).

Operator actions

  • A console for operators. Listing runs, the attention queue, and retry-same, reconcile and cancel are available only through coordinatorctl and the HTTP API. Where the console lives (with the Coordinator, in another app, or in a shared operator surface) is not decided yet. The API it needs already exists.
  • End a held run. A run held with definition-refused cannot be ended by the version that holds it: retry-same, reconcile and cancel answer 409 run.definition-incompatible (operate guide, Held runs). An operator needs a recorded way to close such a run without running its steps.

Throughput

  • The worker claims one job, then pauses before the next claim (crates/registry-coordinator/src/service.rs), even when more work is waiting. Keep claiming while work is due.
  • Start many runs from one request (bulk start for N items), with per-item results.
  • Scaling guidance: replicas, database sizing, and the run rate one deployment supports.

External calls

  • External HTTP operations support GET and POST with a bearer token only (crates/registry-coordinator/src/external_http.rs). Add secret-referenced basic, API-key and static-header authorisation, and PUT and PATCH.
  • Review the fixed bounds on external paths and response size against real source APIs.

Proof and operations

  • Run the BReg native journeys (breg_action_native, breg_event_native) in CI. Today only products/coordinator/scripts/test-breg-action.py runs them.
  • Give Rhai functions a wall-clock bound beside the operation bound.
  • Publish example Prometheus alert rules for the attention queue and worker health.
主要语言
Rust
星标
2
派生
0
平均合并
9 小时 48 分钟
30 天内合并 PR
151

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

registrystack/registry-stack 的其他 Issue

查看 registrystack/registry-stack 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。