)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":27615,"name":"Rajat Dhasmana","email":"rajatdhasmana@gmail.com","username":"whoami-rajat"},"change_message_id":"16d2b8e1a78de779c0efbe9939a7cb236d7c9371","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"4000aa59_927337b7","updated":"2025-01-24 14:02:57.000000000","message":"The spec looks good though it\u0027s very abstract and doesn\u0027t reflect the changes required in Cinder to get the migration progress in a generic migration case (available volume) but we can discuss that in the implementation.","commit_id":"ae9076bdf8651d351e093d5e58b595ed34de4ff9"}],"specs/2025.1/migration-progress-in-volume-details.rst":[{"author":{"_account_id":34860,"name":"Amit Uniyal","email":"auniyal@redhat.com","username":"auniyal"},"change_message_id":"94ada6382d237300ea76fa602cee67fc1817ee76","unresolved":false,"context_lines":[{"line_number":38,"context_line":"The API code for showing a volume\u0027s details would use a microversion to"},{"line_number":39,"context_line":"optionally include a ``migration_progress`` field. The field would be included"},{"line_number":40,"context_line":"in the API response only when the volume is migrating, and when permitted by"},{"line_number":41,"context_line":"the microversion. As the existing ``migration_status`` field is admin-only,"},{"line_number":42,"context_line":"the new field would also be admin-only."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"The value would be obtained via an RPC that fetches a response from either the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"d5654c2d_fb712e57","line":41,"range":{"start_line":41,"start_character":36,"end_line":41,"end_character":52},"updated":"2025-02-04 04:01:49.000000000","message":"I was thinking why not just use this exising one only - None, [1% - 99%], Done.\nbut we do track staus \"migrating\" in nova, may be others in many places too.","commit_id":"ae9076bdf8651d351e093d5e58b595ed34de4ff9"},{"author":{"_account_id":27615,"name":"Rajat Dhasmana","email":"rajatdhasmana@gmail.com","username":"whoami-rajat"},"change_message_id":"16d2b8e1a78de779c0efbe9939a7cb236d7c9371","unresolved":true,"context_lines":[{"line_number":227,"context_line":"Testing"},{"line_number":228,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":229,"context_line":""},{"line_number":230,"context_line":"TBD. The tricky part for incorporating something into a tempest test is"},{"line_number":231,"context_line":"catching a migration operation during the time it\u0027s copying the volume data,"},{"line_number":232,"context_line":"which is the only time when the ``migration_progress`` field will be present"},{"line_number":233,"context_line":"in the volume details response."},{"line_number":234,"context_line":""},{"line_number":235,"context_line":"Documentation Impact"},{"line_number":236,"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":3,"id":"6eff7a46_9174481e","line":233,"range":{"start_line":230,"start_character":0,"end_line":233,"end_character":31},"updated":"2025-01-24 14:02:57.000000000","message":"Since we know migration is a slow process, migrating a 1-2GB volume and immediately calling volume detail API to fetch the migration info seems feasible though if still the migration_progress is not visible we can check the volume migration status:\n1. If migration_status !\u003d migrating, don\u0027t fail\n2. If migration_status \u003d\u003d migrating, fail\n\nWe will also need testing around the following scenarios:\n1. migration_progress not visible by non-admins\n2. migration_progress is not visible without the right microversion\n3. migration_progress is not visible with non-migrating volumes (available/in-use)","commit_id":"ae9076bdf8651d351e093d5e58b595ed34de4ff9"}]}