)]}'
{"specs/liberty/approved/hyperv-storage-qos.rst":[{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"68ab05abf81c35ef12e64cbad155736200095cc3","unresolved":false,"context_lines":[{"line_number":68,"context_line":"    nova volume-attach \u003chyperv_instance_id\u003e \u003cvolume_id\u003e"},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"* Admin sets instance storage QoS specs on the flavor"},{"line_number":71,"context_line":"    nova flavor-key \u003cmy_flavor\u003e set storage_qos:total_bytes_sec\u003d20971520 \\"},{"line_number":72,"context_line":"                                    storage_qos:min_bytes_sec\u003d20971520"},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3acd31a7_7725cac0","line":71,"updated":"2015-04-29 14:39:55.000000000","message":"maybe we should make this storage_local_qos? i.e. so it explicitly excludes cinder volumes.\n\nThis doesn\u0027t cover the general case, but I think that sounds reasonable.\n\nAlso are these front-end or back-end, should we make that clear somehow?","commit_id":"b7949d11258650297436f3ba349e8a4a2804dc44"},{"author":{"_account_id":8543,"name":"Lucian Petrut","email":"lpetrut@cloudbasesolutions.com","username":"plucian"},"change_message_id":"6e77f24d6b5f83db4c4a98b38b6b6cf197737eca","unresolved":false,"context_lines":[{"line_number":68,"context_line":"    nova volume-attach \u003chyperv_instance_id\u003e \u003cvolume_id\u003e"},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"* Admin sets instance storage QoS specs on the flavor"},{"line_number":71,"context_line":"    nova flavor-key \u003cmy_flavor\u003e set storage_qos:total_bytes_sec\u003d20971520 \\"},{"line_number":72,"context_line":"                                    storage_qos:min_bytes_sec\u003d20971520"},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3acd31a7_ad2c114b","line":71,"in_reply_to":"3acd31a7_7725cac0","updated":"2015-04-30 10:46:31.000000000","message":"I agree on the storage_local_qos scope name.\n\nCinder has nothing to do with those disks and since those are stored on the hypervisor node, we may consider it to be the back-end of those disks, thus having only back-end QoS specs in this case.","commit_id":"b7949d11258650297436f3ba349e8a4a2804dc44"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"68ab05abf81c35ef12e64cbad155736200095cc3","unresolved":false,"context_lines":[{"line_number":70,"context_line":"* Admin sets instance storage QoS specs on the flavor"},{"line_number":71,"context_line":"    nova flavor-key \u003cmy_flavor\u003e set storage_qos:total_bytes_sec\u003d20971520 \\"},{"line_number":72,"context_line":"                                    storage_qos:min_bytes_sec\u003d20971520"},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"Alternatives"},{"line_number":75,"context_line":"------------"},{"line_number":76,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"3acd31a7_da860565","line":73,"updated":"2015-04-29 14:39:55.000000000","message":"Can we please give a clear list of all the supported options please? Can we also please define what they mean, such that making this cross hypervisor should be possilbe\n\nits it just total_bytes, or does it include read_bypes write_bytes, or iops instead of bytes?","commit_id":"b7949d11258650297436f3ba349e8a4a2804dc44"},{"author":{"_account_id":8543,"name":"Lucian Petrut","email":"lpetrut@cloudbasesolutions.com","username":"plucian"},"change_message_id":"6e77f24d6b5f83db4c4a98b38b6b6cf197737eca","unresolved":false,"context_lines":[{"line_number":70,"context_line":"* Admin sets instance storage QoS specs on the flavor"},{"line_number":71,"context_line":"    nova flavor-key \u003cmy_flavor\u003e set storage_qos:total_bytes_sec\u003d20971520 \\"},{"line_number":72,"context_line":"                                    storage_qos:min_bytes_sec\u003d20971520"},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"Alternatives"},{"line_number":75,"context_line":"------------"},{"line_number":76,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"3acd31a7_4d733db2","line":73,"in_reply_to":"3acd31a7_da860565","updated":"2015-04-30 10:46:31.000000000","message":"Sure, I\u0027ll add this.","commit_id":"b7949d11258650297436f3ba349e8a4a2804dc44"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"68ab05abf81c35ef12e64cbad155736200095cc3","unresolved":false,"context_lines":[{"line_number":101,"context_line":""},{"line_number":102,"context_line":"While minimum IOPS will not be enforced, Hyper-V will trigger events in case"},{"line_number":103,"context_line":"disk IOPS go below this threshold. Handling those events and emitting"},{"line_number":104,"context_line":"notifications is out of the scope of this blueprint."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"Other end user impact"},{"line_number":107,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3acd31a7_17033611","line":104,"updated":"2015-04-29 14:39:55.000000000","message":"What does that mean?\n\nI assumed minimum IOPs was more about some kinda of guaranteed level of IOPs?","commit_id":"b7949d11258650297436f3ba349e8a4a2804dc44"},{"author":{"_account_id":8543,"name":"Lucian Petrut","email":"lpetrut@cloudbasesolutions.com","username":"plucian"},"change_message_id":"6e77f24d6b5f83db4c4a98b38b6b6cf197737eca","unresolved":false,"context_lines":[{"line_number":101,"context_line":""},{"line_number":102,"context_line":"While minimum IOPS will not be enforced, Hyper-V will trigger events in case"},{"line_number":103,"context_line":"disk IOPS go below this threshold. Handling those events and emitting"},{"line_number":104,"context_line":"notifications is out of the scope of this blueprint."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"Other end user impact"},{"line_number":107,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3acd31a7_6d7cb972","line":104,"in_reply_to":"3acd31a7_17033611","updated":"2015-04-30 10:46:31.000000000","message":"Actually, this does not guarantee a minimum IOPS threshold, but emits events in case the the IOPS go bellow this threshold. I\u0027ll try to make this clear in the specs.","commit_id":"b7949d11258650297436f3ba349e8a4a2804dc44"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"66f54003b3316ae307f482785f131405c82b03ef","unresolved":false,"context_lines":[{"line_number":111,"context_line":""},{"line_number":112,"context_line":"While minimum IOPS are not guaranteed, Hyper-V will trigger events in case"},{"line_number":113,"context_line":"disk IOPS go below this threshold. Handling those events and emitting"},{"line_number":114,"context_line":"notifications is out of the scope of this blueprint."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"Other end user impact"},{"line_number":117,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":7,"id":"9af37de9_f5fd3e6f","line":114,"updated":"2015-05-11 10:32:43.000000000","message":"I am unsure about the feature if these notifications are out of scope.\n\nCould we consider just adding total_bytes_sec/total_iops_sec and looking at adding min as a separate spec?","commit_id":"6c6a15078080c96c22c7cce6d79d40b5d668c4b0"},{"author":{"_account_id":2271,"name":"Michael Still","email":"mikal@stillhq.com","username":"mikalstill"},"change_message_id":"12c5f366abb5f7a81162dc3fc3b69ba97b197095","unresolved":false,"context_lines":[{"line_number":72,"context_line":"Available QoS specs:"},{"line_number":73,"context_line":"    * total_bytes_sec - includes read/writes"},{"line_number":74,"context_line":""},{"line_number":75,"context_line":"    * total_iops_sec - already used by the Libvirt driver"},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"Alternatives"},{"line_number":78,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":8,"id":"5ad58531_6d02b540","line":75,"updated":"2015-05-11 19:31:17.000000000","message":"I feel like we shouldn\u0027t have different specs per hypervisor. What is your reasoning for not using total_iops_sec in your implementation?","commit_id":"122cb3747ce997891340eec5cc04f563449ce149"},{"author":{"_account_id":8543,"name":"Lucian Petrut","email":"lpetrut@cloudbasesolutions.com","username":"plucian"},"change_message_id":"a22b281161ffd5d4141fc6fcf3371196cadb812c","unresolved":false,"context_lines":[{"line_number":72,"context_line":"Available QoS specs:"},{"line_number":73,"context_line":"    * total_bytes_sec - includes read/writes"},{"line_number":74,"context_line":""},{"line_number":75,"context_line":"    * total_iops_sec - already used by the Libvirt driver"},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"Alternatives"},{"line_number":78,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":8,"id":"5ad58531_f681d64e","line":75,"in_reply_to":"5ad58531_6d02b540","updated":"2015-05-11 20:31:31.000000000","message":"Actually, I am using it. I was just trying to underline the fact that this will be consistent with Libvirt. I\u0027m sorry if this was rather misleading.\n\nI\u0027ll try to rephrase this.","commit_id":"122cb3747ce997891340eec5cc04f563449ce149"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"20b60c905e5186ee6f3072bc2fdfd4f7413e5da3","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Problem description"},{"line_number":20,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Use Cases"},{"line_number":23,"context_line":"----------"},{"line_number":24,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"3afb71cf_c1991e70","line":21,"updated":"2015-06-08 09:32:01.000000000","message":"This section is missing here, although I am going to overlook this given how long we have been iterating doesn\u0027t make sense given the impact of the work.","commit_id":"732595578e17dc2e7fc679bc95ab1ddb67f2151b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"20b60c905e5186ee6f3072bc2fdfd4f7413e5da3","unresolved":false,"context_lines":[{"line_number":119,"context_line":"---------------------"},{"line_number":120,"context_line":""},{"line_number":121,"context_line":"Apart from the volume and flavor QoS specs, we may add configurable default"},{"line_number":122,"context_line":"IOPS caps."},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"Developer impact"},{"line_number":125,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3afb71cf_81cb2653","line":122,"updated":"2015-06-08 09:32:01.000000000","message":"I don\u0027t like: \"we may add\", the spec is meant to define what is happening.\n\nAgain, I am overlooking this, in the hope we revise the spec later to include what actually happened.","commit_id":"732595578e17dc2e7fc679bc95ab1ddb67f2151b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"20b60c905e5186ee6f3072bc2fdfd4f7413e5da3","unresolved":false,"context_lines":[{"line_number":150,"context_line":"Testing"},{"line_number":151,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"This feature will be tested by the Hyper-V CI."},{"line_number":154,"context_line":""},{"line_number":155,"context_line":"Documentation Impact"},{"line_number":156,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":9,"id":"3afb71cf_21c0f229","line":153,"updated":"2015-06-08 09:32:01.000000000","message":"Thats quite a bold statement... I doubt tempest tests will check these kinds of things, but again, going to overlook that.","commit_id":"732595578e17dc2e7fc679bc95ab1ddb67f2151b"}]}