open-nomad/scheduler
Yorick Gersie 2a5c423ae0
Allow per_alloc to be used with host volumes (#15780)
Disallowing per_alloc for host volumes in some cases makes life of a nomad user much harder.
When we rely on the NOMAD_ALLOC_INDEX for any configuration that needs to be re-used across
restarts we need to make sure allocation placement is consistent. With CSI volumes we can
use the `per_alloc` feature but for some reason this is explicitly disabled for host volumes.

Ensure host volumes understand the concept of per_alloc
2023-01-26 09:14:47 -05:00
..
benchmarks
annotate.go
annotate_test.go
context.go
context_test.go
device.go
device_test.go
feasible.go Allow per_alloc to be used with host volumes (#15780) 2023-01-26 09:14:47 -05:00
feasible_test.go Allow per_alloc to be used with host volumes (#15780) 2023-01-26 09:14:47 -05:00
generic_sched.go scheduler: log stack in case of panic (#15303) 2022-11-17 18:59:33 -05:00
generic_sched_test.go
preemption.go
preemption_test.go
propertyset.go
rank.go
rank_test.go
reconcile.go scheduler: create placements for non-register MRD (#15325) 2022-11-25 12:45:34 -05:00
reconcile_test.go scheduler: create placements for non-register MRD (#15325) 2022-11-25 12:45:34 -05:00
reconcile_util.go
reconcile_util_test.go
scheduler.go
scheduler_oss.go
scheduler_sysbatch_test.go
scheduler_system.go scheduler: log stack in case of panic (#15303) 2022-11-17 18:59:33 -05:00
scheduler_system_test.go scheduler: set job on system stack for CSI feasibility check (#15372) 2022-11-23 16:47:35 -05:00
select.go
select_test.go
spread.go
spread_test.go
stack.go Allow per_alloc to be used with host volumes (#15780) 2023-01-26 09:14:47 -05:00
stack_oss.go
stack_test.go
testing.go
util.go
util_test.go