Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check all devices that write files are using a compatible mount #455

Open
DiamondJoseph opened this issue Apr 22, 2024 · 0 comments
Open
Labels
bug Something isn't working question Further information is requested

Comments

@DiamondJoseph
Copy link
Contributor

ophyd-async devices take a DirectoryProvider, which provides two parts of the resource path: root and resource_path.
This is used by the filewriters to construct a path into the visit directory, where the data should be written and referenced externally.
The current working assumption is that all devices that make use of it will be operating as Kubernetes softIOCs, with the DLS filesystem mounted so as to expose the least access while still allowing for full functionality (i.e. for a device on beamline ixx, it should only expose /data -> /dls/ixx/data, preventing any data being written to the wrong beamline, while still allowing for end of year/change of visit).
Some devices may need to remain non-softIOCs, potentially mounting the whole filesystem /dls -> /dls.

Acceptance Criteria

  • On startup of a selected group of devices, we should be able to check that their mountpoint is mutual.
  • This issue may belong in ophyd-async or blueapi?
@DiamondJoseph DiamondJoseph added bug Something isn't working question Further information is requested labels Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant