Period is currently constrained to be non-zero and a
multiple of 60. Validate those limits.
Periods must be >= 1.
Had to change the except clause to print out the
msg from the parser. This gives good messages for
these two cases but so-so for other cases
Add tests to ensure validation works as expected
Change-Id: If473359901621dae7f3e4d3be903f5d5d7e2885a
Added documentation for last function
Added python parsing for last function
Added tempest tests for last_value function
Change-Id: I4c35321e23e13596a2ef02e7e57306d5685c81ec
Depends-On: Ib5123ed035018757a50d9ebeb7335fbca48054f2
Implements: Blueprint last-value
The deterministic alarm's main trait
is preventing from transition to UNDETERMINTED state.
That allows effectively create alarms for metrics
which behaviour is similar to events (i.e. generated
upon critical situation in the system). By default (non-deterministic)
alarms created for those metrics would stay in UNDETERMINED stay
for most of the time.
Implements: blueprint alarmsonlogs
Change-Id: I506fcd0b9861e902a2bfcfa768d402c568b85cea
Upgraded to Falcon 0.2
Converted from stevedore to simport
Converted from monasca to monasca_api
Removed events. Events api is in monasca-events-api
Removed references to elastic search
Removed support for message format translations
Removed unused and dead code
Removed author tags
Change-Id: I5034ea256372d22b9f824e301c379da81f82b4e2
