-
Notifications
You must be signed in to change notification settings - Fork 2
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
determine log file/discovery report location for user job output #78
Comments
further elaboration: this won't be a single log file for everything. it'll likely be a pre-determined sub-path within the user's pre-assembly bundle (thus, different for every job, but easily computed from user input). |
We discussed earlier today that many of the mounts are read-only to the preassembly server. Would consider choosing a single writable path for this. Slightly aged list of mount paths is here: https://consul.stanford.edu/display/CollAcc/Content+Mount+Paths - I'll take a pass and make sure this is up to date. |
We could also use the dumbest of document stores as the permanent persistence home for "output" files. |
|
should be deterministic/predetermined, should not be specified by users of the web app.
work break down:
user_id/bundle_dir
portion of path will be deterministically computed from bundlecontext (Job output parent dir #311)Plan:
(writeable_parent_dir)/user_id/bundle_dir/job_output_here.whatever
requirements:
NOTE: this does not mean there aren't other ways to do this, e.g. use the database to store all the artifacts, or use the database to assign the unique location for the files ... just for now, the team agreed the file system was the easiest way forward, especially since Ben occasionally has had to manually delete progress files.
The text was updated successfully, but these errors were encountered: