)]}'
{"specs/pike/better-user-messages.rst":[{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"c72dd0df2c3585468b2ad2862ec43ebc35de268e","unresolved":false,"context_lines":[{"line_number":15,"context_line":"Problem description"},{"line_number":16,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"We have introduced user messages since Ocata, That\u0027s a beneficial feature,"},{"line_number":19,"context_line":"because it solve the problem that we doesn\u0027t provide enough message when an"},{"line_number":20,"context_line":"async task is failed (especially for volume and snapshot resources)."},{"line_number":21,"context_line":"It\u0027s easy to find out when and where the task failed with our new"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ffe62b97_937c63ec","line":18,"range":{"start_line":18,"start_character":46,"end_line":18,"end_character":47},"updated":"2017-03-30 13:46:49.000000000","message":"Lower case t.","commit_id":"d0661a148cc7476da11cbb5dd631dbe1712caab9"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"c72dd0df2c3585468b2ad2862ec43ebc35de268e","unresolved":false,"context_lines":[{"line_number":16,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"We have introduced user messages since Ocata, That\u0027s a beneficial feature,"},{"line_number":19,"context_line":"because it solve the problem that we doesn\u0027t provide enough message when an"},{"line_number":20,"context_line":"async task is failed (especially for volume and snapshot resources)."},{"line_number":21,"context_line":"It\u0027s easy to find out when and where the task failed with our new"},{"line_number":22,"context_line":"messages APIs."}],"source_content_type":"text/x-rst","patch_set":2,"id":"ffe62b97_d371cb0e","line":19,"range":{"start_line":19,"start_character":37,"end_line":19,"end_character":44},"updated":"2017-03-30 13:46:49.000000000","message":"/doesn\u0027t/don\u0027t/","commit_id":"d0661a148cc7476da11cbb5dd631dbe1712caab9"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"c72dd0df2c3585468b2ad2862ec43ebc35de268e","unresolved":false,"context_lines":[{"line_number":16,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"We have introduced user messages since Ocata, That\u0027s a beneficial feature,"},{"line_number":19,"context_line":"because it solve the problem that we doesn\u0027t provide enough message when an"},{"line_number":20,"context_line":"async task is failed (especially for volume and snapshot resources)."},{"line_number":21,"context_line":"It\u0027s easy to find out when and where the task failed with our new"},{"line_number":22,"context_line":"messages APIs."}],"source_content_type":"text/x-rst","patch_set":2,"id":"ffe62b97_1368531f","line":19,"range":{"start_line":19,"start_character":11,"end_line":19,"end_character":16},"updated":"2017-03-30 13:46:49.000000000","message":"/solve/solves/","commit_id":"d0661a148cc7476da11cbb5dd631dbe1712caab9"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"c72dd0df2c3585468b2ad2862ec43ebc35de268e","unresolved":false,"context_lines":[{"line_number":21,"context_line":"It\u0027s easy to find out when and where the task failed with our new"},{"line_number":22,"context_line":"messages APIs."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"But, the better user experience is all depended on whether we have hard coded"},{"line_number":25,"context_line":"enough user messages in our projects. So that raises a new question, how could"},{"line_number":26,"context_line":"we add this messages without changing our code frequently and how could we"},{"line_number":27,"context_line":"maintain this \u0027better user experience but not functionality involved\u0027 code"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ffe62b97_93ca2318","line":24,"range":{"start_line":24,"start_character":32,"end_line":24,"end_character":47},"updated":"2017-03-30 13:46:49.000000000","message":"\"is all dependent\" or \"all depends\"","commit_id":"d0661a148cc7476da11cbb5dd631dbe1712caab9"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"c72dd0df2c3585468b2ad2862ec43ebc35de268e","unresolved":false,"context_lines":[{"line_number":23,"context_line":""},{"line_number":24,"context_line":"But, the better user experience is all depended on whether we have hard coded"},{"line_number":25,"context_line":"enough user messages in our projects. So that raises a new question, how could"},{"line_number":26,"context_line":"we add this messages without changing our code frequently and how could we"},{"line_number":27,"context_line":"maintain this \u0027better user experience but not functionality involved\u0027 code"},{"line_number":28,"context_line":"cleanly."},{"line_number":29,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"ffe62b97_73e8bf7b","line":26,"range":{"start_line":26,"start_character":7,"end_line":26,"end_character":11},"updated":"2017-03-30 13:46:49.000000000","message":"these","commit_id":"d0661a148cc7476da11cbb5dd631dbe1712caab9"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"c72dd0df2c3585468b2ad2862ec43ebc35de268e","unresolved":false,"context_lines":[{"line_number":76,"context_line":""},{"line_number":77,"context_line":"The proposed changes are:"},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"* Introduce ``message`` (or name it ``detail`` to avoid confusion) to user"},{"line_number":80,"context_line":"  messages, the \u0027message\u0027 only represent what (no matter error or warning)"},{"line_number":81,"context_line":"  happened at that explicit time, that means ``QUOTA_EXCEED`` is a valid one"},{"line_number":82,"context_line":"  while ``UPLOAD_TO_IMAGE_OVER_QUOTA`` isn\u0027t."}],"source_content_type":"text/x-rst","patch_set":2,"id":"ffe62b97_3387d7b9","line":79,"range":{"start_line":79,"start_character":50,"end_line":79,"end_character":66},"updated":"2017-03-30 13:46:49.000000000","message":"+1","commit_id":"d0661a148cc7476da11cbb5dd631dbe1712caab9"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"c72dd0df2c3585468b2ad2862ec43ebc35de268e","unresolved":false,"context_lines":[{"line_number":118,"context_line":"    IMAGE_FROM_VOLUME_OVER_QUOTA \u003d \u0027VOLUME_000004\u0027"},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"    # This is how we would build the event_id at response after this change."},{"line_number":121,"context_line":"    VOLUME_0001_0002 : ({RESOURCE}_{ACTION_ID}_{MESSAGE_ID})"},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"  We could have these benefits:"},{"line_number":124,"context_line":"  1. We don\u0027t need to define that much events. (we only need to"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ffe62b97_b32f67a6","line":121,"range":{"start_line":121,"start_character":24,"end_line":121,"end_character":34},"updated":"2017-03-30 13:46:49.000000000","message":"There\u0027s one subtle difference here. The \"VOLUME_\" prefix was not intended to be an indication of the resource that the message pertains to, but rather a way to differentiate COMPUTE_ (nova), SHARE_ (manila), and other messages. So categorizing by  project/service rather than specific resource type to make sure these are globally unique across all of OpenStack.","commit_id":"d0661a148cc7476da11cbb5dd631dbe1712caab9"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"08783036b4c2f61ab2611b1feef19155304acabe","unresolved":false,"context_lines":[{"line_number":97,"context_line":""},{"line_number":98,"context_line":"     message_map \u003d {"},{"line_number":99,"context_line":"     MessageIds.DEVICE_IS_BUSY: _(\"Backend device is busy at present.\"),"},{"line_number":100,"context_line":"     MessageIds.INVALID_CONFIGURATION: _(\"An unknown error occurred.\"),"},{"line_number":101,"context_line":"     }"},{"line_number":102,"context_line":"     ..."},{"line_number":103,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"ffe62b97_560c8641","line":100,"range":{"start_line":100,"start_character":41,"end_line":100,"end_character":69},"updated":"2017-03-30 15:05:14.000000000","message":"This doesn\u0027t seem like a good example for INVALID_CONFIGURATION .","commit_id":"288204c20cd5bdc98aa58a8a5af44de63bf1eeaf"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"08783036b4c2f61ab2611b1feef19155304acabe","unresolved":false,"context_lines":[{"line_number":118,"context_line":"    IMAGE_FROM_VOLUME_OVER_QUOTA \u003d \u0027VOLUME_000004\u0027"},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"    # This is how we would build the event_id at response after this change."},{"line_number":121,"context_line":"    VOLUME_0001_0002 : ({RESOURCE}_{ACTION_ID}_{MESSAGE_ID})"},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"  We could have these benefits:"},{"line_number":124,"context_line":"  1. We don\u0027t need to define that much events. (we only need to"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ffe62b97_b93185a5","line":121,"updated":"2017-03-30 15:05:14.000000000","message":"Still haven\u0027t really addressed Sean\u0027s concern here.  We will need to figure out how to do that.  Should it become \n{PROJECT}_{RESOURCE}_{ACTION_ID}_{MESSAGE_ID}  That is getting awful long but it maybe that is the way we need to go.","commit_id":"288204c20cd5bdc98aa58a8a5af44de63bf1eeaf"}],"specs/pike/explicit-user-messages.rst":[{"author":{"_account_id":7582,"name":"Jan Provaznik","email":"jan.provaznik@gmail.com","username":"jprovazn"},"change_message_id":"2193d0e247dfe4554ff040d9ab9f3be33fe58c66","unresolved":false,"context_lines":[{"line_number":68,"context_line":"Use Cases"},{"line_number":69,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"The main use-case here is for an explicit user message to administrators and"},{"line_number":72,"context_line":"a better maintaining experience for cinder developers."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"Proposed change"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dfeb2761_4e47441f","line":71,"updated":"2017-03-31 09:53:55.000000000","message":"My thinking about user messages (either in cinder or manila) is that it\u0027s primarily focused on providing better messages (information about what happened) to *ordinary users*, not parimarily administrators who can get get all details e.g. from logs (with all extra details).","commit_id":"d6c2fd47e47c9a2da9dbe0c0b5b1d01b289c8b96"},{"author":{"_account_id":23083,"name":"TommyLike","email":"tommylikehu@gmail.com","username":"TommyLike"},"change_message_id":"2c6f4818542722a3453e93aede6c5398b235a3a3","unresolved":false,"context_lines":[{"line_number":68,"context_line":"Use Cases"},{"line_number":69,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"The main use-case here is for an explicit user message to administrators and"},{"line_number":72,"context_line":"a better maintaining experience for cinder developers."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"Proposed change"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dfeb2761_76201aad","line":71,"in_reply_to":"dfeb2761_4e47441f","updated":"2017-04-05 08:07:02.000000000","message":"Done","commit_id":"d6c2fd47e47c9a2da9dbe0c0b5b1d01b289c8b96"},{"author":{"_account_id":7582,"name":"Jan Provaznik","email":"jan.provaznik@gmail.com","username":"jprovazn"},"change_message_id":"2193d0e247dfe4554ff040d9ab9f3be33fe58c66","unresolved":false,"context_lines":[{"line_number":87,"context_line":"  sensitive information. We couldn\u0027t hard code the cleaned messages into"},{"line_number":88,"context_line":"  exceptions either, because it could add more dependency and hard to remove"},{"line_number":89,"context_line":"  (presume we have a cross-project user message project in the future), so"},{"line_number":90,"context_line":"  this is proposed how to do, build a dictionary from exception name to"},{"line_number":91,"context_line":"  ``messages`` (introduced above)::"},{"line_number":92,"context_line":""},{"line_number":93,"context_line":"     # multi_key dictionary"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dfeb2761_2edac016","line":90,"updated":"2017-03-31 09:53:55.000000000","message":"I actually liked your original proposal to define user messages in exceptions (https://review.openstack.org/#/c/448384/7/cinder/exception.py), I\u0027m not sure what you mean by \"more dependency and hard to remove\"?","commit_id":"d6c2fd47e47c9a2da9dbe0c0b5b1d01b289c8b96"},{"author":{"_account_id":23083,"name":"TommyLike","email":"tommylikehu@gmail.com","username":"TommyLike"},"change_message_id":"2c6f4818542722a3453e93aede6c5398b235a3a3","unresolved":false,"context_lines":[{"line_number":87,"context_line":"  sensitive information. We couldn\u0027t hard code the cleaned messages into"},{"line_number":88,"context_line":"  exceptions either, because it could add more dependency and hard to remove"},{"line_number":89,"context_line":"  (presume we have a cross-project user message project in the future), so"},{"line_number":90,"context_line":"  this is proposed how to do, build a dictionary from exception name to"},{"line_number":91,"context_line":"  ``messages`` (introduced above)::"},{"line_number":92,"context_line":""},{"line_number":93,"context_line":"     # multi_key dictionary"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dfeb2761_4180ae46","line":90,"in_reply_to":"dfeb2761_2edac016","updated":"2017-04-05 08:07:02.000000000","message":"Thanks, I will reword this.","commit_id":"d6c2fd47e47c9a2da9dbe0c0b5b1d01b289c8b96"},{"author":{"_account_id":7582,"name":"Jan Provaznik","email":"jan.provaznik@gmail.com","username":"jprovazn"},"change_message_id":"2193d0e247dfe4554ff040d9ab9f3be33fe58c66","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  have \u0027event_id\u0027 no matter how we change the underground behaviour. Instead"},{"line_number":113,"context_line":"  of manually define and maintain this event_ids we could build them by a"},{"line_number":114,"context_line":"  combination of ``RESOURCE``, ``ACTION`` and ``MESSAGE``, take these for"},{"line_number":115,"context_line":"  example::"},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"    # This is how we define event currently"},{"line_number":118,"context_line":"    IMAGE_FROM_VOLUME_OVER_QUOTA \u003d \u0027VOLUME_000004\u0027"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dfeb2761_ee30580a","line":115,"updated":"2017-03-31 09:53:55.000000000","message":"Supposing messages API would support search by resouce type, action and message, isn\u0027t event_id redundant?","commit_id":"d6c2fd47e47c9a2da9dbe0c0b5b1d01b289c8b96"},{"author":{"_account_id":23083,"name":"TommyLike","email":"tommylikehu@gmail.com","username":"TommyLike"},"change_message_id":"2c6f4818542722a3453e93aede6c5398b235a3a3","unresolved":false,"context_lines":[{"line_number":112,"context_line":"  have \u0027event_id\u0027 no matter how we change the underground behaviour. Instead"},{"line_number":113,"context_line":"  of manually define and maintain this event_ids we could build them by a"},{"line_number":114,"context_line":"  combination of ``RESOURCE``, ``ACTION`` and ``MESSAGE``, take these for"},{"line_number":115,"context_line":"  example::"},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"    # This is how we define event currently"},{"line_number":118,"context_line":"    IMAGE_FROM_VOLUME_OVER_QUOTA \u003d \u0027VOLUME_000004\u0027"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dfeb2761_a1909a44","line":115,"in_reply_to":"dfeb2761_ee30580a","updated":"2017-04-05 08:07:02.000000000","message":"I reckon event_id is not redundant, because this unique id can be easily utilized by upper message collecting projects when they doing filtering, locating and other stuff.","commit_id":"d6c2fd47e47c9a2da9dbe0c0b5b1d01b289c8b96"}]}
