luxolus
/
open-nomad
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Added warning about impossible constraints 

This was as a resolution to https://github.com/hashicorp/nomad/issues/4424
This commit is contained in:
Charlie Voiselle 2018-06-19 09:27:16 -04:00
parent 9d75c5192a
commit a3780d37e2
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
website/source/docs/job-specification/constraint.html.md
View File

@ -28,6 +28,11 @@ filter on [attributes][interpolation] or [client metadata][client-meta].
Additionally constraints may be specified at the [job][job], [group][group], or
[task][task] levels for ultimate flexibility.
~> **It is possible to define irreconcilable constraints in a job.**
For example, because all [tasks within a group are scheduled on the same client node][group],
specifying different [`${attr.unique.hostname}`][node-variables] constraints at
the task level will cause a job to be unplaceable.
```hcl
job "docs" {
# All tasks in this job must run on linux.
@ -59,6 +64,7 @@ Placing constraints at both the job level and at the group level is redundant
since constraints are applied hierarchically. The job constraints will affect
all groups (and tasks) in the job.
## `constraint` Parameters
- `attribute` `(string: "")` - Specifies the name or reference of the attribute
@ -273,3 +279,4 @@ constraint {
[client-meta]: /docs/agent/configuration/client.html#meta "Nomad meta Job Specification"
[task]: /docs/job-specification/task.html "Nomad task Job Specification"
[interpolation]: /docs/runtime/interpolation.html "Nomad interpolation"
[node-variables]: /docs/runtime/interpolation.html#node-variables- "Nomad interpolation-Node variables"