)]}'
{"cinder/api/contrib/admin_actions.py":[{"author":{"_account_id":26250,"name":"Johannes Kulik","email":"johannes.kulik@sap.com","username":"jkulik"},"change_message_id":"2bbce68807422a55ce77f18ddfa1949a4bf53068","unresolved":false,"context_lines":[{"line_number":101,"context_line":"        LOG.debug(msg, {\u0027resource\u0027: self.resource_name, \u0027id\u0027: id,"},{"line_number":102,"context_line":"                        \u0027update\u0027: update})"},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"        # calling notifier here for volumeStatusUpdate here is"},{"line_number":105,"context_line":"        # deprecated.  Will be replaced with _notify_reset_status()"},{"line_number":106,"context_line":"        notifier_info \u003d dict(id\u003did, update\u003dupdate)"},{"line_number":107,"context_line":"        notifier \u003d rpc.get_notifier(\u0027volumeStatusUpdate\u0027)"}],"source_content_type":"text/x-python","patch_set":4,"id":"1fa4df85_00431cb1","line":104,"updated":"2020-03-16 12:58:47.000000000","message":"double \"here\"","commit_id":"7209f8afe06356d43b18d81d24bc6b3e5fa48e81"},{"author":{"_account_id":5997,"name":"Walt","display_name":"Hemna","email":"waboring@hemna.com","username":"walter-boring","status":"SAP"},"change_message_id":"eac086441cd964500bf25509042dab653fab2ee0","unresolved":false,"context_lines":[{"line_number":101,"context_line":"        LOG.debug(msg, {\u0027resource\u0027: self.resource_name, \u0027id\u0027: id,"},{"line_number":102,"context_line":"                        \u0027update\u0027: update})"},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"        # calling notifier here for volumeStatusUpdate here is"},{"line_number":105,"context_line":"        # deprecated.  Will be replaced with _notify_reset_status()"},{"line_number":106,"context_line":"        notifier_info \u003d dict(id\u003did, update\u003dupdate)"},{"line_number":107,"context_line":"        notifier \u003d rpc.get_notifier(\u0027volumeStatusUpdate\u0027)"}],"source_content_type":"text/x-python","patch_set":4,"id":"1fa4df85_50ebf4da","line":104,"in_reply_to":"1fa4df85_00431cb1","updated":"2020-03-18 18:19:04.000000000","message":"Done","commit_id":"7209f8afe06356d43b18d81d24bc6b3e5fa48e81"}],"releasenotes/notes/reset-status-notification-update-4a80a8b5feb821ef.yaml":[{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"a35cd309b862fbd3d9363aaa032042384d52d261","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"issues:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The issue is for a lesser used portion of Cinder.  The problem is that"},{"line_number":5,"context_line":"    reset_status notifications for volumes, snapshots and backups are not"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"1fa4df85_81404837","line":2,"range":{"start_line":2,"start_character":0,"end_line":2,"end_character":6},"updated":"2020-03-18 13:47:24.000000000","message":"I think this should be removed. We don\u0027t need to call out an issue in the release notes if that issue has been fixed.","commit_id":"7209f8afe06356d43b18d81d24bc6b3e5fa48e81"},{"author":{"_account_id":5997,"name":"Walt","display_name":"Hemna","email":"waboring@hemna.com","username":"walter-boring","status":"SAP"},"change_message_id":"eac086441cd964500bf25509042dab653fab2ee0","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"issues:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The issue is for a lesser used portion of Cinder.  The problem is that"},{"line_number":5,"context_line":"    reset_status notifications for volumes, snapshots and backups are not"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"1fa4df85_301bd81b","line":2,"range":{"start_line":2,"start_character":0,"end_line":2,"end_character":6},"in_reply_to":"1fa4df85_81404837","updated":"2020-03-18 18:19:04.000000000","message":"Done","commit_id":"7209f8afe06356d43b18d81d24bc6b3e5fa48e81"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"a35cd309b862fbd3d9363aaa032042384d52d261","unresolved":false,"context_lines":[{"line_number":8,"context_line":"    as volumes."},{"line_number":9,"context_line":"deprecations:"},{"line_number":10,"context_line":"  - |"},{"line_number":11,"context_line":"    This deprecates the sending of os-reset_status notifications to the"},{"line_number":12,"context_line":"    volumeStatusUpdate, backupStatusUpdate publisher_id.   Those queues"},{"line_number":13,"context_line":"    are not consistent with all other notifications for volumes and backups."},{"line_number":14,"context_line":"    The reset_status updates for snapshots were going to volumeStatusUpdate"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"1fa4df85_61450c43","line":11,"range":{"start_line":11,"start_character":35,"end_line":11,"end_character":50},"updated":"2020-03-18 13:47:24.000000000","message":"Since update is needed, would be good to format these with `` so it\u0027s more visible in the generated output that these are config option names.","commit_id":"7209f8afe06356d43b18d81d24bc6b3e5fa48e81"},{"author":{"_account_id":5997,"name":"Walt","display_name":"Hemna","email":"waboring@hemna.com","username":"walter-boring","status":"SAP"},"change_message_id":"eac086441cd964500bf25509042dab653fab2ee0","unresolved":false,"context_lines":[{"line_number":8,"context_line":"    as volumes."},{"line_number":9,"context_line":"deprecations:"},{"line_number":10,"context_line":"  - |"},{"line_number":11,"context_line":"    This deprecates the sending of os-reset_status notifications to the"},{"line_number":12,"context_line":"    volumeStatusUpdate, backupStatusUpdate publisher_id.   Those queues"},{"line_number":13,"context_line":"    are not consistent with all other notifications for volumes and backups."},{"line_number":14,"context_line":"    The reset_status updates for snapshots were going to volumeStatusUpdate"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"1fa4df85_501694f3","line":11,"range":{"start_line":11,"start_character":35,"end_line":11,"end_character":50},"in_reply_to":"1fa4df85_61450c43","updated":"2020-03-18 18:19:04.000000000","message":"Done","commit_id":"7209f8afe06356d43b18d81d24bc6b3e5fa48e81"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"a2c5e1817a9ac256cb72cf392648bead402c3567","unresolved":false,"context_lines":[{"line_number":9,"context_line":"deprecations:"},{"line_number":10,"context_line":"  - |"},{"line_number":11,"context_line":"    This deprecates the sending of os-reset_status notifications to the"},{"line_number":12,"context_line":"    volumeStatusUpdate, backupStatusUpdate publisher_id.   Those queues"},{"line_number":13,"context_line":"    are not consistent with all other notifications for volumes and backups."},{"line_number":14,"context_line":"    The reset_status updates for snapshots were going to volumeStatusUpdate"},{"line_number":15,"context_line":"    as well."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"1fa4df85_e13d7cdd","line":12,"range":{"start_line":12,"start_character":4,"end_line":12,"end_character":42},"updated":"2020-03-18 14:31:17.000000000","message":"volumeStatusUpdate and backupStatusUpdate","commit_id":"7209f8afe06356d43b18d81d24bc6b3e5fa48e81"},{"author":{"_account_id":5997,"name":"Walt","display_name":"Hemna","email":"waboring@hemna.com","username":"walter-boring","status":"SAP"},"change_message_id":"eac086441cd964500bf25509042dab653fab2ee0","unresolved":false,"context_lines":[{"line_number":9,"context_line":"deprecations:"},{"line_number":10,"context_line":"  - |"},{"line_number":11,"context_line":"    This deprecates the sending of os-reset_status notifications to the"},{"line_number":12,"context_line":"    volumeStatusUpdate, backupStatusUpdate publisher_id.   Those queues"},{"line_number":13,"context_line":"    are not consistent with all other notifications for volumes and backups."},{"line_number":14,"context_line":"    The reset_status updates for snapshots were going to volumeStatusUpdate"},{"line_number":15,"context_line":"    as well."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"1fa4df85_f0d22034","line":12,"range":{"start_line":12,"start_character":4,"end_line":12,"end_character":42},"in_reply_to":"1fa4df85_e13d7cdd","updated":"2020-03-18 18:19:04.000000000","message":"Done","commit_id":"7209f8afe06356d43b18d81d24bc6b3e5fa48e81"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"a2c5e1817a9ac256cb72cf392648bead402c3567","unresolved":false,"context_lines":[{"line_number":16,"context_line":"fixes:"},{"line_number":17,"context_line":"  - |"},{"line_number":18,"context_line":"    os-reset_status notifications for volumes, snapshots and backups will now"},{"line_number":19,"context_line":"    go to the standard publisher id for volume, snapshot and backup as all"},{"line_number":20,"context_line":"    other notifications for volume, snapshot and backup."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"1fa4df85_44357ed9","line":19,"range":{"start_line":19,"start_character":68,"end_line":19,"end_character":74},"updated":"2020-03-18 14:31:17.000000000","message":"like all","commit_id":"7209f8afe06356d43b18d81d24bc6b3e5fa48e81"},{"author":{"_account_id":5997,"name":"Walt","display_name":"Hemna","email":"waboring@hemna.com","username":"walter-boring","status":"SAP"},"change_message_id":"eac086441cd964500bf25509042dab653fab2ee0","unresolved":false,"context_lines":[{"line_number":16,"context_line":"fixes:"},{"line_number":17,"context_line":"  - |"},{"line_number":18,"context_line":"    os-reset_status notifications for volumes, snapshots and backups will now"},{"line_number":19,"context_line":"    go to the standard publisher id for volume, snapshot and backup as all"},{"line_number":20,"context_line":"    other notifications for volume, snapshot and backup."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"1fa4df85_10d6dc28","line":19,"range":{"start_line":19,"start_character":68,"end_line":19,"end_character":74},"in_reply_to":"1fa4df85_44357ed9","updated":"2020-03-18 18:19:04.000000000","message":"Done","commit_id":"7209f8afe06356d43b18d81d24bc6b3e5fa48e81"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"19cca2e3eeb980a0ddd85b8284ccd5a7738bbe7f","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"deprecations:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    This deprecates the sending of ``os-reset_status`` notifications to the"},{"line_number":5,"context_line":"    ``volumeStatusUpdate``, ``backupStatusUpdate`` publisher_id.   Those queues"},{"line_number":6,"context_line":"    are not consistent with all other notifications for volumes and backups."},{"line_number":7,"context_line":"    The reset_status updates for snapshots were going to"},{"line_number":8,"context_line":"    ``volumeStatusUpdate`` as well."},{"line_number":9,"context_line":"fixes:"},{"line_number":10,"context_line":"  - |"},{"line_number":11,"context_line":"    ``os-reset_status`` notifications for volumes, snapshots and backups will"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"1fa4df85_c215cc4a","line":8,"range":{"start_line":4,"start_character":0,"end_line":8,"end_character":35},"updated":"2020-03-19 14:08:01.000000000","message":"I\u0027d like to make this a bit more detailed, something like:\n\n  In this release, sending ``os-reset_status`` notifications to the following *nonstandard* publisher_ids is DEPRECATED:\n\n  * \u0027volumeStatusUpdate\u0027 for volume status resets\n  * \u0027volumeStatusUpdate\u0027 for snapshot status resets\n  * \u0027backupStatusUpdate\u0027 for backup status resets\n\n  The notifications continue to be published to the above during the deprecation period.  Beginning with this release, the ``os-reset_status`` notifications are also sent to the following *standard* publisher_ids:\n\n  * \u0027volume\u0027 for volume status resets   \n  * \u0027snapshot\u0027 for snapshot status resets \n  * \u0027backup\u0027 for backup status resets\n\n  This will allow consumers of these notifications to make a smooth transition.  In the Victoria release, ``os-reset_status`` notifications will *only* be sent to the standard publisher_ids.\n\n(This interface isn\u0027t cooperating.  Even though you can\u0027t see them, don\u0027t forget to make sure there\u0027s a blank line before the bulleted lists, otherwise they won\u0027t render correctly.)","commit_id":"e7490637bc7216ef876cc4d62a60646570ffbe81"},{"author":{"_account_id":5997,"name":"Walt","display_name":"Hemna","email":"waboring@hemna.com","username":"walter-boring","status":"SAP"},"change_message_id":"bbd9a09169d6b81a922e782b100f9142967e0dba","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"deprecations:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    This deprecates the sending of ``os-reset_status`` notifications to the"},{"line_number":5,"context_line":"    ``volumeStatusUpdate``, ``backupStatusUpdate`` publisher_id.   Those queues"},{"line_number":6,"context_line":"    are not consistent with all other notifications for volumes and backups."},{"line_number":7,"context_line":"    The reset_status updates for snapshots were going to"},{"line_number":8,"context_line":"    ``volumeStatusUpdate`` as well."},{"line_number":9,"context_line":"fixes:"},{"line_number":10,"context_line":"  - |"},{"line_number":11,"context_line":"    ``os-reset_status`` notifications for volumes, snapshots and backups will"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"df33271e_e8c6a349","line":8,"range":{"start_line":4,"start_character":0,"end_line":8,"end_character":35},"in_reply_to":"1fa4df85_c215cc4a","updated":"2020-03-25 15:35:47.000000000","message":"I think I got this in correctly.   It\u0027s hard to get the formatting right.   Anyway, I have a new rev up.","commit_id":"e7490637bc7216ef876cc4d62a60646570ffbe81"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"ec0161d746f036a4d3e1dbabd9add9e5ba9d3d89","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"deprecations:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    This deprecates the sending of ``os-reset_status`` notifications to the"},{"line_number":5,"context_line":"    ``volumeStatusUpdate``, ``backupStatusUpdate`` publisher_id.   Those queues"},{"line_number":6,"context_line":"    are not consistent with all other notifications for volumes and backups."},{"line_number":7,"context_line":"    The reset_status updates for snapshots were going to"},{"line_number":8,"context_line":"    ``volumeStatusUpdate`` as well."},{"line_number":9,"context_line":"fixes:"},{"line_number":10,"context_line":"  - |"},{"line_number":11,"context_line":"    ``os-reset_status`` notifications for volumes, snapshots and backups will"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"df33271e_421debbb","line":8,"range":{"start_line":4,"start_character":0,"end_line":8,"end_character":35},"in_reply_to":"df33271e_e8c6a349","updated":"2020-03-25 18:05:32.000000000","message":"Generated HTML looks good!","commit_id":"e7490637bc7216ef876cc4d62a60646570ffbe81"}]}