1e3c3cb287
IOPS have been modelled as a resource since Nomad 0.1 but has never actually been detected and there is no plan in the short term to add detection. This is because IOPS is a bit simplistic of a unit to define the performance requirements from the underlying storage system. In its current state it adds unnecessary confusion and can be removed without impacting any users. This PR leaves IOPS defined at the jobspec parsing level and in the api/ resources since these are the two public uses of the field. These should be considered deprecated and only exist to allow users to stop using them during the Nomad 0.9.x release. In the future, there should be no expectation that the field will exist. |
||
|---|---|---|
| .. | ||
| affinity.html.md | ||
| artifact.html.md | ||
| check_restart.html.md | ||
| constraint.html.md | ||
| dispatch_payload.html.md | ||
| env.html.md | ||
| ephemeral_disk.html.md | ||
| group.html.md | ||
| index.html.md | ||
| job.html.md | ||
| logs.html.md | ||
| meta.html.md | ||
| migrate.html.md | ||
| network.html.md | ||
| parameterized.html.md | ||
| periodic.html.md | ||
| reschedule.html.md | ||
| resources.html.md | ||
| restart.html.md | ||
| service.html.md | ||
| task.html.md | ||
| template.html.md | ||
| update.html.md | ||
| vault.html.md | ||