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

Merge pull request #5473 from hashicorp/f-spread-docs-fix

Browse source 
minor fixes to spread stanza documentation
This commit is contained in:
Preetha 2019-03-26 17:13:43 -05:00 committed by GitHub
parent b2b7618a1c bd2e6b5bf9
commit f9bd698801
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
website/source/docs/job-specification/spread.html.md
View file

@ -41,11 +41,11 @@ job "docs" {
group "example" {
# Spread allocations over each rack based on desired percentage
spread {
attribute = "${node.datacenter}"
target "us-east1" {
attribute = "${meta.rack}"
target "r1" {
percent = 60
}
target "us-west1" {
target "r2" {
percent = 40
}
}
@ -105,9 +105,9 @@ spread {
### Spread With Target Percentages
This example shows a spread stanza that specifies one target percentage. If we
have three datacenters `us-east1`, `us-east2` and `us-west1`, and a task group
of `count = 10` Nomad will attempt to place place 5 of the allocations in "us-east1",
and then spread the rest among the other two datacenters.
have three datacenters `us-east1`, `us-east2`, and `us-west1`, and a task group
of `count = 10`, Nomad will attempt to place place 5 of the allocations in "us-east1",
and will spread the remaining among the other two datacenters.
```hcl
spread {
@ -144,7 +144,7 @@ spread {
This example shows spread stanzas with multiple attributes. Consider a Nomad cluster
where there are two datacenters `us-east1` and `us-west1`, and each datacenter has nodes
with `${meta.rack}` being `r1` or `r2`. For the following spread stanza used on a job with `count=12`, Nomad
with `${meta.rack}` being `r1` or `r2`. With the following spread stanza used on a job with `count=12`, Nomad
will attempt to place 6 allocations in each datacenter. Within a datacenter, Nomad will
attempt to place 3 allocations in nodes on rack `r1`, and 3 allocations in nodes on rack `r2`.