)]}'
{"cinder/volume/drivers/quobyte.py":[{"author":{"_account_id":36171,"name":"jayaanand borra","display_name":"jayaanand borra","email":"jayaanand.borra@netapp.com","username":"jayaanan","status":"netapp"},"change_message_id":"f2b67c31cc956bb276172b986dba0742e0db2b6a","unresolved":true,"context_lines":[{"line_number":715,"context_line":""},{"line_number":716,"context_line":"        if refresh:"},{"line_number":717,"context_line":"            self._update_volume_stats()"},{"line_number":718,"context_line":"        return self._stats"},{"line_number":719,"context_line":""},{"line_number":720,"context_line":"    # open() wrapper to mock reading from /proc/mount."},{"line_number":721,"context_line":"    @staticmethod"}],"source_content_type":"text/x-python","patch_set":1,"id":"716acac1_04e0784c","line":718,"updated":"2026-08-16 14:43:35.000000000","message":"in the inheritance change top most Base class is BaseVD is get_volume_status has same function. what you gain by placing same signature and ignore refresh?","commit_id":"49302a56560d66c9f3365d5633cd2c0f1b0191c8"},{"author":{"_account_id":13915,"name":"Silvan Kaiser","email":"silvan@quobyte.com","username":"kaisers"},"change_message_id":"890a04e23a4b6c4d021f50c83f87a644eb63d04f","unresolved":true,"context_lines":[{"line_number":715,"context_line":""},{"line_number":716,"context_line":"        if refresh:"},{"line_number":717,"context_line":"            self._update_volume_stats()"},{"line_number":718,"context_line":"        return self._stats"},{"line_number":719,"context_line":""},{"line_number":720,"context_line":"    # open() wrapper to mock reading from /proc/mount."},{"line_number":721,"context_line":"    @staticmethod"}],"source_content_type":"text/x-python","patch_set":1,"id":"f70d6b36_8a37cfd3","line":718,"in_reply_to":"716acac1_04e0784c","updated":"2026-08-17 12:08:30.000000000","message":"fair point, this is a backport artifact that is not needed here (it doesn\u0027t hurt much, either). So i wonder what to prefer, kicking this out (clean) or keep consistency with the origin of this backport.\nI\u0027m currently thinking i\u0027ll re-do this in master and then port that cleanup back in here into the backports, too. Is that workable?","commit_id":"49302a56560d66c9f3365d5633cd2c0f1b0191c8"}],"releasenotes/notes/qb_thinprov-a8ed645f8ba51d26.yaml":[{"author":{"_account_id":36171,"name":"jayaanand borra","display_name":"jayaanand borra","email":"jayaanand.borra@netapp.com","username":"jayaanan","status":"netapp"},"change_message_id":"f2b67c31cc956bb276172b986dba0742e0db2b6a","unresolved":true,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"features:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Quobyte driver: adds thin provisioning support for Quobyte volumes."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"6feec7d4_5165661a","line":4,"updated":"2026-08-16 14:43:35.000000000","message":"can you elaborate about capacity behavior and its impact on scheduling as part of documentation.","commit_id":"49302a56560d66c9f3365d5633cd2c0f1b0191c8"},{"author":{"_account_id":13915,"name":"Silvan Kaiser","email":"silvan@quobyte.com","username":"kaisers"},"change_message_id":"890a04e23a4b6c4d021f50c83f87a644eb63d04f","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"features:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Quobyte driver: adds thin provisioning support for Quobyte volumes."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1e34490a_a43006fd","line":4,"in_reply_to":"6feec7d4_5165661a","updated":"2026-08-17 12:08:30.000000000","message":"mmh, i do not think capacity behaviour and scheduling impact belong into a release note of a backport. Those should be looked up in the general documentation of Cinder / Quobyte.","commit_id":"49302a56560d66c9f3365d5633cd2c0f1b0191c8"}]}