Feature #22029
closed
arvados-dispatch-cloud option to use a different directory than /tmp for staging the crunch-run binary
Added by Peter Amstutz 3 months ago.
Updated 9 days ago.
Description
Arvados dispatch cloud by default copies itself to /tmp when launching a new compute node instance, which does not work if /tmp is mounted noexec, for example. Currently the only workaround is to disable automatic crunch-run installation and place the burden back on the admin to install/upgrade crunch-run on every compute node/image.
It would be much better to offer configuration option that tells arvados-dispatch-cloud where to install the crunch-run binary.
- Related to Bug #21999: Support compute nodes with /tmp mounted with "noexec" flag added
- Description updated (diff)
- Description updated (diff)
- Target version changed from Development 2024-08-28 sprint to Development 2024-09-11 sprint
- Target version changed from Development 2024-09-11 sprint to Development 2024-09-25 sprint
- Target version changed from Development 2024-09-25 sprint to Development 2024-10-09 sprint
- Target version changed from Development 2024-10-09 sprint to Development 2024-10-23 sprint
- Assigned To set to Tom Clegg
- Target version changed from Development 2024-10-23 sprint to Development 2024-11-06 sprint
- Target version changed from Development 2024-11-06 sprint to Development 2024-11-20
- Target version changed from Development 2024-11-20 to Development 2024-12-04
- Target version changed from Development 2024-12-04 to Development 2024-11-20
- Status changed from New to In Progress
- Description updated (diff)
22029-crunch-run-install-dir @ ed27877f50a6c05dbfc14a511f7222977671cc5e -- developer-run-tests: #4552 
22029-crunch-run-install-dir @ ed27877f50a6c05dbfc14a511f7222977671cc5e -- developer-run-tests: #4554 
- All agreed upon points are implemented / addressed. Describe changes from pre-implementation design.
- New config is
Containers.CloudVMs.DeployRunnerDirectory
- Anything not implemented (discovered or discussed during work) has a follow-up story.
- Code is tested and passing, both automated and manual, what manual testing was done is described.
- New or changed UX/UX and has gotten feedback from stakeholders.
- Documentation has been updated.
- Behaves appropriately at the intended scale (describe intended scale).
- Considered backwards and forwards compatibility issues between client and server.
- Follows our coding standards and GUI style guidelines.
That was easy! This LGTM, thanks!
- Status changed from In Progress to Resolved
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by