Feature #22029
closedarvados-dispatch-cloud option to use a different directory than /tmp for staging the crunch-run binary
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.
Updated by Peter Amstutz 4 months ago
- Related to Bug #21999: Support compute nodes with /tmp mounted with "noexec" flag added
Updated by Peter Amstutz 4 months ago
- Target version changed from Development 2024-08-28 sprint to Development 2024-09-11 sprint
Updated by Peter Amstutz 4 months ago
- Target version changed from Development 2024-09-11 sprint to Development 2024-09-25 sprint
Updated by Peter Amstutz 3 months ago
- Target version changed from Development 2024-09-25 sprint to Development 2024-10-09 sprint
Updated by Peter Amstutz 3 months ago
- Target version changed from Development 2024-10-09 sprint to Development 2024-10-23 sprint
Updated by Peter Amstutz 2 months ago
- Target version changed from Development 2024-10-23 sprint to Development 2024-11-06 sprint
Updated by Peter Amstutz about 2 months ago
- Target version changed from Development 2024-11-06 sprint to Development 2024-11-20
Updated by Peter Amstutz about 2 months ago
- Target version changed from Development 2024-11-20 to Development 2024-12-04
Updated by Peter Amstutz about 1 month ago
- Target version changed from Development 2024-12-04 to Development 2024-11-20
Updated by Tom Clegg about 1 month ago
- Status changed from New to In Progress
- Description updated (diff)
Updated by Tom Clegg about 1 month ago
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
- New config is
- Anything not implemented (discovered or discussed during work) has a follow-up story.
- N/A
- Code is tested and passing, both automated and manual, what manual testing was done is described.
- N/A
- New or changed UX/UX and has gotten feedback from stakeholders.
- N/A
- Documentation has been updated.
- N/A, assuming the config-default comment plus the existing advice to Refer to config.defaults.yml for information about additional configuration options is appropriate since the default is expected to work in most setups.
- Behaves appropriately at the intended scale (describe intended scale).
- N/A
- Considered backwards and forwards compatibility issues between client and server.
- N/A
- Follows our coding standards and GUI style guidelines.
- ✅
Updated by Lucas Di Pentima about 1 month ago
That was easy! This LGTM, thanks!
Updated by Tom Clegg about 1 month ago
- Status changed from In Progress to Resolved
Applied in changeset arvados|575a6df71cf9176aa2757ea72c4604784963f6ab.