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

オープン
#2,724 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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分
マージ済み PR(30日)
151

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

registrystack/registry-stack のほかの issue

registrystack/registry-stack の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。