Actions
Feature #14713
closedcrunch-dispatch-slurm uses cluster config file
Added by Peter Amstutz almost 6 years ago. Updated almost 5 years ago.
Story points:
1.0
Release:
Release relationship:
Auto
Related issues
Updated by Peter Amstutz almost 6 years ago
- Status changed from New to In Progress
Updated by Peter Amstutz almost 6 years ago
- Status changed from In Progress to New
Updated by Peter Amstutz almost 6 years ago
- Related to Idea #13648: [Epic] Use one cluster configuration file for all components added
Updated by Lucas Di Pentima almost 6 years ago
Based on the documentation at https://doc.arvados.org/install/crunch2-slurm/install-dispatch.html
We may have multiple dispatchers so I think we would need a section for them, identified by hostname. AuthToken
was included inside an individual dispatcher section because the docs say that every dispatcher should have its own token.
NodeProfiles: apiserver: Dispatcher: slurm1 Timers: MinRetryPeriod: 30s ContainerDispatchPollInterval: 10s (already listed on the wiki) Dispatchers: slurm1: AuthToken: zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz KeepServiceURIs: 1: http://127.0.0.1:25107 PrioritySpread: 1000 SbatchArguments: partition: PartitionName CrunchRunParams: cgroup-parent-subsystem: memory container-enable-networking: always container-network-mode: host ReserveExtraRAM: 268435456
Updated by Tom Morris almost 6 years ago
- Target version changed from To Be Groomed to Arvados Future Sprints
- Story points set to 1.0
Updated by Tom Morris over 5 years ago
- Target version changed from Arvados Future Sprints to 2019-07-17 Sprint
Updated by Peter Amstutz over 5 years ago
- Status changed from New to In Progress
Updated by Peter Amstutz over 5 years ago
- Target version changed from 2019-07-17 Sprint to 2019-07-31 Sprint
Updated by Peter Amstutz over 5 years ago
Updated by Eric Biagiotti over 5 years ago
Peter Amstutz wrote:
14713-cds-new-config @ 726881f8950e4f361193a612c66c90ca9535e81a
https://ci.curoverse.com/view/Developer/job/developer-run-tests/1401/
I reviewed the code and don't have any comments, but there are some test failures on jenkins that need a look.
Updated by Peter Amstutz over 5 years ago
- Status changed from In Progress to Resolved
Actions