)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":3012,"name":"Dina Belova","email":"dbelova@mirantis.com","username":"dbelova"},"change_message_id":"dcc383c0493f5c8a9515a8669775dd43c54f9047","unresolved":false,"context_lines":[{"line_number":9,"context_line":"This test checks alarm functionality."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"The following is the scenario outline:"},{"line_number":12,"context_line":" 1. Create alarm which triggered to alarm and send"},{"line_number":13,"context_line":"    callback by alarm_actions if in last period"},{"line_number":14,"context_line":"    more then one server had been created."},{"line_number":15,"context_line":" 2. Create one server."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"1ae5cdf2_ecd4f3ea","line":12,"updated":"2014-06-25 11:37:43.000000000","message":"please use\nto alarm -\u003e to \u0027alarm\u0027 state\n\nto make this more readable","commit_id":"bb59976845e984f3b72c60e6428593fd6fa89496"}],"tempest/scenario/test_threshold_alarm.py":[{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"4b4fe31e1b8251b176f0a984ee9869eb408e8c41","unresolved":false,"context_lines":[{"line_number":39,"context_line":"    6. Check that alarms callback received."},{"line_number":40,"context_line":"    \"\"\""},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"    THRESHOLD_PERIOD \u003d 30"},{"line_number":43,"context_line":"    PORT \u003d 61482"},{"line_number":44,"context_line":"    alarm_callback_received \u003d False"},{"line_number":45,"context_line":""}],"source_content_type":"text/x-python","patch_set":2,"id":"1ae5cdf2_59ac07ef","line":42,"updated":"2014-06-23 23:17:32.000000000","message":"This seems to be a unusual alarm definition in that the tight period (30s) is dependent on notification-driven samples for the instance meter, so is likely to be in the insufficient_data state for much of the alarm\u0027s lifetime.\n\nIf the purpose is to test threshold-oriented alarming in general, would it be better to base this on a metric such as cpu_util that\u0027s collected at a predictable cadence?","commit_id":"bb59976845e984f3b72c60e6428593fd6fa89496"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"9107bcd8531fc0e491ac9d796c902ec533a2ef68","unresolved":false,"context_lines":[{"line_number":39,"context_line":"    6. Check that alarms callback received."},{"line_number":40,"context_line":"    \"\"\""},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"    THRESHOLD_PERIOD \u003d 30"},{"line_number":43,"context_line":"    PORT \u003d 61482"},{"line_number":44,"context_line":"    alarm_callback_received \u003d False"},{"line_number":45,"context_line":""}],"source_content_type":"text/x-python","patch_set":2,"id":"1ae5cdf2_da99d67a","line":42,"in_reply_to":"1ae5cdf2_59ac07ef","updated":"2014-06-24 10:56:39.000000000","message":"Discussed with the author on IRC.\n\nThe intent here is simply to avoid depending on the existence of a metric with an associated polling lag.","commit_id":"bb59976845e984f3b72c60e6428593fd6fa89496"}]}