Threshold can be set to any value. (e.g: 11999999999999999999999999999999999999). No limit or restriction

[Manik Bindlish]

Release: Stable Newton
Ubuntu 16.04
Environment for NFV

Threshold can be set of any of value. (e.g: 11999999999999999999999999999999999999). There is no limit or restriction.

root@node-1:~# aodh alarm create --name mack --type threshold --meter-name cpu_util --alarm-action http://controller:9890/v1.0/vnfs/92de8dfc-740d-4968-9ebf-9fb073cf41ab/vdu1_cpu_usage_monitoring_policy/SP1/us9fwbn5 --state alarm --threshold 1999999999999999999999999999999999999
+---------------------------+--------------------------------------------------------------------------------------------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------------------------------------------------------------------------------------------+
| alarm_actions | [u'http://controller:9890/v1.0/vnfs/92de8dfc-740d-4968-9ebf-9fb073cf41ab/vdu1_cpu_usage_monitoring_policy/SP1/us9fwbn5'] |
| alarm_id | ff352d48-6089-4135-92a5-3fbe66335bd9 |
| comparison_operator | eq |
| description | Alarm when cpu_util is eq a avg of 2e+36 over 60 seconds |
| enabled | True |
| evaluation_periods | 1 |
| exclude_outliers | False |
| insufficient_data_actions | [] |
| meter_name | cpu_util |
| name | mack |
| ok_actions | [] |
| period | 60 |
| project_id | 9a036d420925419c9066e02ae98c4f99 |
| query | |
| repeat_actions | False |
| severity | low |
| state | alarm |
| state_timestamp | 2017-12-26T00:24:45.096501 |
| statistic | avg |
| threshold | 2e+36 |
| time_constraints | [] |
| timestamp | 2017-12-26T00:24:45.096501 |
| type | threshold |
| user_id | 4f40ae325991476f8733358eb736ad1e |
+---------------------------+--------------------------------------------------------------------------------------------------------------------------+

[gordon chung (chungg)]

how would you enforce a restriction? a threshold can be any value depending on context.