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

Ouverte
#2,724 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
postgresql, prometheus, rust

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.
Langage dominant
Rust
Étoiles
2
Forks
0
Merge moyen
9 h 48 min
PR mergées (30 j)
151

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de registrystack/registry-stack

Toutes les issues de registrystack/registry-stack

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.