)]}'
{"specs/2027.1/approved/zone-migration-improvements.rst":[{"author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"8b874eb8a31a662deb596c2ef8d44ebe18175553","unresolved":false,"context_lines":[{"line_number":17,"context_line":"Problem Description"},{"line_number":18,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"The ``zone_migration`` strategy has some shortcomings that limits draining"},{"line_number":21,"context_line":"hosts and storage today:"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"* The ``parallel_total``, ``parallel_per_node`` and ``parallel_per_pool``"}],"source_content_type":"text/x-rst","patch_set":1,"id":"c2706ea2_8e19d0dc","line":20,"updated":"2026-11-18 19:27:48.000000000","message":"Three writing defects slipped into the spec text: a subject-verb disagreement in the problem statement, a misspelling of \u0027counter\u0027 in the parallel-counter semantics paragraph, and a comma splice in the volume-selection rules. Each is small but lands in the permanent specification record that implementation work and future reviews will quote.\n\n**Severity**: SUGGESTION | **Confidence**: 0.9\n\n**Impact**: Purely editorial: the errors do not change the meaning, but they reduce the polish of a long-lived design document, and the spec file is the primary artifact this repository produces.\n\n**Recommendation**:\nChange \u0027limits\u0027 to \u0027limit\u0027 (line 20), \u0027copunter\u0027 to \u0027counter\u0027 (line 75), and break the comma splice at lines 97-99, for example \u0027A type-only entry must use ``dst_type``; the combination ``{src_type, dst_pool}`` is rejected, because ...\u0027","commit_id":"0e293bd38b20b73c424851b362d9c016916c3a52"},{"author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"8b874eb8a31a662deb596c2ef8d44ebe18175553","unresolved":false,"context_lines":[{"line_number":57,"context_line":"Unlimited Parallel Counters"},{"line_number":58,"context_line":"---------------------------"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"The three counters,``parallel_total``, ``parallel_per_node`` and"},{"line_number":61,"context_line":"``parallel_per_pool``, are deprecated and made unlimited by default:"},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"* Any counter may be set to ``-1``, meaning no cap is applied. The JSON"}],"source_content_type":"text/x-rst","patch_set":1,"id":"8ce2a47a_9799261c","line":60,"updated":"2026-11-18 19:27:48.000000000","message":"Line 60 places the inline literal start-string for the first counter name immediately after a comma with no whitespace. docutils only recognizes inline markup when the start-string is preceded by whitespace (comma is not in the accepted preceding-character set), so the first counter name in the deprecation statement is not rendered as literal text, unlike the two counter names beside it on the same line.\n\n**Severity**: WARNING | **Confidence**: 0.93\n\n**Impact**: The spec is published at specs.openstack.org and is the permanent record implementers and reviewers consult. On that page the first counter name shows raw markup characters, making the key deprecation paragraph look broken and inconsistently formatted relative to the adjacent names.\n\n**Suggestion**:\nAdd a space after \u0027counters,\u0027 so the line reads \u0027The three counters, ``parallel_total``, ``parallel_per_node`` and ``parallel_per_pool``, are deprecated and made unlimited by default:\u0027. No other line in the file has the same problem.","commit_id":"0e293bd38b20b73c424851b362d9c016916c3a52"}]}
