Repository navigation
docs: fill the gaps in the Node operator pages - #153
Conversation
Say who can join (compute Nodes with a TES or WES service that requires LS Login tokens; data nodes later), and document the deployment's proTES, TRS-Filer and Poiesis. Mark proWES and DRS-Filer as being revived instead of archived, and remove the CWL-WES page. Closes #81 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewer's GuideConfigurationRemove the CWL-WES entry from the site navigation to match the deleted service page.
DocumentationReview the compute-Node eligibility and onboarding guidance together to check that the TES/WES, LS Login, and Cloud Registry requirements agree across the overview and onboarding pages.
Check the data-centre guidance for consistent storage, DRS, and federation-requirement status.
Review the deployment-specific proTES facts alongside the onboarding tutorial and Cloud Registry guidance that explain how its TES services are configured and discovered.
Check the deployment-specific TRS-Filer address and access policy against the service overview.
Review Poiesis deployment status and gateway behavior together with the related token-group issue reference.
Check that proWES and DRS-Filer are consistently described as being revived and not yet deployed, and remove the obsolete CWL-WES page.
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Documentation build overview
12 files changed ·
|
Linked issuesChecked at commit 9fa8d10 #81 docs: fill the gaps in the Node Operators pages · 3 of 6 met
|
There was a problem hiding this comment.
Hey - I've found 4 issues
Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments
### Comment 1
<location path="docs/operators/index.md" line_range="43" />
<code_context>
1. Read [Onboarding](onboarding.md).
-2. Deploy a TES service and a storage server at your Node.
-3. Register your TES service in the Cloud Registry.
+2. Deploy a TES or WES service and a storage server at your Node.
+3. Register your service in the Cloud Registry.
4. Optional: deploy more [services](services/index.md), and connect your own
</code_context>
<issue_to_address>
**WES-only operators cannot onboard**
When an operator wants to join with only a WES service, the index advertises WES deployment and registration, but the onboarding guide and tutorial cover TES only, and the service list identifies proWES as a gateway rather than a WES implementation. The pages therefore leave WES-only operators without a documented way to complete onboarding.
Provide WES-specific deployment and registration instructions, or remove WES-only Nodes from the advertised joining steps.
Also at `docs/operators/onboarding.md:17`, `docs/operators/onboarding.md:19`, `docs/operators/index.md:31-33`, `docs/operators/node-onboarding-tutorial.md:27`.
</issue_to_address>
### Comment 2
<location path="docs/operators/services/index.md" line_range="24" />
<code_context>
| Service | Standard | Role |
|---|---|---|
| [proTES](protes.md) | [GA4GH TES][ga4gh-tes] | Gateway in front of several TES services. |
-| [CWL-WES](cwlwes.md) | [GA4GH WES][ga4gh-wes] | Archived, unmaintained. Ran CWL workflows on a TES service. |
-| [proWES](prowes.md) | [GA4GH WES][ga4gh-wes] | Archived, unmaintained. Gateway in front of several WES services. |
-| [DRS-Filer](drsfiler.md) | [GA4GH DRS][ga4gh-drs] | Archived, unmaintained. Served data objects. |
</code_context>
<issue_to_address>
**CWL-WES deployment facts absent**
The issue asks for CWL-WES’s address and contents, including which TES it uses. The change removes its service entry without stating whether it is deployed or documenting those facts.
</issue_to_address>
### Comment 3
<location path="docs/operators/services/protes.md" line_range="42-43" />
<code_context>
+gateway](../node-onboarding-tutorial.md#7-get-added-behind-the-gateway)).
+The service info of proTES (`GET /ga4gh/tes/v1/service-info`) lists the TES
+services that it uses. The rest of its configuration, such as its plugins
+and how it authenticates at its TES services, is tracked in
+[generic-issues#31][gi-31].
[gi-31]: <https://github.com/elixir-cloud-aai/generic-issues/issues/31>
</code_context>
<issue_to_address>
**proTES plugins remain unspecified**
The issue asks for the deployment’s proTES plugins, but the page says that plugin configuration is tracked in generic-issues#31 rather than documenting which plugins it uses.
</issue_to_address>
### Comment 4
<location path="docs/operators/services/poiesis.md" line_range="40-41" />
<code_context>
+
+| Node | Address | Status |
+|---|---|---|
+| Czech Republic (CZ) | <https://poiesis.dyn.cloud.e-infra.cz/> | runs; not behind the gateway yet |
+| Finland (FI) | none | not part of the deployment yet |
+
+Poiesis joins the TES services of the [gateway](protes.md) once it checks
</code_context>
<issue_to_address>
**Poiesis storage not documented**
The table identifies which Nodes run Poiesis, but the page does not say which storage it uses.
</issue_to_address>Sourcery assessment
Approval pending. 4 findings to address first.
Blocking findings: docs/operators/index.md:43, docs/operators/services/index.md:24, docs/operators/services/protes.md:43, docs/operators/services/poiesis.md:41
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Summary
Fills the gaps that #81 lists in the Node operator pages, with the maintainers' answers of 2026-11-17:
ECP_CLN:EOC-Computemembers, the FI TESK as its TES service, registry discovery off); the tutorial and "Using the Cloud Registry" now say that it lists its TES services in its configuration. TRS-Filer page: https://trs-filer.rahtiapp.fi/ga4gh/trs/v2, public reads, writes with LS Login tokens under the same access rules as the Cloud Registry. proWES and DRS-Filer: "Archived" notes replaced by "Being revived" (unarchived 2026-11-16; not deployed yet; docs follow with the revival). CWL-WES: page and nav entry removed, no more references in the Node operator pages.The deployment-specific facts are in "In the ELIXIR On-Cloud" sections marked "As of November 2026", so that they are easy to find and update.
Removing
operators/services/cwlwes.mddrops its URL; the site has no redirect plugin.Closes #81
Verification
python scripts/check_names.py: passesmkdocs build --strict: passes, no warningspytest: 25 passed, 100% coverage (unchanged)GET /service-info(proTES 0.6.0, TES 1.1.0), Poiesis CZ answers 200.Declined review findings
Review
Light lane: docs only. I reviewed the diff myself.
🤖 Generated with Claude Code