)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":7173,"name":"Scott DAngelo","email":"scott.dangelo@gmail.com","username":"scottda"},"change_message_id":"7be4268e407bcb8292f624d8107a5abba4f0ad53","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"RBD: use user-configured value for chunk size"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This patch allows a user to override the default chunk size in"},{"line_number":10,"context_line":"cinder.conf."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: I66a99950b7c4080de932be7ddac2f1595b9d59f4"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3a50d1a3_3e2b9a83","line":9,"updated":"2015-07-29 16:01:49.000000000","message":"This code looks like it will always use self.configuration.rbd_store_chunk_size CONF.rbd_store_chunk_size  which has a default of 4 (if the user does not provide input) instead of any value in CONF.rbd_store_chunk_size \nSo either the commit message should be changed to state that we are not using what is in cinder.conf or the code should change to allow cinder.conf value to be the default.","commit_id":"43691d77bbd6f830bb563ee5845e0c109dbe19b7"},{"author":{"_account_id":17405,"name":"Jacob Gregor","email":"jgregor@us.ibm.com","username":"jgregor"},"change_message_id":"80d4fca924bbeb6311b6ef0d65fb5c7b87098951","unresolved":false,"context_lines":[{"line_number":7,"context_line":"RBD: use user-configured value for chunk size"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This patch allows a user to override the default chunk size in"},{"line_number":10,"context_line":"cinder.conf."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: I66a99950b7c4080de932be7ddac2f1595b9d59f4"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3a50d1a3_89c71344","line":10,"updated":"2015-07-29 18:47:26.000000000","message":"The commit message should have a little more detail explaining why this patch is needed.\n\nAlso wondering if there is any API/DocImpact or similar documentation that goes with this patch.","commit_id":"43691d77bbd6f830bb563ee5845e0c109dbe19b7"}]}