Ask whether the durable data tier is reachable at all - #702
Merged
Conversation
The plan for registering the DM-tier copy of a scan file rested on /gdata/dm/2BM being readable from tomdet, over the SSH hop the scan probe already uses. That was never established. The 2026-08-11 check behind HOST-2 found /gdata invisible from arcturus and covered no other host, so the tomdet case is untested rather than confirmed. It gates a design rather than a setting: if tomdet cannot see the tree, CORA needs a different host or a DM-side listing interface to observe the durable copy, which is a different slice from the one planned. Ask the beamline instead of assuming, and accept a pointer to whichever host can read it as an equally complete answer.
Coverage report
This PR does not seem to contain any modification to coverable code. |
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
1 participant
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.
Why
Planning the slice that registers the APS Data Management copy of a scan file, I went to confirm the fact the whole design rests on: that
/gdata/dm/2BMis readable fromtomdet, over the SSH hop CORA's scan probe already uses.It is not confirmed. The 2026-08-11 check behind HOST-2 found
/gdatainvisible fromarcturusand covered no other host. Two successive plans carried thetomdetmount as established fact anyway.Why it blocks rather than defaults
If
tomdetcannot see the tree, CORA needs a different host or a DM-side listing interface to observe the durable copy. That is a different slice, not a setting, so guessing would mean building the wrong thing and finding out at go-live.The DM copy is also the one that matters most: every upstream tier is capacity-purged, and
/data2was lost outright on 2026-08-14. A record naming only/local1points at bytes that will be gone.The row
One
Blocks-go-livequestion in the 2-BM open-questions page, phrased so that naming whichever host can read the tree counts as a complete answer rather than a partial one.Docs only.
make docs-buildpasses with--strict.🤖 Generated with Claude Code