)]}'
{"specs/2025.1/approved/dynamic-volume-qos-updates.rst":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"5a5b5620667bcab6de0c3d824ff687f21cfab9ed","unresolved":true,"context_lines":[{"line_number":27,"context_line":"#. Change the volume state from ``in-use`` to ``available`` in cinder."},{"line_number":28,"context_line":"#. Retype volume to volume type with another QoS."},{"line_number":29,"context_line":"#. Return volume to the state ``in-use``."},{"line_number":30,"context_line":"#. For applying volume QoS perform vm live migration."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"The second way also can be used for QoS updating on bootable volume."},{"line_number":33,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3975c0dd_eddde849","line":30,"updated":"2025-01-10 00:45:18.000000000","message":"so really this is somethign that cider should be orchstrating.\n\nthe only way to update h qos on a volume that i was aware of was to retry it.\nso im not sure why we would not first look at modifyign cider to supprot retyping in use volumes without needed to do the in-use -\u003e aviabale -\u003e in-use dance.","commit_id":"4e8dded4c8370a4022cfa45c851c1e3518333a61"},{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"adc00fa3bc2757109647859adddba927d4d4ee76","unresolved":true,"context_lines":[{"line_number":56,"context_line":"* Add logic to support QoS updates to nova compute."},{"line_number":57,"context_line":"* Add the set method to libvirt driver."},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"When this api is called there are actual QoS values in ``connection_info``"},{"line_number":60,"context_line":"data. It can be used to update volume QoS. This spec proposes to implement the"},{"line_number":61,"context_line":"way of dynamic volume QoS adjusting for libvirt driver only. To support QoS"},{"line_number":62,"context_line":"updates ``setBlockIoTune`` libvirt api can be used."}],"source_content_type":"text/x-rst","patch_set":1,"id":"edfca1c2_c79e5bdb","line":59,"updated":"2025-01-08 16:24:50.000000000","message":"I don\u0027t see ``connection_info`` in the request body of https://docs.openstack.org/api-ref/compute/#update-a-volume-attachment So I\u0027m a bit confused where the new QoS values are coming from.","commit_id":"4e8dded4c8370a4022cfa45c851c1e3518333a61"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"5a5b5620667bcab6de0c3d824ff687f21cfab9ed","unresolved":true,"context_lines":[{"line_number":56,"context_line":"* Add logic to support QoS updates to nova compute."},{"line_number":57,"context_line":"* Add the set method to libvirt driver."},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"When this api is called there are actual QoS values in ``connection_info``"},{"line_number":60,"context_line":"data. It can be used to update volume QoS. This spec proposes to implement the"},{"line_number":61,"context_line":"way of dynamic volume QoS adjusting for libvirt driver only. To support QoS"},{"line_number":62,"context_line":"updates ``setBlockIoTune`` libvirt api can be used."}],"source_content_type":"text/x-rst","patch_set":1,"id":"06e14f7e_44b206ae","line":59,"in_reply_to":"edfca1c2_c79e5bdb","updated":"2025-01-10 00:45:18.000000000","message":"well they are comeming form cinder i think.\nnova woudl have to create a new atachment for the voluem and update the xml based on the new data.","commit_id":"4e8dded4c8370a4022cfa45c851c1e3518333a61"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"5a5b5620667bcab6de0c3d824ff687f21cfab9ed","unresolved":true,"context_lines":[{"line_number":84,"context_line":"            \"volumeId\": \"3399c872-ed11-4c91-823c-9dfd0daf61c6\","},{"line_number":85,"context_line":"            \"update_qos\": true"},{"line_number":86,"context_line":"        }"},{"line_number":87,"context_line":"    }"},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"Security impact"},{"line_number":90,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"39a3fe88_bf0bdaf1","line":87,"updated":"2025-01-10 00:45:18.000000000","message":"who would call this api?\n\nif you suggesting a user would i dont think that is a good workflow.\n\nare you suggesting that cinder will do this in respocne to a request to retype the volume?\n\n\nif this is in respocne to a volume retype i think we shoudl be using the server external events api like we do for resize instead.\n\nwe can add a volume-qos-update external event insetad that would be sent by cinder to nova if and only if the cinder volume was usign frontend qos.","commit_id":"4e8dded4c8370a4022cfa45c851c1e3518333a61"}]}