)]}'
{"specs/2026.2/approved/preemptible-instances.rst":[{"robot_id":"zuul","robot_run_id":"ed167f3ea6dc4843ba477a7b20258e5a","url":"https://zuul.teim.app/t/main/buildset/ed167f3ea6dc4843ba477a7b20258e5a","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":"e75015aeda0a8ff66f4f6d5729ee520e77b2d881","patch_set":1,"id":"d4e9b51e_42c6d24d","line":1,"updated":"2026-05-04 14:18:27.000000000","message":"The spec is placed in the \u0027approved\u0027 directory but is clearly a WIP draft with most sections unfilled. This may set incorrect expectations.\n\n**Severity**: SUGGESTION | **Confidence**: 0.8\n\n**Benefit**: Adding a clear WIP marker in the document body makes the status unambiguous when the spec is rendered independently of the commit message.\n\n**Recommendation**:\nConsider adding a note at the top of the spec (below the title) stating this is a WIP draft seeking preliminary design feedback. The [WIP] prefix in the commit message is good but is not visible in the rendered spec.","commit_id":"1d5a9ef30f1572a79c226aac332dcd8eaf55f377"},{"robot_id":"zuul","robot_run_id":"ed167f3ea6dc4843ba477a7b20258e5a","url":"https://zuul.teim.app/t/main/buildset/ed167f3ea6dc4843ba477a7b20258e5a","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":"e75015aeda0a8ff66f4f6d5729ee520e77b2d881","patch_set":1,"id":"d415b305_a086373e","line":21,"updated":"2026-05-04 14:18:27.000000000","message":"The spec uses smart/curly quotes around \u0027preemptible\u0027 on line 21, which may cause rendering or encoding issues in some contexts.\n\n**Severity**: SUGGESTION | **Confidence**: 0.8\n\n**Benefit**: Using straight quotes ensures consistent rendering across all editors, browsers, and build systems, and avoids potential UTF-8 encoding surprises.\n\n**Recommendation**:\nReplace the curly/smart quotes around \u0027preemptible\u0027 with straight quotes on line 21.","commit_id":"1d5a9ef30f1572a79c226aac332dcd8eaf55f377"},{"robot_id":"zuul","robot_run_id":"ed167f3ea6dc4843ba477a7b20258e5a","url":"https://zuul.teim.app/t/main/buildset/ed167f3ea6dc4843ba477a7b20258e5a","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":"e75015aeda0a8ff66f4f6d5729ee520e77b2d881","patch_set":1,"id":"b53294c8_e40a1c28","line":34,"updated":"2026-05-04 14:18:27.000000000","message":"The \u0027high cost--both operational and monetary--associated with.\u0027 sentence on line 34 is grammatically incomplete. The preposition \u0027with\u0027 at the end has no object.\n\n**Severity**: WARNING | **Confidence**: 0.9\n\n**Impact**: An incomplete sentence in the problem description undermines the professional quality of the specification.\n\n**Suggestion**:\nRephrase for clarity, e.g.: \u0027especially because of the high costs associated with it--both operational and monetary.\u0027 or \u0027especially because of the high operational and monetary costs it entails.\u0027","commit_id":"1d5a9ef30f1572a79c226aac332dcd8eaf55f377"},{"robot_id":"zuul","robot_run_id":"ed167f3ea6dc4843ba477a7b20258e5a","url":"https://zuul.teim.app/t/main/buildset/ed167f3ea6dc4843ba477a7b20258e5a","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":"e75015aeda0a8ff66f4f6d5729ee520e77b2d881","patch_set":1,"id":"e221137f_c9741bbf","line":36,"updated":"2026-05-04 14:18:27.000000000","message":"Line 36 has trailing whitespace, which can cause issues with some editors and diff tools.\n\n**Severity**: WARNING | **Confidence**: 1.0\n\n**Impact**: Trailing whitespace is a minor formatting issue that may trigger linting warnings and adds noise to diffs.\n\n**Suggestion**:\nRemove the trailing whitespace from line 36 (\u0027but this can also lead to under resource utilisation. \u0027).","commit_id":"1d5a9ef30f1572a79c226aac332dcd8eaf55f377"},{"robot_id":"zuul","robot_run_id":"ed167f3ea6dc4843ba477a7b20258e5a","url":"https://zuul.teim.app/t/main/buildset/ed167f3ea6dc4843ba477a7b20258e5a","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":"e75015aeda0a8ff66f4f6d5729ee520e77b2d881","patch_set":1,"id":"a3a3280b_66fab322","line":36,"updated":"2026-05-04 14:18:27.000000000","message":"The \u0027under resource utilisation\u0027 phrase on line 36 should be \u0027under-utilisation of resources\u0027 for better grammar and clarity.\n\n**Severity**: WARNING | **Confidence**: 0.8\n\n**Impact**: Awkward phrasing reduces readability of the problem description.\n\n**Suggestion**:\nRephrase to \u0027but this can also lead to under-utilisation of resources.\u0027 or \u0027but this can also result in resources being under-utilised.\u0027","commit_id":"1d5a9ef30f1572a79c226aac332dcd8eaf55f377"},{"robot_id":"zuul","robot_run_id":"ed167f3ea6dc4843ba477a7b20258e5a","url":"https://zuul.teim.app/t/main/buildset/ed167f3ea6dc4843ba477a7b20258e5a","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":"e75015aeda0a8ff66f4f6d5729ee520e77b2d881","patch_set":1,"id":"4ca4d180_d6682453","line":39,"updated":"2026-05-04 14:18:27.000000000","message":"Terminology inconsistency: the spec title and introduction use \u0027preemptible\u0027 but lines 39 and 53 use \u0027preemptable\u0027. One spelling should be chosen and used consistently throughout.\n\n**Severity**: HIGH | **Confidence**: 0.9\n\n**Risk**: Inconsistent terminology creates confusion for implementers and reviewers, and may lead to divergent naming in code, API fields, and documentation.\n\n**Priority**: Before merge\n**Why This Matters**: OpenStack specs serve as the authoritative design reference. Mixed terminology undermines spec clarity and sets a poor precedent for the implementation phase.\n\n**Recommendation**:\nStandardize on \u0027preemptible\u0027 (the spelling used in the title, blueprint URL, and launchpad) throughout the entire document. Change \u0027preemptable\u0027 on lines 39 and 53 to \u0027preemptible\u0027.","commit_id":"1d5a9ef30f1572a79c226aac332dcd8eaf55f377"},{"robot_id":"zuul","robot_run_id":"ed167f3ea6dc4843ba477a7b20258e5a","url":"https://zuul.teim.app/t/main/buildset/ed167f3ea6dc4843ba477a7b20258e5a","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":"e75015aeda0a8ff66f4f6d5729ee520e77b2d881","patch_set":1,"id":"11994195_f3b4ab20","line":41,"updated":"2026-05-04 14:18:27.000000000","message":"The spec claims \u0027Currently, OpenStack does not provide any mechanism to achieve this\u0027 which is inaccurate. Blazar (reservation service) provides resource reservation capabilities and Nova server groups offer related scheduling behaviors that overlap with this use case.\n\n**Severity**: HIGH | **Confidence**: 0.8\n\n**Risk**: An inaccurate problem statement may lead reviewers to question the author\u0027s understanding of the existing OpenStack ecosystem and weaken the justification for the feature.\n\n**Priority**: Before merge\n**Why This Matters**: Accurate problem framing is essential for a spec to be approved. Acknowledging related existing capabilities shows thorough research and helps differentiate the proposed approach.\n\n**Recommendation**:\nRevise the claim to acknowledge existing OpenStack capabilities (Blazar reservations, Nova server groups) and explain why they are insufficient or how this spec complements them. For example: \u0027While OpenStack provides Blazar for resource reservations and Nova server groups for placement policies, there is no integrated mechanism for preemption-based capacity management within Watcher.\u0027","commit_id":"1d5a9ef30f1572a79c226aac332dcd8eaf55f377"},{"robot_id":"zuul","robot_run_id":"ed167f3ea6dc4843ba477a7b20258e5a","url":"https://zuul.teim.app/t/main/buildset/ed167f3ea6dc4843ba477a7b20258e5a","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":"e75015aeda0a8ff66f4f6d5729ee520e77b2d881","patch_set":1,"id":"60c4657a_fc33a836","line":70,"updated":"2026-05-04 14:18:27.000000000","message":"14 of 17 major sections contain only \u0027*writing...\u0027 placeholders, including Proposed change, Alternatives, Data model impact, REST API impact, Security impact, and nine others. No substantive content exists for design review.\n\n**Severity**: HIGH | **Confidence**: 1.0\n\n**Risk**: Without filled sections, reviewers cannot evaluate the technical approach, assess risks, or provide meaningful feedback on the design.\n\n**Priority**: Next sprint\n**Why This Matters**: The template states sections should not be deleted but should say \u0027None\u0027 if not applicable. Placeholder text indicates the spec is not yet ready for substantive review of the proposed solution.\n\n**Recommendation**:\nAt minimum, fill the \u0027Proposed change\u0027 and \u0027Alternatives\u0027 sections before requesting design review. Use \u0027None\u0027 for sections that genuinely have no impact. Consider posting to the mailing list for preliminary scope feedback if not ready for full spec review.","commit_id":"1d5a9ef30f1572a79c226aac332dcd8eaf55f377"},{"robot_id":"zuul","robot_run_id":"ed167f3ea6dc4843ba477a7b20258e5a","url":"https://zuul.teim.app/t/main/buildset/ed167f3ea6dc4843ba477a7b20258e5a","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":"e75015aeda0a8ff66f4f6d5729ee520e77b2d881","patch_set":1,"id":"7a3ada55_af2b773f","line":151,"updated":"2026-05-04 14:18:27.000000000","message":"Line 151 is 116 characters long, exceeding the 79-character wrap limit specified in the watcher-specs template. Line 157 is 95 characters.\n\n**Severity**: WARNING | **Confidence**: 1.0\n\n**Impact**: Long lines may cause formatting issues when rendered to HTML and violate the project\u0027s documented wrapping requirement.\n\n**Suggestion**:\nWrap reference lines. For URLs in references, use Sphinx link syntax to keep lines under 79 chars:\n\n.. _ref1:\n\n[1] AWS Spot Instances Documentation -\nhttps://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-spot-instances.html","commit_id":"1d5a9ef30f1572a79c226aac332dcd8eaf55f377"},{"robot_id":"zuul","robot_run_id":"3138fd1970b346edb212676ed4e91eeb","url":"https://zuul.teim.app/t/main/buildset/3138fd1970b346edb212676ed4e91eeb","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":"5858ccd1e0b9470ce35d4cbf27e236f54930858f","patch_set":2,"id":"73a53105_92293dbf","line":22,"updated":"2026-05-05 17:36:57.000000000","message":"Inconsistent dash usage: the introduction paragraph uses an em dash character on line 22 while the Problem description uses a double dash (--) on line 33.\n\n**Severity**: WARNING | **Confidence**: 0.9\n\n**Impact**: Minor formatting inconsistency that could render differently depending on the RST renderer.\n\n**Suggestion**:\nStandardize on one dash style throughout the document. In RST, em dashes can be represented as \u0027---\u0027 or the Unicode character. Pick one convention and use it consistently.","commit_id":"97bc455a15d3741df0270ba13143a833326b6a78"},{"robot_id":"zuul","robot_run_id":"3138fd1970b346edb212676ed4e91eeb","url":"https://zuul.teim.app/t/main/buildset/3138fd1970b346edb212676ed4e91eeb","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":"5858ccd1e0b9470ce35d4cbf27e236f54930858f","patch_set":2,"id":"a66874e4_e4b17be3","line":35,"updated":"2026-05-05 17:36:57.000000000","message":"Grammar error in Problem description: \u0027the actual quota system only ensures a project to have a fair share\u0027 uses non-idiomatic English. Should use \u0027ensures that a project has\u0027.\n\n**Severity**: WARNING | **Confidence**: 1.0\n\n**Impact**: Impairs readability of the problem description, which is the most complete section of the spec.\n\n**Suggestion**:\nChange \u0027the actual quota system only ensures a project to have a fair share of the cloud resources\u0027 to \u0027the current quota system only ensures that a project has a fair share of cloud resources\u0027.","commit_id":"97bc455a15d3741df0270ba13143a833326b6a78"},{"robot_id":"zuul","robot_run_id":"3138fd1970b346edb212676ed4e91eeb","url":"https://zuul.teim.app/t/main/buildset/3138fd1970b346edb212676ed4e91eeb","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":"5858ccd1e0b9470ce35d4cbf27e236f54930858f","patch_set":2,"id":"450de4f7_d47410b5","line":36,"updated":"2026-05-05 17:36:57.000000000","message":"Grammar error in Problem description: \u0027underutilisation resources\u0027 is missing the preposition \u0027of\u0027. Should read \u0027underutilisation of resources\u0027.\n\n**Severity**: WARNING | **Confidence**: 1.0\n\n**Impact**: Reduces clarity and professionalism of the specification document.\n\n**Suggestion**:\nChange \u0027but this can also lead to underutilisation resources\u0027 to \u0027but this can also lead to underutilisation of resources\u0027.","commit_id":"97bc455a15d3741df0270ba13143a833326b6a78"},{"robot_id":"zuul","robot_run_id":"3138fd1970b346edb212676ed4e91eeb","url":"https://zuul.teim.app/t/main/buildset/3138fd1970b346edb212676ed4e91eeb","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":"5858ccd1e0b9470ce35d4cbf27e236f54930858f","patch_set":2,"id":"cd89a25c_f1d2d846","line":39,"updated":"2026-05-05 17:36:57.000000000","message":"Reference formatting inconsistency: References [1] and [2] have RST named anchors (.. _ref1:, .. _ref2:) but the inline text uses bare [1][2] syntax rather than RST :ref: role or hyperlink syntax. Reference [3] lacks a named anchor entirely.\n\n**Severity**: WARNING | **Confidence**: 0.9\n\n**Impact**: References will not render as clickable links in the generated HTML documentation.\n\n**Suggestion**:\nUse consistent RST reference syntax. Either use RST hyperlink references (e.g., [1]_) with corresponding target definitions, or use the :ref: role with the named anchors. Apply the same format to all three references including [3].","commit_id":"97bc455a15d3741df0270ba13143a833326b6a78"},{"robot_id":"zuul","robot_run_id":"3138fd1970b346edb212676ed4e91eeb","url":"https://zuul.teim.app/t/main/buildset/3138fd1970b346edb212676ed4e91eeb","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":"5858ccd1e0b9470ce35d4cbf27e236f54930858f","patch_set":2,"id":"ee42dcb4_7107e1e0","line":39,"updated":"2026-05-05 17:36:57.000000000","message":"The spec claims \u0027Currently, OpenStack does not provide any mechanism to achieve this\u0027 but does not discuss whether Nova\u0027s server groups, host aggregates, Blazar reservations, or existing placement allocation candidates could be partially leveraged.\n\n**Severity**: SUGGESTION | **Confidence**: 0.8\n\n**Benefit**: Acknowledging related existing mechanisms strengthens the proposal by showing awareness of the broader OpenStack ecosystem.\n\n**Recommendation**:\nIn the Alternatives section, briefly discuss why Nova server groups, host aggregates, or Blazar reservations are insufficient for the preemptible instances use case, and why a Watcher-based approach is preferred.","commit_id":"97bc455a15d3741df0270ba13143a833326b6a78"},{"robot_id":"zuul","robot_run_id":"3138fd1970b346edb212676ed4e91eeb","url":"https://zuul.teim.app/t/main/buildset/3138fd1970b346edb212676ed4e91eeb","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":"5858ccd1e0b9470ce35d4cbf27e236f54930858f","patch_set":2,"id":"67402381_2ffa18a5","line":43,"updated":"2026-05-05 17:36:57.000000000","message":"The spec mentions Watcher\u0027s decision engine but does not describe the preemption strategy or algorithm for selecting which instances to preempt.\n\n**Severity**: SUGGESTION | **Confidence**: 0.9\n\n**Benefit**: Clarifying the preemption strategy early helps reviewers evaluate whether the approach fits within Watcher\u0027s existing strategy/plugin framework.\n\n**Recommendation**:\nDescribe the preemption decision criteria: will it be priority-based (user-assigned priority), cost-based, FIFO, random, or a combination? Explain how this integrates with Watcher\u0027s existing strategy and action plugin architecture.","commit_id":"97bc455a15d3741df0270ba13143a833326b6a78"},{"robot_id":"zuul","robot_run_id":"3138fd1970b346edb212676ed4e91eeb","url":"https://zuul.teim.app/t/main/buildset/3138fd1970b346edb212676ed4e91eeb","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":"5858ccd1e0b9470ce35d4cbf27e236f54930858f","patch_set":2,"id":"45d886d6_d77dd922","line":49,"updated":"2026-05-05 17:36:57.000000000","message":"Grammar issue in Use Cases: \u0027sell it for the customers\u0027 should use \u0027to\u0027 instead of \u0027for\u0027.\n\n**Severity**: WARNING | **Confidence**: 1.0\n\n**Impact**: Minor grammar error in a user-facing specification document.\n\n**Suggestion**:\nChange \u0027sell it for the customers\u0027 to \u0027sell it to customers\u0027 (or \u0027offer it to customers\u0027).","commit_id":"97bc455a15d3741df0270ba13143a833326b6a78"},{"robot_id":"zuul","robot_run_id":"3138fd1970b346edb212676ed4e91eeb","url":"https://zuul.teim.app/t/main/buildset/3138fd1970b346edb212676ed4e91eeb","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":"5858ccd1e0b9470ce35d4cbf27e236f54930858f","patch_set":2,"id":"bb22fe5b_22e929c7","line":67,"updated":"2026-05-05 17:36:57.000000000","message":"The spec should discuss how preemptible instances would be identified in Nova (e.g., via server tags, flavor extra_specs, or a new server property), as this is foundational to the entire feature design.\n\n**Severity**: SUGGESTION | **Confidence**: 0.9\n\n**Benefit**: Would provide reviewers with the critical architectural detail of how Watcher discovers and tracks preemptible instances across the OpenStack deployment.\n\n**Recommendation**:\nIn the Proposed change section, explain the instance identification mechanism. For example, will Watcher rely on a Nova flavor extra_spec like \u0027watcher:preemptible\u003dtrue\u0027, a server tag, or will this require a new Nova API extension? This decision affects dependencies and data model impact.","commit_id":"97bc455a15d3741df0270ba13143a833326b6a78"},{"robot_id":"zuul","robot_run_id":"3138fd1970b346edb212676ed4e91eeb","url":"https://zuul.teim.app/t/main/buildset/3138fd1970b346edb212676ed4e91eeb","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":"5858ccd1e0b9470ce35d4cbf27e236f54930858f","patch_set":2,"id":"18db285a_9cc7380c","line":67,"updated":"2026-05-05 17:36:57.000000000","message":"The specification template recommends ASCII diagrams for complex workflows. The preemption decision flow and instance lifecycle would benefit from a diagram.\n\n**Severity**: SUGGESTION | **Confidence**: 0.8\n\n**Benefit**: A diagram would make the preemption workflow and data flow between Nova, Placement, and Watcher much clearer for reviewers.\n\n**Recommendation**:\nConsider adding an ASCII flow diagram in the Proposed change section showing: (1) how a preemptible instance is created/tagged, (2) how Watcher detects resource pressure, (3) the decision process for selecting instances to preempt, and (4) the preemption execution flow.","commit_id":"97bc455a15d3741df0270ba13143a833326b6a78"},{"robot_id":"zuul","robot_run_id":"3138fd1970b346edb212676ed4e91eeb","url":"https://zuul.teim.app/t/main/buildset/3138fd1970b346edb212676ed4e91eeb","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":"5858ccd1e0b9470ce35d4cbf27e236f54930858f","patch_set":2,"id":"c0f3b685_bce4e20e","line":70,"updated":"2026-05-05 17:36:57.000000000","message":"All major design sections (Proposed change, Alternatives, Data model impact, REST API impact, Security impact, Notifications impact, Other end user impact, Performance Impact, Other deployer impact, Developer impact, Work Items, Dependencies, Testing, Documentation Impact) contain only \u0027*writing...\u0027 placeholder text with no technical content.\n\n**Severity**: HIGH | **Confidence**: 1.0\n\n**Risk**: Reviewers cannot evaluate the technical approach, feasibility, or correctness of the proposed feature. Without any design detail, the spec cannot be meaningfully reviewed or approved.\n\n**Priority**: Before merge\n**Why This Matters**: The watcher-spec template explicitly states sections should either contain substantive content or \u0027None\u0027. Placeholder text prevents any meaningful technical review of the design.\n\n**Recommendation**:\nFill in at minimum the \u0027Proposed change\u0027 and \u0027Alternatives\u0027 sections with concrete technical content before requesting review. Per the template: \u0027At this point, if you would like to just get feedback on if the problem and proposed change fit in Watcher, you can stop here and post this for review to get preliminary feedback.\u0027 If seeking preliminary scope feedback, state that explicitly and remove empty sections below Proposed change.","commit_id":"97bc455a15d3741df0270ba13143a833326b6a78"},{"robot_id":"zuul","robot_run_id":"3138fd1970b346edb212676ed4e91eeb","url":"https://zuul.teim.app/t/main/buildset/3138fd1970b346edb212676ed4e91eeb","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":"5858ccd1e0b9470ce35d4cbf27e236f54930858f","patch_set":2,"id":"fe426660_73a31c9d","line":123,"updated":"2026-05-05 17:36:57.000000000","message":"Missing \u0027Other contributors\u0027 line in the Assignee(s) section. The template includes \u0027Other contributors: \u003claunchpad-id or None\u003e\u0027 but the spec omits it entirely.\n\n**Severity**: WARNING | **Confidence**: 0.9\n\n**Impact**: Minor deviation from the spec template structure. The template says \u0027Please do not delete any of the sections\u0027.\n\n**Suggestion**:\nAdd \u0027Other contributors:\u0027 line (with \u0027None\u0027 if there are no other contributors) to match the template structure.","commit_id":"97bc455a15d3741df0270ba13143a833326b6a78"}]}