For a tool designed to test storage, there are few if any storage path options #245
russfellows
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As a tool that is designed to primarily test storage, and does so on **nix based systems, the primary method and mechanism for specifying storage to use during testing is a path, typically a full path starting with a "/". All of this is quite obvious, however; there does not appear to be any mechanism to specify a storage device, and/or path to use during testing.
Within the yaml config files, there are only two places where a path is specified, and in both instances they appear to be relative paths. These being the fields:
In testing, I have changed the values from their defaults, and specified fully qualified paths, such as "/mnt/my-vol" to be used for the dataset and checkpoint folders. In neither case do these appear to be used.
As mentioned, the concept of specifying a path to use for storage testing should be one of the primary features documented, yet it appears to be completely hidden, or lacking altogether.
Does documentation exist for specifying a storage location for testing? If so, perhaps adding to the existing docs and examples would be VERY helpful.
Beta Was this translation helpful? Give feedback.
All reactions