Replace deprecated max_failure_precent sla

The new sla is a failure_rate with min/max sub-keys. Update the
documentation and examples to reflect this.

Change-Id: Id947e4684aa84fe7d6c239a28b92e2a893ddaf66
This commit is contained in:
Jesse Keating 2015-01-21 12:25:54 -08:00
parent d431a0b749
commit cf2f121515
5 changed files with 12 additions and 6 deletions

View File

@ -41,7 +41,9 @@ To configure the SLA, add the *"sla"* section to the configuration of the corres
},
"sla": {
"max_seconds_per_iteration": 10,
"max_failure_percent": 25
"failure_rate": {
"max": 25
}
}
}
]

View File

@ -162,7 +162,8 @@ class InfoCommands(object):
"assosiated value, e.g.:\n\n"
" sla:\n"
" max_seconds_per_iteration: 4\n"
" max_failure_percent: 1"
" failure_rate:\n"
" max: 1"
"\n\n" +
self._compose_table("List of SLA checks", sla) +
"To get information about specific SLA checks, run:\n"

View File

@ -9,10 +9,10 @@ with contracted values such as maximum error rate or minimum response time.
Currently supported criteria:
max_failure_percent
failure_rate
-------------------
Maximum allowed failure rate in percent.
A maximum and/or a minimum failure rate expressed as max or min sub-keys.
max_seconds_per_iteration

View File

@ -11,7 +11,9 @@
},
"sla": {
"max_seconds_per_iteration": 4,
"max_failure_percent": 1
"failure_rate": {
"max": 1
}
}
}
]

View File

@ -9,4 +9,5 @@
concurrency: 10
sla:
max_seconds_per_iteration: 4
max_failure_percent: 1
failure_rate:
max: 1