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

Merge pull request #4501 from msvbhat/nomad-contraints-docs

Browse source 
Fix client metadata link in Nomad constraints docs
This commit is contained in:
Michael Schurter 2018-07-16 09:54:02 -07:00 committed by GitHub
parent 9413c719a6 b7dd9f8c29
commit 4fc04794a7
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
website/source/docs/job-specification/constraint.html.md
View file

@ -219,7 +219,7 @@ constraint {
A potential use case of the `distinct_property` constraint is to spread a A potential use case of the `distinct_property` constraint is to spread a
service with `count > 1` across racks to minimize correlated failure. Nodes can service with `count > 1` across racks to minimize correlated failure. Nodes can
be annotated with which rack they are on using [client be annotated with which rack they are on using [client
metadata][client-metadata] with values such as "rack-12-1", "rack-12-2", etc. metadata][client-meta] with values such as "rack-12-1", "rack-12-2", etc.
The following constraint would assure that an individual rack is not running The following constraint would assure that an individual rack is not running
more than 2 instances of the task group. more than 2 instances of the task group.