)]}'
{"deliverables/rocky/watcher.yaml":[{"author":{"_account_id":21561,"name":"Anne Bertucio","email":"annebertucio@gmail.com","username":"whyhiannabelle"},"change_message_id":"cc48167553dadc0cd3680be541864565ee72527b","unresolved":false,"context_lines":[{"line_number":33,"context_line":"  - |"},{"line_number":34,"context_line":"    Watcher services can be launched in HA mode. From now on Watcher Decision"},{"line_number":35,"context_line":"    Engine and Watcher Applier services may be deployed on different nodes to"},{"line_number":36,"context_line":"    run in active-active or active-passive mode. Any ONGOING Audits or Action"},{"line_number":37,"context_line":"    Plans will be CANCELLED if service they are executed on is restarted."},{"line_number":38,"context_line":"  - |"},{"line_number":39,"context_line":"    Added a host maintenance strategy to prepare compute node for maintenance"},{"line_number":40,"context_line":"    by cleaning up instances via migration."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3f79a3b5_63c4de91","line":37,"range":{"start_line":36,"start_character":49,"end_line":37,"end_character":73},"updated":"2018-08-13 15:14:06.000000000","message":"This detail can probably live in the release notes or other guides vs here. Aim here is to keep these fairly high level.","commit_id":"cdbadd631017b6b91eec4cc517f624ec4d58ea21"},{"author":{"_account_id":19055,"name":"Alexander Chadin","email":"joker946@gmail.com","username":"joker946"},"change_message_id":"bc6e24016c0dc58ec37cd4579a620a3111e2a37f","unresolved":false,"context_lines":[{"line_number":33,"context_line":"  - |"},{"line_number":34,"context_line":"    Watcher services can be launched in HA mode. From now on Watcher Decision"},{"line_number":35,"context_line":"    Engine and Watcher Applier services may be deployed on different nodes to"},{"line_number":36,"context_line":"    run in active-active or active-passive mode. Any ONGOING Audits or Action"},{"line_number":37,"context_line":"    Plans will be CANCELLED if service they are executed on is restarted."},{"line_number":38,"context_line":"  - |"},{"line_number":39,"context_line":"    Added a host maintenance strategy to prepare compute node for maintenance"},{"line_number":40,"context_line":"    by cleaning up instances via migration."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3f79a3b5_72281896","line":37,"range":{"start_line":36,"start_character":49,"end_line":37,"end_character":73},"in_reply_to":"3f79a3b5_63c4de91","updated":"2018-08-14 08:32:29.000000000","message":"Agreed, fixed.","commit_id":"cdbadd631017b6b91eec4cc517f624ec4d58ea21"},{"author":{"_account_id":21561,"name":"Anne Bertucio","email":"annebertucio@gmail.com","username":"whyhiannabelle"},"change_message_id":"cc48167553dadc0cd3680be541864565ee72527b","unresolved":false,"context_lines":[{"line_number":41,"context_line":"  - |"},{"line_number":42,"context_line":"    Excluding of instances from audit scope based on project_id is added."},{"line_number":43,"context_line":"  - |"},{"line_number":44,"context_line":"    Added an ability not to take into account some instances during strategy\u0027s"},{"line_number":45,"context_line":"    work but consider their workload."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3f79a3b5_63f7fed4","line":45,"range":{"start_line":44,"start_character":4,"end_line":45,"end_character":37},"updated":"2018-08-13 15:14:06.000000000","message":"Would reword to take out the double negative. Is, \"Added the ability to ignore specified instances during [strategy\u0027s*] work but still consider the workload\" accurate? \n\n*This word isn\u0027t quite making sense to me here. What was the general idea?","commit_id":"cdbadd631017b6b91eec4cc517f624ec4d58ea21"},{"author":{"_account_id":19055,"name":"Alexander Chadin","email":"joker946@gmail.com","username":"joker946"},"change_message_id":"bc6e24016c0dc58ec37cd4579a620a3111e2a37f","unresolved":false,"context_lines":[{"line_number":41,"context_line":"  - |"},{"line_number":42,"context_line":"    Excluding of instances from audit scope based on project_id is added."},{"line_number":43,"context_line":"  - |"},{"line_number":44,"context_line":"    Added an ability not to take into account some instances during strategy\u0027s"},{"line_number":45,"context_line":"    work but consider their workload."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3f79a3b5_f542d20e","line":45,"range":{"start_line":44,"start_character":4,"end_line":45,"end_character":37},"in_reply_to":"3f79a3b5_63f7fed4","updated":"2018-08-14 08:32:29.000000000","message":"Strategy is a special algorithm (should be considered as a part of Watcher\u0027s glossary[1]). I\u0027ve completed your proposal, does it look right?\n\nhttps://docs.openstack.org/watcher/latest/glossary.html#strategy","commit_id":"cdbadd631017b6b91eec4cc517f624ec4d58ea21"},{"author":{"_account_id":21561,"name":"Anne Bertucio","email":"annebertucio@gmail.com","username":"whyhiannabelle"},"change_message_id":"7162ac63e19df747a078fdfc0ea790322d4c64e3","unresolved":false,"context_lines":[{"line_number":41,"context_line":"  - |"},{"line_number":42,"context_line":"    Excluding of instances from audit scope based on project_id is added."},{"line_number":43,"context_line":"  - |"},{"line_number":44,"context_line":"    Added an ability not to take into account some instances during strategy\u0027s"},{"line_number":45,"context_line":"    work but consider their workload."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3f79a3b5_44eaecd7","line":45,"range":{"start_line":44,"start_character":4,"end_line":45,"end_character":37},"in_reply_to":"3f79a3b5_f542d20e","updated":"2018-08-14 20:03:12.000000000","message":"Does it make sense to write it as \"strategy (an implementation in Watcher)\"?","commit_id":"cdbadd631017b6b91eec4cc517f624ec4d58ea21"}]}