mirror of
https://github.com/kemko/nomad.git
synced 2026-01-01 16:05:42 +03:00
3a11a0b1e1
In anticipation of having quotas for dynamic host volumes, we want the user experience of the storage limits to feel integrated with the other resource limits. This is currently prevented by reusing the `Resources` type instead of having a specific type for `QuotaResources`. Update the quota limit/usage types to use a `QuotaResources` that includes a new storage resources quota block. The wire format for the two types are compatible such that we can migrate the existing variables limit in the FSM. Also fixes improper parallelism in the quota init test where we change working directory to avoid file write conflicts but this breaks when multiple tests are executed in the same process. Ref: https://github.com/hashicorp/nomad-enterprise/pull/2096
12 lines
543 B
Plaintext
12 lines
543 B
Plaintext
```release-note:breaking-change
|
|
api: QuotaSpec.RegionLimit is now of type QuotaResources instead of Resources
|
|
```
|
|
|
|
```release-note:deprecation
|
|
api: QuotaSpec.VariablesLimit field is deprecated and will be removed in Nomad 1.12.0. Use QuotaSpec.RegionLimit.Storage.Variables instead.
|
|
```
|
|
|
|
```release-note:deprecation
|
|
quotas: the variables_limit field in the quota specification is deprecated and replaced by a new storage block under the region_limit block, with a variables field. The variables_limit field will be removed in Nomad 1.12.0
|
|
```
|