)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"f65b81f594477181d88c09c0a90a8b01df36e785","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"21cac65b_b0d683db","updated":"2026-10-13 11:26:14.000000000","message":"-1 is for the cancelation and piplien update semantic gaps noted inline\n\nim also unsure if we really can defer the stroage model emulation\nit probably shoudl be a strech goal at the elast and we need to decied\nif that means you cannot use stragies that produce storage action as part of the plan in a pipleine or howe that works because im not sure we can add this later without chaging behvior.","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":34452,"name":"Joan Gilabert","display_name":"jgilaber","email":"jgilaber@redhat.com","username":"jgilaber"},"change_message_id":"6b6c242391e547f21726134b110ceadc38d91d4b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"df263c56_29e705b6","updated":"2026-09-29 11:30:45.000000000","message":"the changes lgtm and the spec renders well https://dd2708c069c2d2c6f740-5c1e119604e6c3a613471c5b91ef3887.ssl.cf2.rackcdn.com/openstack/2bb671598ec24b2daff404980a3eb851/docs/specs/2027.1/approved/audit-pipeline.html","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"b83c53d48b583482613b7f6d5b3d7634e6501677","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7d002aab_19ccb14a","in_reply_to":"21cac65b_b0d683db","updated":"2026-10-15 12:12:41.000000000","message":"storage model was removed from 2026.2 implementation due to the amount of work already in progress, but we can add it back for Indri proposal yes.","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"ee3e08ff18140aaa3d31c6cd398557e166eea6d1","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e75b5627_ad7a47eb","in_reply_to":"7d002aab_19ccb14a","updated":"2026-10-20 14:04:10.000000000","message":"Done, added both storage_model implementation and CANCELLING state proposal for Audit Pipeline. We may double check Audit case wrt to CANCELLING state too.","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":16312,"name":"Alfredo Moralejo","email":"amoralej@redhat.com","username":"amoralej"},"change_message_id":"901611730355173131511f8e43a1c07d5f83d469","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"51ba5606_ea074521","updated":"2026-10-20 15:43:15.000000000","message":"I\u0027m mostly fine with the changes in the spec. Just a couple of comments.","commit_id":"14de18fe39745ab25cc43fd357e079896cd479c7"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"b13912017f5d80eafed5c0d0a82d5b548d406c95","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"ec39dc1f_6bf54377","updated":"2026-10-20 18:04:38.000000000","message":"Thanks for reviewing Alfredo","commit_id":"14de18fe39745ab25cc43fd357e079896cd479c7"},{"author":{"_account_id":16312,"name":"Alfredo Moralejo","email":"amoralej@redhat.com","username":"amoralej"},"change_message_id":"f4d43ef6e5ad9a07b19e97b784b31d65f95ce75f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"cff9ea28_987289a2","updated":"2026-10-28 08:04:10.000000000","message":"As discussed in the inline comments, I think this is good to go.","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"},{"author":{"_account_id":16312,"name":"Alfredo Moralejo","email":"amoralej@redhat.com","username":"amoralej"},"change_message_id":"ab1076eb6f69eb0286c87e2285d64c1791e7cd41","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"c3266bc4_929e1180","updated":"2026-10-23 10:04:36.000000000","message":"Sorry for the last minute addition but I just realized we need to do at least two more things for the watcher-pipelines:\n\n1. Support for purging soft_deleted objects in dbmanage https://github.com/openstack/watcher/blob/master/watcher/db/purge.py . That\u0027s the current way of purging old db objects which have been soft deleted from the database.\n2. Managing auditpipelines in decision-engine sync in https://github.com/openstack/watcher/blob/master/watcher/decision_engine/sync.py . That sync covers two cases, strategy/goal update and strategy/goal removal. I think we should make auditpipelines and auditpipelinesstages consistent with audits or at least cover the goal/strategy deletion case. For updates, i plan to work on it in this cycle, but I\u0027d say we should also make them consistent to curreent behavior and fix it later if needed.\n\nWe probably should mention it in the spec althoug no much detail if needed so that we don\u0027t forget it in the implementation phase.","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"e7db942439562662e22c1f2e92ea65ead4388cd1","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":3,"id":"ba7eca1a_948695d7","updated":"2026-10-27 18:31:30.000000000","message":"i do not have any stong feelign either way\n\ni think we could proceed with this as is.\n\nthere are certely parts we coudl continue to refine but without increase the scope more i think this is as code as we can do for now","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"},{"author":{"_account_id":34452,"name":"Joan Gilabert","display_name":"jgilaber","email":"jgilaber@redhat.com","username":"jgilaber"},"change_message_id":"31e194f5505f09b33dd784076fe85e40a50a0cf3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"89f61c74_a09a6067","updated":"2026-11-04 12:40:06.000000000","message":"lgtm, there are some minor changes that could be applied, but I think this is good to go as is","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"3484e445f60401130f04182bc7b28353681bf4df","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":3,"id":"91bbd202_ea1c9547","in_reply_to":"c3266bc4_929e1180","updated":"2026-10-23 12:16:10.000000000","message":"Correct.\n1) I completly missed that in implemenatation too, thanks for raising it.\n2) Yes, I can cover in the upgrade session. I have that change staged here. I can also include here the cancel of the ONGOING ones in the scheduling class (similar to Audits).\nI will update the spec adding those, and resolve the comments afterwards.","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"}],"specs/2027.1/approved/audit-pipeline.rst":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"f65b81f594477181d88c09c0a90a8b01df36e785","unresolved":true,"context_lines":[{"line_number":64,"context_line":"the strategy parameters of each pipeline stage."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"The initial implementation is intentionally scoped to ONESHOT audit pipelines"},{"line_number":67,"context_line":"using cascade execution. CONTINUOUS and EVENT audit pipelines, composite"},{"line_number":68,"context_line":"execution, and recurring pipeline scheduling are out of scope for the first"},{"line_number":69,"context_line":"implementation and may be proposed in a future spec."},{"line_number":70,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5ec6b68e_9c696c72","line":67,"range":{"start_line":67,"start_character":0,"end_line":67,"end_character":24},"updated":"2026-10-13 11:26:14.000000000","message":"nit: i have the context form last cycle and an implict understanding of the terms cascade adn composite because i proposted those names but a new reader would not\n\nwe proably shoudl have a short glossary of terms or define them when they are first used to make this eaiser to read for someone without that.\n\nyou could also just remove the last sentace form ehre and move it to the alternitives section.","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"ee3e08ff18140aaa3d31c6cd398557e166eea6d1","unresolved":false,"context_lines":[{"line_number":64,"context_line":"the strategy parameters of each pipeline stage."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"The initial implementation is intentionally scoped to ONESHOT audit pipelines"},{"line_number":67,"context_line":"using cascade execution. CONTINUOUS and EVENT audit pipelines, composite"},{"line_number":68,"context_line":"execution, and recurring pipeline scheduling are out of scope for the first"},{"line_number":69,"context_line":"implementation and may be proposed in a future spec."},{"line_number":70,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"fc79b3e2_fa42fdfe","line":67,"range":{"start_line":67,"start_character":0,"end_line":67,"end_character":24},"in_reply_to":"4182a510_2efa851e","updated":"2026-10-20 14:04:10.000000000","message":"Done","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"b83c53d48b583482613b7f6d5b3d7634e6501677","unresolved":true,"context_lines":[{"line_number":64,"context_line":"the strategy parameters of each pipeline stage."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"The initial implementation is intentionally scoped to ONESHOT audit pipelines"},{"line_number":67,"context_line":"using cascade execution. CONTINUOUS and EVENT audit pipelines, composite"},{"line_number":68,"context_line":"execution, and recurring pipeline scheduling are out of scope for the first"},{"line_number":69,"context_line":"implementation and may be proposed in a future spec."},{"line_number":70,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"4182a510_2efa851e","line":67,"range":{"start_line":67,"start_character":0,"end_line":67,"end_character":24},"in_reply_to":"5ec6b68e_9c696c72","updated":"2026-10-15 12:12:41.000000000","message":"ack, makes sense.","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"f65b81f594477181d88c09c0a90a8b01df36e785","unresolved":true,"context_lines":[{"line_number":88,"context_line":"All pipelines start in ``PENDING`` state. ``DELETED`` is the final soft-delete"},{"line_number":89,"context_line":"state. ``SUSPENDED`` remains an Audit state only, and suspending and resuming"},{"line_number":90,"context_line":"pipelines is out of scope until recurring CONTINUOUS or EVENT pipelines are"},{"line_number":91,"context_line":"specified."},{"line_number":92,"context_line":""},{"line_number":93,"context_line":"An Audit Pipeline is similar to an Audit, with these differences:"},{"line_number":94,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"ad3df500_d95eede3","line":91,"range":{"start_line":91,"start_character":0,"end_line":91,"end_character":9},"updated":"2026-10-13 11:26:14.000000000","message":"supported or implmenented","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"ee3e08ff18140aaa3d31c6cd398557e166eea6d1","unresolved":false,"context_lines":[{"line_number":88,"context_line":"All pipelines start in ``PENDING`` state. ``DELETED`` is the final soft-delete"},{"line_number":89,"context_line":"state. ``SUSPENDED`` remains an Audit state only, and suspending and resuming"},{"line_number":90,"context_line":"pipelines is out of scope until recurring CONTINUOUS or EVENT pipelines are"},{"line_number":91,"context_line":"specified."},{"line_number":92,"context_line":""},{"line_number":93,"context_line":"An Audit Pipeline is similar to an Audit, with these differences:"},{"line_number":94,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"16b9bdb0_68e0ed51","line":91,"range":{"start_line":91,"start_character":0,"end_line":91,"end_character":9},"in_reply_to":"ad3df500_d95eede3","updated":"2026-10-20 14:04:10.000000000","message":"Done","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"f65b81f594477181d88c09c0a90a8b01df36e785","unresolved":true,"context_lines":[{"line_number":95,"context_line":"* It accepts a list of stage objects. Each stage references one Audit Template."},{"line_number":96,"context_line":"  The goal, strategy, scope, and parameters used by the stage are snapshotted"},{"line_number":97,"context_line":"  from that Audit Template when the pipeline is created."},{"line_number":98,"context_line":"* Unlike Audit, Audit Pipeline will not accept strategy ``input_parameters``"},{"line_number":99,"context_line":"  directly. Strategy parameters must be defined as ``default_parameters`` in"},{"line_number":100,"context_line":"  the Audit Template for each stage."},{"line_number":101,"context_line":"* It does not directly accept a goal or strategy. Those are defined by the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"eebbc780_65dd4eaf","line":98,"range":{"start_line":98,"start_character":2,"end_line":98,"end_character":14},"updated":"2026-10-13 11:26:14.000000000","message":"```suggestion\n* Unlike an Audit, an Audit Pipeline will not accept strategy ``input_parameters``\n```","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"ee3e08ff18140aaa3d31c6cd398557e166eea6d1","unresolved":false,"context_lines":[{"line_number":95,"context_line":"* It accepts a list of stage objects. Each stage references one Audit Template."},{"line_number":96,"context_line":"  The goal, strategy, scope, and parameters used by the stage are snapshotted"},{"line_number":97,"context_line":"  from that Audit Template when the pipeline is created."},{"line_number":98,"context_line":"* Unlike Audit, Audit Pipeline will not accept strategy ``input_parameters``"},{"line_number":99,"context_line":"  directly. Strategy parameters must be defined as ``default_parameters`` in"},{"line_number":100,"context_line":"  the Audit Template for each stage."},{"line_number":101,"context_line":"* It does not directly accept a goal or strategy. Those are defined by the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3adaa76b_e284742c","line":98,"range":{"start_line":98,"start_character":2,"end_line":98,"end_character":14},"in_reply_to":"eebbc780_65dd4eaf","updated":"2026-10-20 14:04:10.000000000","message":"Done","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"f65b81f594477181d88c09c0a90a8b01df36e785","unresolved":true,"context_lines":[{"line_number":275,"context_line":"Pipeline Planner normalises the per-stage indicators through a grouping"},{"line_number":276,"context_line":"layer before persisting them."},{"line_number":277,"context_line":""},{"line_number":278,"context_line":"A ``PipelineIndicatorGroup`` declares a set of source indicator names that"},{"line_number":279,"context_line":"are semantically equivalent and sums their values across all stage"},{"line_number":280,"context_line":"solutions into a single combined pipeline-level indicator.  The default"},{"line_number":281,"context_line":"groups are:"},{"line_number":282,"context_line":""},{"line_number":283,"context_line":"* ``pipeline_instance_migrations_count`` — aggregates"}],"source_content_type":"text/x-rst","patch_set":1,"id":"0a44657d_90c137d3","line":280,"range":{"start_line":278,"start_character":0,"end_line":280,"end_character":59},"updated":"2026-10-13 11:26:14.000000000","message":"is this the pre or post optimization count\n\ni.e. before any a-\u003eb b-\u003ec migrations are collapsed into a-\u003ec","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"b83c53d48b583482613b7f6d5b3d7634e6501677","unresolved":true,"context_lines":[{"line_number":275,"context_line":"Pipeline Planner normalises the per-stage indicators through a grouping"},{"line_number":276,"context_line":"layer before persisting them."},{"line_number":277,"context_line":""},{"line_number":278,"context_line":"A ``PipelineIndicatorGroup`` declares a set of source indicator names that"},{"line_number":279,"context_line":"are semantically equivalent and sums their values across all stage"},{"line_number":280,"context_line":"solutions into a single combined pipeline-level indicator.  The default"},{"line_number":281,"context_line":"groups are:"},{"line_number":282,"context_line":""},{"line_number":283,"context_line":"* ``pipeline_instance_migrations_count`` — aggregates"}],"source_content_type":"text/x-rst","patch_set":1,"id":"e72f6a08_1c8d8d51","line":280,"range":{"start_line":278,"start_character":0,"end_line":280,"end_character":59},"in_reply_to":"0a44657d_90c137d3","updated":"2026-10-15 12:12:41.000000000","message":"collapsing doesn\u0027t change the original indicadors, but the new grouping one can be updated after collapses, the amount of optimizations is also a new exclusive indicator from audit pipeline. I can update the spec (and code if needed) to be in sync with that.","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"e7db942439562662e22c1f2e92ea65ead4388cd1","unresolved":false,"context_lines":[{"line_number":275,"context_line":"Pipeline Planner normalises the per-stage indicators through a grouping"},{"line_number":276,"context_line":"layer before persisting them."},{"line_number":277,"context_line":""},{"line_number":278,"context_line":"A ``PipelineIndicatorGroup`` declares a set of source indicator names that"},{"line_number":279,"context_line":"are semantically equivalent and sums their values across all stage"},{"line_number":280,"context_line":"solutions into a single combined pipeline-level indicator.  The default"},{"line_number":281,"context_line":"groups are:"},{"line_number":282,"context_line":""},{"line_number":283,"context_line":"* ``pipeline_instance_migrations_count`` — aggregates"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7c4d9ba3_a6ea5f48","line":280,"range":{"start_line":278,"start_character":0,"end_line":280,"end_character":59},"in_reply_to":"e72f6a08_1c8d8d51","updated":"2026-10-27 18:31:30.000000000","message":"Acknowledged","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"f65b81f594477181d88c09c0a90a8b01df36e785","unresolved":true,"context_lines":[{"line_number":468,"context_line":"        strategy \u003d orm.relationship("},{"line_number":469,"context_line":"            Strategy, foreign_keys\u003dstrategy_id, lazy\u003dNone)"},{"line_number":470,"context_line":""},{"line_number":471,"context_line":"The stage stores a snapshot of the referenced Audit Template\u0027s goal, strategy,"},{"line_number":472,"context_line":"scope, and default parameters at pipeline creation time. Later edits or deletes"},{"line_number":473,"context_line":"of the Audit Template do not change existing pipelines. The source template"},{"line_number":474,"context_line":"reference is intentionally not stored because the Audit Template may be updated"},{"line_number":475,"context_line":"or deleted independently after the pipeline is created."},{"line_number":476,"context_line":""},{"line_number":477,"context_line":"``Action Plan Changes``"},{"line_number":478,"context_line":""},{"line_number":479,"context_line":"Update the existing ``ActionPlan`` model to make ``audit_id`` and"}],"source_content_type":"text/x-rst","patch_set":1,"id":"bf0df03b_6d05da4e","line":476,"range":{"start_line":471,"start_character":0,"end_line":476,"end_character":0},"updated":"2026-10-13 11:26:14.000000000","message":"we shoudl proably just snapshot the entire audit template includign its uuid as a json blob instead of cherry pickign filed.","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"3484e445f60401130f04182bc7b28353681bf4df","unresolved":true,"context_lines":[{"line_number":468,"context_line":"        strategy \u003d orm.relationship("},{"line_number":469,"context_line":"            Strategy, foreign_keys\u003dstrategy_id, lazy\u003dNone)"},{"line_number":470,"context_line":""},{"line_number":471,"context_line":"The stage stores a snapshot of the referenced Audit Template\u0027s goal, strategy,"},{"line_number":472,"context_line":"scope, and default parameters at pipeline creation time. Later edits or deletes"},{"line_number":473,"context_line":"of the Audit Template do not change existing pipelines. The source template"},{"line_number":474,"context_line":"reference is intentionally not stored because the Audit Template may be updated"},{"line_number":475,"context_line":"or deleted independently after the pipeline is created."},{"line_number":476,"context_line":""},{"line_number":477,"context_line":"``Action Plan Changes``"},{"line_number":478,"context_line":""},{"line_number":479,"context_line":"Update the existing ``ActionPlan`` model to make ``audit_id`` and"}],"source_content_type":"text/x-rst","patch_set":1,"id":"78215c62_20503855","line":476,"range":{"start_line":471,"start_character":0,"end_line":476,"end_character":0},"in_reply_to":"46f7f413_a87d3b5b","updated":"2026-10-23 12:16:10.000000000","message":"So yeah, fields for goal and strategy helps on filtering. Additional fields added to Strategies/Goals I believe that should be treated during DB upgrades. The missing piece are the json fields that we don\u0027t version today. I believe that we should then snapshot all parameters + a schema version (to help on upgrades?).\nLets see what @smooney@redhat.com has to say about that based on how Nova handle similar cases.","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":16312,"name":"Alfredo Moralejo","email":"amoralej@redhat.com","username":"amoralej"},"change_message_id":"ab1076eb6f69eb0286c87e2285d64c1791e7cd41","unresolved":true,"context_lines":[{"line_number":468,"context_line":"        strategy \u003d orm.relationship("},{"line_number":469,"context_line":"            Strategy, foreign_keys\u003dstrategy_id, lazy\u003dNone)"},{"line_number":470,"context_line":""},{"line_number":471,"context_line":"The stage stores a snapshot of the referenced Audit Template\u0027s goal, strategy,"},{"line_number":472,"context_line":"scope, and default parameters at pipeline creation time. Later edits or deletes"},{"line_number":473,"context_line":"of the Audit Template do not change existing pipelines. The source template"},{"line_number":474,"context_line":"reference is intentionally not stored because the Audit Template may be updated"},{"line_number":475,"context_line":"or deleted independently after the pipeline is created."},{"line_number":476,"context_line":""},{"line_number":477,"context_line":"``Action Plan Changes``"},{"line_number":478,"context_line":""},{"line_number":479,"context_line":"Update the existing ``ActionPlan`` model to make ``audit_id`` and"}],"source_content_type":"text/x-rst","patch_set":1,"id":"46f7f413_a87d3b5b","line":476,"range":{"start_line":471,"start_character":0,"end_line":476,"end_character":0},"in_reply_to":"4de883ee_0bb6a9b4","updated":"2026-10-23 10:04:36.000000000","message":"We discussed to change Audit object to have a json snapshot of the object as part of the new behavior on upgrades so i think it\u0027s good to discuss what is better (as i will also need to cover the auditpipelines in the upgrade. My understanding was that having it as a full snapshot would help to have a full picture of how the object Audit or AuditPipeline was created including some form of version of strategies specification that can be used later for online data migrations if needed. Said that, i understand we still want to have separated fields for some information so that we can easily filter by them in the db queries, as uuids of the different elements, etc... although that may end up in duplicated information in db columns and json snapshots.\n\n@smooney@redhat.com may you give some additional details on the advantadges of full object snapshot vs json snapshot only for parameters and the best way to use each field?","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"9f15d22914de37bacdb9a5eaa23f9ba75330988e","unresolved":true,"context_lines":[{"line_number":468,"context_line":"        strategy \u003d orm.relationship("},{"line_number":469,"context_line":"            Strategy, foreign_keys\u003dstrategy_id, lazy\u003dNone)"},{"line_number":470,"context_line":""},{"line_number":471,"context_line":"The stage stores a snapshot of the referenced Audit Template\u0027s goal, strategy,"},{"line_number":472,"context_line":"scope, and default parameters at pipeline creation time. Later edits or deletes"},{"line_number":473,"context_line":"of the Audit Template do not change existing pipelines. The source template"},{"line_number":474,"context_line":"reference is intentionally not stored because the Audit Template may be updated"},{"line_number":475,"context_line":"or deleted independently after the pipeline is created."},{"line_number":476,"context_line":""},{"line_number":477,"context_line":"``Action Plan Changes``"},{"line_number":478,"context_line":""},{"line_number":479,"context_line":"Update the existing ``ActionPlan`` model to make ``audit_id`` and"}],"source_content_type":"text/x-rst","patch_set":1,"id":"0fcbad8d_949e9f95","line":476,"range":{"start_line":471,"start_character":0,"end_line":476,"end_character":0},"in_reply_to":"72962c8b_71077be3","updated":"2026-10-27 19:21:29.000000000","message":"Ack, so IIUC it is fine to keep the individual fields (goal and strategy) for filtering stages, but we would likely save the entire audit template object too (which would include parameters and scope). That would replace this \"parameters\" and \"scope\" here, as also in existing objects. We can discuss this and hold the implementation for a while. Or merge as is and then do the DB migrations (considering that this implementation has only ONESHOT type, i don\u0027t think that will impact in migrations during upgrades)","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"e7db942439562662e22c1f2e92ea65ead4388cd1","unresolved":true,"context_lines":[{"line_number":468,"context_line":"        strategy \u003d orm.relationship("},{"line_number":469,"context_line":"            Strategy, foreign_keys\u003dstrategy_id, lazy\u003dNone)"},{"line_number":470,"context_line":""},{"line_number":471,"context_line":"The stage stores a snapshot of the referenced Audit Template\u0027s goal, strategy,"},{"line_number":472,"context_line":"scope, and default parameters at pipeline creation time. Later edits or deletes"},{"line_number":473,"context_line":"of the Audit Template do not change existing pipelines. The source template"},{"line_number":474,"context_line":"reference is intentionally not stored because the Audit Template may be updated"},{"line_number":475,"context_line":"or deleted independently after the pipeline is created."},{"line_number":476,"context_line":""},{"line_number":477,"context_line":"``Action Plan Changes``"},{"line_number":478,"context_line":""},{"line_number":479,"context_line":"Update the existing ``ActionPlan`` model to make ``audit_id`` and"}],"source_content_type":"text/x-rst","patch_set":1,"id":"72962c8b_71077be3","line":476,"range":{"start_line":471,"start_character":0,"end_line":476,"end_character":0},"in_reply_to":"78215c62_20503855","updated":"2026-10-27 18:31:30.000000000","message":"its more a case of gettign the serisation format for free.\nif we save the full ovo then it handels the versioning for us on load form the db and saving\n\nif we take a subset we need to maintian supprot for constucting and migrating the partail obejcts.\n\n\nthe case for this in nova is the flavor wherew we snapshto the flavor object and save the fully ting in a blob\n\nthe counter point for thisis the image where we save each image property as its onw keyvalue apir in the isntance_system_metadta table as a triple\ninstance_uuid,key,value.\n\nboth work and both have there tradeoffs.","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"ee3e08ff18140aaa3d31c6cd398557e166eea6d1","unresolved":true,"context_lines":[{"line_number":468,"context_line":"        strategy \u003d orm.relationship("},{"line_number":469,"context_line":"            Strategy, foreign_keys\u003dstrategy_id, lazy\u003dNone)"},{"line_number":470,"context_line":""},{"line_number":471,"context_line":"The stage stores a snapshot of the referenced Audit Template\u0027s goal, strategy,"},{"line_number":472,"context_line":"scope, and default parameters at pipeline creation time. Later edits or deletes"},{"line_number":473,"context_line":"of the Audit Template do not change existing pipelines. The source template"},{"line_number":474,"context_line":"reference is intentionally not stored because the Audit Template may be updated"},{"line_number":475,"context_line":"or deleted independently after the pipeline is created."},{"line_number":476,"context_line":""},{"line_number":477,"context_line":"``Action Plan Changes``"},{"line_number":478,"context_line":""},{"line_number":479,"context_line":"Update the existing ``ActionPlan`` model to make ``audit_id`` and"}],"source_content_type":"text/x-rst","patch_set":1,"id":"4de883ee_0bb6a9b4","line":476,"range":{"start_line":471,"start_character":0,"end_line":476,"end_character":0},"in_reply_to":"bf0df03b_6d05da4e","updated":"2026-10-20 14:04:10.000000000","message":"They are proposed as inidividual fields, similar to an Audit object today, with the additions of audit_pipeline reference and its position in the pipeline.","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"f65b81f594477181d88c09c0a90a8b01df36e785","unresolved":true,"context_lines":[{"line_number":543,"context_line":"        \"name\": \"maintenance-pipeline\","},{"line_number":544,"context_line":"        \"audit_type\": \"ONESHOT\","},{"line_number":545,"context_line":"        \"execution_mode\": \"CASCADE\","},{"line_number":546,"context_line":"        \"auto_trigger\": false,"},{"line_number":547,"context_line":"        \"stages\": ["},{"line_number":548,"context_line":"            {"},{"line_number":549,"context_line":"                \"name\": \"maintenance\","}],"source_content_type":"text/x-rst","patch_set":1,"id":"09c038ab_30e2bd6c","line":546,"updated":"2026-10-13 11:26:14.000000000","message":"should we also have a description at the pipeline level","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"b83c53d48b583482613b7f6d5b3d7634e6501677","unresolved":true,"context_lines":[{"line_number":543,"context_line":"        \"name\": \"maintenance-pipeline\","},{"line_number":544,"context_line":"        \"audit_type\": \"ONESHOT\","},{"line_number":545,"context_line":"        \"execution_mode\": \"CASCADE\","},{"line_number":546,"context_line":"        \"auto_trigger\": false,"},{"line_number":547,"context_line":"        \"stages\": ["},{"line_number":548,"context_line":"            {"},{"line_number":549,"context_line":"                \"name\": \"maintenance\","}],"source_content_type":"text/x-rst","patch_set":1,"id":"2f0aa8e2_a88410de","line":546,"in_reply_to":"09c038ab_30e2bd6c","updated":"2026-10-15 12:12:41.000000000","message":"ack, can be added yes","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"ee3e08ff18140aaa3d31c6cd398557e166eea6d1","unresolved":false,"context_lines":[{"line_number":543,"context_line":"        \"name\": \"maintenance-pipeline\","},{"line_number":544,"context_line":"        \"audit_type\": \"ONESHOT\","},{"line_number":545,"context_line":"        \"execution_mode\": \"CASCADE\","},{"line_number":546,"context_line":"        \"auto_trigger\": false,"},{"line_number":547,"context_line":"        \"stages\": ["},{"line_number":548,"context_line":"            {"},{"line_number":549,"context_line":"                \"name\": \"maintenance\","}],"source_content_type":"text/x-rst","patch_set":1,"id":"bde53ed3_d18eb967","line":546,"in_reply_to":"2f0aa8e2_a88410de","updated":"2026-10-20 14:04:10.000000000","message":"Done","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"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":"6d61fc65426bb9cd4b133a57eabb29d73f9a1f77","unresolved":false,"context_lines":[{"line_number":585,"context_line":"        \"audit_type\": \"ONESHOT\","},{"line_number":586,"context_line":"        \"execution_mode\": \"CASCADE\","},{"line_number":587,"context_line":"        \"state\": \"PENDING\","},{"line_number":588,"context_line":"        \"auto_trigger\": true,"},{"line_number":589,"context_line":"        \"hostname\": null,"},{"line_number":590,"context_line":"        \"status_message\": null,"},{"line_number":591,"context_line":"        \"stage_uuids\": [\"stage-uuid-1\", \"stage-uuid-2\"],"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a1485bb_011ee404","line":588,"updated":"2026-09-10 18:03:53.000000000","message":"The create example request body sets \"auto_trigger\": false and the prose says the field defaults to false, but the corresponding response body example returns \"auto_trigger\": true. The two examples describe the same request/response pair and must agree.\n\n**Severity**: SUGGESTION | **Confidence**: 0.9\n\n**Impact**: API sample tests and client bindings modelled on this example would encode the wrong value, and readers cannot tell what the API actually returns for the example request.\n\n**Recommendation**:\nChange the response example to \"auto_trigger\": false so it matches the request example and the documented default.","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"ee3e08ff18140aaa3d31c6cd398557e166eea6d1","unresolved":false,"context_lines":[{"line_number":585,"context_line":"        \"audit_type\": \"ONESHOT\","},{"line_number":586,"context_line":"        \"execution_mode\": \"CASCADE\","},{"line_number":587,"context_line":"        \"state\": \"PENDING\","},{"line_number":588,"context_line":"        \"auto_trigger\": true,"},{"line_number":589,"context_line":"        \"hostname\": null,"},{"line_number":590,"context_line":"        \"status_message\": null,"},{"line_number":591,"context_line":"        \"stage_uuids\": [\"stage-uuid-1\", \"stage-uuid-2\"],"}],"source_content_type":"text/x-rst","patch_set":1,"id":"d446b622_219cd93d","line":588,"in_reply_to":"3a1485bb_011ee404","updated":"2026-10-20 14:04:10.000000000","message":"fixed","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"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":"6d61fc65426bb9cd4b133a57eabb29d73f9a1f77","unresolved":false,"context_lines":[{"line_number":679,"context_line":"* Normal response: 200 OK"},{"line_number":680,"context_line":"* Error responses: 400 Bad Request, 404 Not Found, 409 Conflict"},{"line_number":681,"context_line":""},{"line_number":682,"context_line":"PUT updates the mutable user fields and is allowed only while the pipeline is"},{"line_number":683,"context_line":"in ``PENDING`` state. The mutable pipeline fields are ``name`` and"},{"line_number":684,"context_line":"``auto_trigger``; both are optional in the request body and only the supplied"},{"line_number":685,"context_line":"fields are changed. All other fields, including stage fields, are immutable."}],"source_content_type":"text/x-rst","patch_set":1,"id":"c11840b6_12b904c4","line":682,"updated":"2026-09-10 18:03:53.000000000","message":"The spec states ONESHOT pipelines are triggered automatically by the API at creation time, so a pipeline leaves PENDING almost immediately after create returns. Yet the update API is defined as allowed only while the pipeline is in PENDING state. In the initial microversion only ONESHOT pipelines exist, so the update endpoint can only succeed in a narrow asynchronous window. The 2026.2 version of this spec had an explicit /start action endpoint that this revision removes, eliminating the operator\u0027s only way to control when planning starts.\n\n**Severity**: WARNING | **Confidence**: 0.85\n\n**Impact**: Implementers following this spec would ship an update endpoint that effectively always returns 409 Conflict in real deployments, and operators would have no documented way to change auto_trigger before the final Action Plan launch decision.\n\n**Suggestion**:\nReconcile the lifecycle: keep pipelines PENDING until explicitly started (restore a start/trigger action), or allow updating auto_trigger while ONGOING until the final Action Plan is persisted, and document the usable update window explicitly.","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"ee3e08ff18140aaa3d31c6cd398557e166eea6d1","unresolved":false,"context_lines":[{"line_number":679,"context_line":"* Normal response: 200 OK"},{"line_number":680,"context_line":"* Error responses: 400 Bad Request, 404 Not Found, 409 Conflict"},{"line_number":681,"context_line":""},{"line_number":682,"context_line":"PUT updates the mutable user fields and is allowed only while the pipeline is"},{"line_number":683,"context_line":"in ``PENDING`` state. The mutable pipeline fields are ``name`` and"},{"line_number":684,"context_line":"``auto_trigger``; both are optional in the request body and only the supplied"},{"line_number":685,"context_line":"fields are changed. All other fields, including stage fields, are immutable."}],"source_content_type":"text/x-rst","patch_set":1,"id":"556ad74c_4aa0bef8","line":682,"in_reply_to":"a9d1d7ac_f2122b77","updated":"2026-10-20 14:04:10.000000000","message":"Ack, makes sense and that would allow users to rename them at any time (and reuse the name in other audit pipelines)","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"f65b81f594477181d88c09c0a90a8b01df36e785","unresolved":true,"context_lines":[{"line_number":679,"context_line":"* Normal response: 200 OK"},{"line_number":680,"context_line":"* Error responses: 400 Bad Request, 404 Not Found, 409 Conflict"},{"line_number":681,"context_line":""},{"line_number":682,"context_line":"PUT updates the mutable user fields and is allowed only while the pipeline is"},{"line_number":683,"context_line":"in ``PENDING`` state. The mutable pipeline fields are ``name`` and"},{"line_number":684,"context_line":"``auto_trigger``; both are optional in the request body and only the supplied"},{"line_number":685,"context_line":"fields are changed. All other fields, including stage fields, are immutable."}],"source_content_type":"text/x-rst","patch_set":1,"id":"a9d1d7ac_f2122b77","line":682,"in_reply_to":"c11840b6_12b904c4","updated":"2026-10-13 11:26:14.000000000","message":"gpt-6.1-sol agrees\n\ni think for now the only mutations we want to allwo are the name.descrption and or auto_trigger.\n\nwe likely want to allow mutaton of those at any point priort to the creation/execution fo the action plan\n\nwe could allow the name to be updated at any point same for dsecription if we add it\n\nauto trigger only makes sense in my view to chagne if a plan has not been created since its a oneshot pipeline. changign ti for event based and or continous culd make sense but setting auto_trigger should not run an already produced plan","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"f65b81f594477181d88c09c0a90a8b01df36e785","unresolved":true,"context_lines":[{"line_number":695,"context_line":"* Error responses: 404 Not Found, 409 Conflict"},{"line_number":696,"context_line":""},{"line_number":697,"context_line":"Cancel is valid for ``PENDING`` and ``ONGOING`` pipelines and returns the"},{"line_number":698,"context_line":"updated pipeline representation. It moves the pipeline to ``CANCELLED``"},{"line_number":699,"context_line":"directly; for an ``ONGOING`` pipeline that persisted state is the cancellation"},{"line_number":700,"context_line":"request. The Pipeline Handler checks for it between stages and before"},{"line_number":701,"context_line":"persisting the final Action Plan, so the currently running strategy is not"},{"line_number":702,"context_line":"interrupted. Cancelling a pipeline already in the terminal ``SUCCEEDED`` or"},{"line_number":703,"context_line":"``FAILED`` state returns ``409 Conflict``."}],"source_content_type":"text/x-rst","patch_set":1,"id":"638d761e_d7a5aae4","line":700,"range":{"start_line":698,"start_character":33,"end_line":700,"end_character":9},"updated":"2026-10-13 11:26:14.000000000","message":"since we can delete form the cacneled state i am not sure this is safe\n\ni think we need a new `CANCELING` state and only move to `CANCELLED` when the applier has a actully cancled the execution of the action plan.\n\notherwise there could be races.","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"ee3e08ff18140aaa3d31c6cd398557e166eea6d1","unresolved":true,"context_lines":[{"line_number":695,"context_line":"* Error responses: 404 Not Found, 409 Conflict"},{"line_number":696,"context_line":""},{"line_number":697,"context_line":"Cancel is valid for ``PENDING`` and ``ONGOING`` pipelines and returns the"},{"line_number":698,"context_line":"updated pipeline representation. It moves the pipeline to ``CANCELLED``"},{"line_number":699,"context_line":"directly; for an ``ONGOING`` pipeline that persisted state is the cancellation"},{"line_number":700,"context_line":"request. The Pipeline Handler checks for it between stages and before"},{"line_number":701,"context_line":"persisting the final Action Plan, so the currently running strategy is not"},{"line_number":702,"context_line":"interrupted. Cancelling a pipeline already in the terminal ``SUCCEEDED`` or"},{"line_number":703,"context_line":"``FAILED`` state returns ``409 Conflict``."}],"source_content_type":"text/x-rst","patch_set":1,"id":"2df9f3d8_e1888fa7","line":700,"range":{"start_line":698,"start_character":33,"end_line":700,"end_character":9},"in_reply_to":"138739fd_75ab7987","updated":"2026-10-20 14:04:10.000000000","message":"New PatchSet is adding a CANCELLING state, which is moved from ONGOING. PENDING audits coudl still be move directly to CANCELLED.","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"e7db942439562662e22c1f2e92ea65ead4388cd1","unresolved":false,"context_lines":[{"line_number":695,"context_line":"* Error responses: 404 Not Found, 409 Conflict"},{"line_number":696,"context_line":""},{"line_number":697,"context_line":"Cancel is valid for ``PENDING`` and ``ONGOING`` pipelines and returns the"},{"line_number":698,"context_line":"updated pipeline representation. It moves the pipeline to ``CANCELLED``"},{"line_number":699,"context_line":"directly; for an ``ONGOING`` pipeline that persisted state is the cancellation"},{"line_number":700,"context_line":"request. The Pipeline Handler checks for it between stages and before"},{"line_number":701,"context_line":"persisting the final Action Plan, so the currently running strategy is not"},{"line_number":702,"context_line":"interrupted. Cancelling a pipeline already in the terminal ``SUCCEEDED`` or"},{"line_number":703,"context_line":"``FAILED`` state returns ``409 Conflict``."}],"source_content_type":"text/x-rst","patch_set":1,"id":"2ef7cabd_fd5aa791","line":700,"range":{"start_line":698,"start_character":33,"end_line":700,"end_character":9},"in_reply_to":"2df9f3d8_e1888fa7","updated":"2026-10-27 18:31:30.000000000","message":"Acknowledged","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"b83c53d48b583482613b7f6d5b3d7634e6501677","unresolved":true,"context_lines":[{"line_number":695,"context_line":"* Error responses: 404 Not Found, 409 Conflict"},{"line_number":696,"context_line":""},{"line_number":697,"context_line":"Cancel is valid for ``PENDING`` and ``ONGOING`` pipelines and returns the"},{"line_number":698,"context_line":"updated pipeline representation. It moves the pipeline to ``CANCELLED``"},{"line_number":699,"context_line":"directly; for an ``ONGOING`` pipeline that persisted state is the cancellation"},{"line_number":700,"context_line":"request. The Pipeline Handler checks for it between stages and before"},{"line_number":701,"context_line":"persisting the final Action Plan, so the currently running strategy is not"},{"line_number":702,"context_line":"interrupted. Cancelling a pipeline already in the terminal ``SUCCEEDED`` or"},{"line_number":703,"context_line":"``FAILED`` state returns ``409 Conflict``."}],"source_content_type":"text/x-rst","patch_set":1,"id":"138739fd_75ab7987","line":700,"range":{"start_line":698,"start_character":33,"end_line":700,"end_character":9},"in_reply_to":"638d761e_d7a5aae4","updated":"2026-10-15 12:12:41.000000000","message":"We can discuss at the ptg and upadate the spec based on conclusions..","commit_id":"a9ca593b1246116a906090080d133834d6e2d1f6"},{"author":{"_account_id":16312,"name":"Alfredo Moralejo","email":"amoralej@redhat.com","username":"amoralej"},"change_message_id":"901611730355173131511f8e43a1c07d5f83d469","unresolved":true,"context_lines":[{"line_number":95,"context_line":"``CANCELLING`` is an intermediate cancellation state for pipelines that are"},{"line_number":96,"context_line":"already ``ONGOING``. When a cancel request arrives for an ``ONGOING`` pipeline,"},{"line_number":97,"context_line":"the state is set to ``CANCELLING`` and the Pipeline Handler detects this"},{"line_number":98,"context_line":"between stages, aborts the remaining stages without interrupting the strategy"},{"line_number":99,"context_line":"that is currently executing, and then sets the pipeline to ``CANCELLED``. A"},{"line_number":100,"context_line":"``PENDING`` pipeline is moved directly to ``CANCELLED`` without passing through"},{"line_number":101,"context_line":"``CANCELLING`` because no strategy is executing."},{"line_number":102,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"85d18ad0_daf87a4d","line":99,"range":{"start_line":98,"start_character":23,"end_line":99,"end_character":71},"updated":"2026-10-20 15:43:15.000000000","message":"We can discuss some details in the implementaion, i.e. we should catch the status when running the planner phase in case CANCELLING status is set when running the last stage.","commit_id":"14de18fe39745ab25cc43fd357e079896cd479c7"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"b13912017f5d80eafed5c0d0a82d5b548d406c95","unresolved":true,"context_lines":[{"line_number":95,"context_line":"``CANCELLING`` is an intermediate cancellation state for pipelines that are"},{"line_number":96,"context_line":"already ``ONGOING``. When a cancel request arrives for an ``ONGOING`` pipeline,"},{"line_number":97,"context_line":"the state is set to ``CANCELLING`` and the Pipeline Handler detects this"},{"line_number":98,"context_line":"between stages, aborts the remaining stages without interrupting the strategy"},{"line_number":99,"context_line":"that is currently executing, and then sets the pipeline to ``CANCELLED``. A"},{"line_number":100,"context_line":"``PENDING`` pipeline is moved directly to ``CANCELLED`` without passing through"},{"line_number":101,"context_line":"``CANCELLING`` because no strategy is executing."},{"line_number":102,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"d6be2524_f7ab960a","line":99,"range":{"start_line":98,"start_character":23,"end_line":99,"end_character":71},"in_reply_to":"85d18ad0_daf87a4d","updated":"2026-10-20 18:04:38.000000000","message":"Yes, we can check before and after calling the planner too, but I think that we can circle back in the implementation yes.","commit_id":"14de18fe39745ab25cc43fd357e079896cd479c7"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"e7db942439562662e22c1f2e92ea65ead4388cd1","unresolved":true,"context_lines":[{"line_number":95,"context_line":"``CANCELLING`` is an intermediate cancellation state for pipelines that are"},{"line_number":96,"context_line":"already ``ONGOING``. When a cancel request arrives for an ``ONGOING`` pipeline,"},{"line_number":97,"context_line":"the state is set to ``CANCELLING`` and the Pipeline Handler detects this"},{"line_number":98,"context_line":"between stages, aborts the remaining stages without interrupting the strategy"},{"line_number":99,"context_line":"that is currently executing, and then sets the pipeline to ``CANCELLED``. A"},{"line_number":100,"context_line":"``PENDING`` pipeline is moved directly to ``CANCELLED`` without passing through"},{"line_number":101,"context_line":"``CANCELLING`` because no strategy is executing."},{"line_number":102,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"2e00ac99_8ac170bd","line":99,"range":{"start_line":98,"start_character":23,"end_line":99,"end_character":71},"in_reply_to":"d6be2524_f7ab960a","updated":"2026-10-27 18:31:30.000000000","message":"thats an interesting edgecase.\n\ni woudl sltill proably set the action plan to cancleed rather then succeded but i would expect all the actions in the plan to reflect there actual outcome.\n\nwhen we eventually supprot Continuous Pipeliens we want the behvior to work for that too so we woudl not want to trigger it again in the next interval so the pipleine at least i think need to end up in cancled.\n\nthe action plan could end up in succeeded or failed (depending on the actions statuss) or canceled (indepenent of the action status) and wither woudl be consitent","commit_id":"14de18fe39745ab25cc43fd357e079896cd479c7"},{"author":{"_account_id":16312,"name":"Alfredo Moralejo","email":"amoralej@redhat.com","username":"amoralej"},"change_message_id":"901611730355173131511f8e43a1c07d5f83d469","unresolved":true,"context_lines":[{"line_number":161,"context_line":"after the final Action Plan is generated. The CDM is not persisted and is not"},{"line_number":162,"context_line":"reused by any other pipeline execution."},{"line_number":163,"context_line":""},{"line_number":164,"context_line":"The simulation layer must preserve constraints introduced by earlier stages."},{"line_number":165,"context_line":"For example, if a host-maintenance stage requires instances to leave a"},{"line_number":166,"context_line":"maintenance host, later stages must not move those instances back to that host"},{"line_number":167,"context_line":"or eliminate the required migration. The simulation layer will mark such hosts"},{"line_number":168,"context_line":"or actions as constrained so that later stages and the Pipeline Planner can"},{"line_number":169,"context_line":"distinguish required moves from collapsible optimization moves."},{"line_number":170,"context_line":""},{"line_number":171,"context_line":"Metric Data Cache"},{"line_number":172,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5c5afd4a_e4a2ad58","line":169,"range":{"start_line":164,"start_character":26,"end_line":169,"end_character":62},"updated":"2026-10-20 15:43:15.000000000","message":"How this would work? For the explained case, i.e., disabling the node in the first stage should avoid the second sending it back to  the node in maintenance. Do we need something else? otherwise, how the similation layer mark the second stage to \"not undo\" this migration?","commit_id":"14de18fe39745ab25cc43fd357e079896cd479c7"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"b13912017f5d80eafed5c0d0a82d5b548d406c95","unresolved":true,"context_lines":[{"line_number":161,"context_line":"after the final Action Plan is generated. The CDM is not persisted and is not"},{"line_number":162,"context_line":"reused by any other pipeline execution."},{"line_number":163,"context_line":""},{"line_number":164,"context_line":"The simulation layer must preserve constraints introduced by earlier stages."},{"line_number":165,"context_line":"For example, if a host-maintenance stage requires instances to leave a"},{"line_number":166,"context_line":"maintenance host, later stages must not move those instances back to that host"},{"line_number":167,"context_line":"or eliminate the required migration. The simulation layer will mark such hosts"},{"line_number":168,"context_line":"or actions as constrained so that later stages and the Pipeline Planner can"},{"line_number":169,"context_line":"distinguish required moves from collapsible optimization moves."},{"line_number":170,"context_line":""},{"line_number":171,"context_line":"Metric Data Cache"},{"line_number":172,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"355edfaf_dd5fc7a4","line":169,"range":{"start_line":164,"start_character":26,"end_line":169,"end_character":62},"in_reply_to":"5c5afd4a_e4a2ad58","updated":"2026-10-20 18:04:38.000000000","message":"You are correct, the CDM/Metric simulation will not do anything in addition to the proposed solution\u0027s actions. So if a node is goint to maintenance, it should include a disabling node action, which will update the node state in the CDM. This part needs to be changed. Some strategies that currently don\u0027t disable de source node may have the instances moved back by other strategies (e.g zone_migration + workload_balance) - this can be properly documented in the end, but not fixed in the Pipeline.","commit_id":"14de18fe39745ab25cc43fd357e079896cd479c7"},{"author":{"_account_id":34452,"name":"Joan Gilabert","display_name":"jgilaber","email":"jgilaber@redhat.com","username":"jgilaber"},"change_message_id":"fd119a896a5643180f33233a75a9aa889aafbeb5","unresolved":true,"context_lines":[{"line_number":92,"context_line":"pipelines is out of scope until recurring CONTINUOUS or EVENT pipelines are"},{"line_number":93,"context_line":"supported."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"``CANCELLING`` is an intermediate cancellation state for pipelines that are"},{"line_number":96,"context_line":"already ``ONGOING``. When a cancel request arrives for an ``ONGOING`` pipeline,"},{"line_number":97,"context_line":"the state is set to ``CANCELLING`` and the Pipeline Handler detects this"},{"line_number":98,"context_line":"between stages, aborts the remaining stages without interrupting the strategy"}],"source_content_type":"text/x-rst","patch_set":3,"id":"d0e892f1_e9459832","line":95,"updated":"2026-10-30 13:52:46.000000000","message":"will we introduce CANCELING for audits as well or nonly for pipeline audits?","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"7e05061d90fd873dd537fe275327c3afcb9ef2ec","unresolved":true,"context_lines":[{"line_number":92,"context_line":"pipelines is out of scope until recurring CONTINUOUS or EVENT pipelines are"},{"line_number":93,"context_line":"supported."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"``CANCELLING`` is an intermediate cancellation state for pipelines that are"},{"line_number":96,"context_line":"already ``ONGOING``. When a cancel request arrives for an ``ONGOING`` pipeline,"},{"line_number":97,"context_line":"the state is set to ``CANCELLING`` and the Pipeline Handler detects this"},{"line_number":98,"context_line":"between stages, aborts the remaining stages without interrupting the strategy"}],"source_content_type":"text/x-rst","patch_set":3,"id":"66c24c76_148ebe9f","line":95,"in_reply_to":"44115fdb_bde25f3b","updated":"2026-11-04 13:05:25.000000000","message":"yeah right, that line was there before adding CANCELLING yeah, I may update it if needed a new PS.\nI have registered a new blueprint for Audit:\nhttps://blueprints.launchpad.net/watcher/+spec/audit-cancelling-state\nWhich may need to have more than one change, so it is good to track there.","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"},{"author":{"_account_id":34452,"name":"Joan Gilabert","display_name":"jgilaber","email":"jgilaber@redhat.com","username":"jgilaber"},"change_message_id":"31e194f5505f09b33dd784076fe85e40a50a0cf3","unresolved":true,"context_lines":[{"line_number":92,"context_line":"pipelines is out of scope until recurring CONTINUOUS or EVENT pipelines are"},{"line_number":93,"context_line":"supported."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"``CANCELLING`` is an intermediate cancellation state for pipelines that are"},{"line_number":96,"context_line":"already ``ONGOING``. When a cancel request arrives for an ``ONGOING`` pipeline,"},{"line_number":97,"context_line":"the state is set to ``CANCELLING`` and the Pipeline Handler detects this"},{"line_number":98,"context_line":"between stages, aborts the remaining stages without interrupting the strategy"}],"source_content_type":"text/x-rst","patch_set":3,"id":"44115fdb_bde25f3b","line":95,"in_reply_to":"a0f8a2ea_474c7f27","updated":"2026-11-04 12:40:06.000000000","message":"that makes sense to me, but I wasn\u0027t sure since line 80 states that `The Audit Pipeline state machine will reuse the existing Audit states`, but the listed transitions are different from the existing audit ones. If we need to update the spec it might be good to remark that the audit change would be separate and out of the scope of the spec.","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"6b237e06b44bb29ec094786a00062280b4b9230a","unresolved":true,"context_lines":[{"line_number":92,"context_line":"pipelines is out of scope until recurring CONTINUOUS or EVENT pipelines are"},{"line_number":93,"context_line":"supported."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"``CANCELLING`` is an intermediate cancellation state for pipelines that are"},{"line_number":96,"context_line":"already ``ONGOING``. When a cancel request arrives for an ``ONGOING`` pipeline,"},{"line_number":97,"context_line":"the state is set to ``CANCELLING`` and the Pipeline Handler detects this"},{"line_number":98,"context_line":"between stages, aborts the remaining stages without interrupting the strategy"}],"source_content_type":"text/x-rst","patch_set":3,"id":"a0f8a2ea_474c7f27","line":95,"in_reply_to":"d0e892f1_e9459832","updated":"2026-10-30 14:00:15.000000000","message":"In this spec only for Audit Pipelines.\nWe may want to create a LP Bug or a blueprint to track the Audit part, since it needs to be in a different patch imho","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"e7db942439562662e22c1f2e92ea65ead4388cd1","unresolved":true,"context_lines":[{"line_number":200,"context_line":""},{"line_number":201,"context_line":"This approach keeps the strategy interface unchanged and makes caching"},{"line_number":202,"context_line":"transparent to both existing and future strategies. The same mechanism applies"},{"line_number":203,"context_line":"to normal Audits, where the cache acts as a lightweight per-audit cache."},{"line_number":204,"context_line":""},{"line_number":205,"context_line":"Strategy Execution Context"},{"line_number":206,"context_line":"--------------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3aa0e0bc_c355ebf1","line":203,"updated":"2026-10-27 18:31:30.000000000","message":"so since this was implemented last cycele we shoud leither remove this section entrily or shorten it and declare it done\n\nhttps://github.com/openstack/watcher/commit/e8c70fc23210522c93f6fbc8e54771a66333875d","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"9f15d22914de37bacdb9a5eaa23f9ba75330988e","unresolved":true,"context_lines":[{"line_number":200,"context_line":""},{"line_number":201,"context_line":"This approach keeps the strategy interface unchanged and makes caching"},{"line_number":202,"context_line":"transparent to both existing and future strategies. The same mechanism applies"},{"line_number":203,"context_line":"to normal Audits, where the cache acts as a lightweight per-audit cache."},{"line_number":204,"context_line":""},{"line_number":205,"context_line":"Strategy Execution Context"},{"line_number":206,"context_line":"--------------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"a4c99d95_bf835f76","line":203,"in_reply_to":"3aa0e0bc_c355ebf1","updated":"2026-10-27 19:21:29.000000000","message":"Correct, that was merged in previous cycle already. We can just mention that the imlementation relies on that.","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"},{"author":{"_account_id":16312,"name":"Alfredo Moralejo","email":"amoralej@redhat.com","username":"amoralej"},"change_message_id":"fb96fc9e5646066c2bad07818a70afa5098d46e8","unresolved":true,"context_lines":[{"line_number":307,"context_line":"  ``released_compute_nodes_count``."},{"line_number":308,"context_line":"* ``pipeline_volume_migrations_count`` — aggregates"},{"line_number":309,"context_line":"  ``planned_volume_migrate_count``."},{"line_number":310,"context_line":""},{"line_number":311,"context_line":"The combined indicators are stored as ``EfficacyIndicator`` rows linked to"},{"line_number":312,"context_line":"the Action Plan, using the existing data model without requiring new"},{"line_number":313,"context_line":"database columns or per-stage storage."},{"line_number":314,"context_line":""},{"line_number":315,"context_line":"Additionally, when the pipeline optimiser collapses or removes redundant"},{"line_number":316,"context_line":"migration chains, the number of eliminated migrations is recorded in the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"b0e76788_eca0e400","line":313,"range":{"start_line":310,"start_character":1,"end_line":313,"end_character":38},"updated":"2026-10-23 11:22:10.000000000","message":"The per-strategy indicator which are not aggregated via PipelineIndicatorGroup, will be also added as efficacy indicators?. i.e. we have a zone_migrate + workload_stabilization, the efficacy indicators standard_deviation_after_audit and standard_deviation_before_audit should be displayed?","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"e7db942439562662e22c1f2e92ea65ead4388cd1","unresolved":true,"context_lines":[{"line_number":307,"context_line":"  ``released_compute_nodes_count``."},{"line_number":308,"context_line":"* ``pipeline_volume_migrations_count`` — aggregates"},{"line_number":309,"context_line":"  ``planned_volume_migrate_count``."},{"line_number":310,"context_line":""},{"line_number":311,"context_line":"The combined indicators are stored as ``EfficacyIndicator`` rows linked to"},{"line_number":312,"context_line":"the Action Plan, using the existing data model without requiring new"},{"line_number":313,"context_line":"database columns or per-stage storage."},{"line_number":314,"context_line":""},{"line_number":315,"context_line":"Additionally, when the pipeline optimiser collapses or removes redundant"},{"line_number":316,"context_line":"migration chains, the number of eliminated migrations is recorded in the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fc78dc31_551269db","line":313,"range":{"start_line":310,"start_character":1,"end_line":313,"end_character":38},"in_reply_to":"151219d7_7addd309","updated":"2026-10-27 18:31:30.000000000","message":"i think seperat form this effort we need to have an api chage that will normalise all the indcotro san ddefein what they shoudl be across all stragies.\n\nwe shoudl have only 1 indicator for any given action / goal regardless\nof the stragey used to get there.\n\nby teh way i dont really condire planned_volume_migrate_count to be an EfficacyIndicator\n\nif the intent was to move all the vms its binary\n\neither you move them all or you did not\n\nplanned_volume_migrate_count is only an EfficacyIndicator if you combine it with the number of vms moved and the two are nto the same.\n\neven thne if you can caludate it form counting the actions of a give type in the plan i dont think we shoudl be returnign them in the future.\n\nthe only real EfficacyIndicator we have in our stragies today is the standard devition before and after the audit\n\nhttps://docs.openstack.org/watcher/latest/strategies/workload-stabilization.html#efficacy-indicator\n\nthe effincy indicotors are ment to be a mesure of how close to the optimial state of a give goal we got.\n\n\nso if you did not incldue any indicator for the piples that woudl actully be an improvment form my perspectve then just inlcuing the counts as the count dont tell you anything about the efficly of the optimisation just how much work is needed to get there.","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"},{"author":{"_account_id":16312,"name":"Alfredo Moralejo","email":"amoralej@redhat.com","username":"amoralej"},"change_message_id":"42a5b1db349140a5f81a15aaac8cee0fd008c621","unresolved":true,"context_lines":[{"line_number":307,"context_line":"  ``released_compute_nodes_count``."},{"line_number":308,"context_line":"* ``pipeline_volume_migrations_count`` — aggregates"},{"line_number":309,"context_line":"  ``planned_volume_migrate_count``."},{"line_number":310,"context_line":""},{"line_number":311,"context_line":"The combined indicators are stored as ``EfficacyIndicator`` rows linked to"},{"line_number":312,"context_line":"the Action Plan, using the existing data model without requiring new"},{"line_number":313,"context_line":"database columns or per-stage storage."},{"line_number":314,"context_line":""},{"line_number":315,"context_line":"Additionally, when the pipeline optimiser collapses or removes redundant"},{"line_number":316,"context_line":"migration chains, the number of eliminated migrations is recorded in the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"151219d7_7addd309","line":313,"range":{"start_line":310,"start_character":1,"end_line":313,"end_character":38},"in_reply_to":"4ff87325_1268f688","updated":"2026-10-23 13:18:20.000000000","message":"ok, wfm. I agree in the current implementation of grouping/aggregation, my doubt is what to do with the indicators not included in those. I guess at some point we may need to change the api to have sometihng like efficacy_indicators.pipeline efficacy_indicators.stage and include in the stage ones the ones coming from each stage and not aggregated into pipeline level ones\n\nI think We can keep this initial one and defer the other one, although that will requiren new microversion i guess.","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"3484e445f60401130f04182bc7b28353681bf4df","unresolved":true,"context_lines":[{"line_number":307,"context_line":"  ``released_compute_nodes_count``."},{"line_number":308,"context_line":"* ``pipeline_volume_migrations_count`` — aggregates"},{"line_number":309,"context_line":"  ``planned_volume_migrate_count``."},{"line_number":310,"context_line":""},{"line_number":311,"context_line":"The combined indicators are stored as ``EfficacyIndicator`` rows linked to"},{"line_number":312,"context_line":"the Action Plan, using the existing data model without requiring new"},{"line_number":313,"context_line":"database columns or per-stage storage."},{"line_number":314,"context_line":""},{"line_number":315,"context_line":"Additionally, when the pipeline optimiser collapses or removes redundant"},{"line_number":316,"context_line":"migration chains, the number of eliminated migrations is recorded in the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"4ff87325_1268f688","line":313,"range":{"start_line":310,"start_character":1,"end_line":313,"end_character":38},"in_reply_to":"b0e76788_eca0e400","updated":"2026-10-23 12:16:10.000000000","message":"So this is one of the things that I intentionally removed. Today the Action Plan object store a list of EfficacyIndicators, which by themselves can\u0027t identify that belong to a specific strategy or pipeline stage. In order to provide that, the object would need to be extended and include that too, which I deffered here in the spec and in the implementation (but it is possible to add). The only thing that I don\u0027t agree, and which I removed from an initial implementation, was just adding all Indicators to the final Action Plan, since it was: 1) duplicating some migration infos and 2) showing a intermediate state (like a deviaton from a middle stage) which don\u0027t represent the final value. \nSo in order to implement that, we would need to extend the Indicator, or extend the Action Plan to include indicators per stage. I think that the later would be the best option since Strategies need to know about Indicators, but don\u0027t need to know about pipeline stages.\nSo yeah, basically I deffered to simplify this initial implementation.","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"9f15d22914de37bacdb9a5eaa23f9ba75330988e","unresolved":true,"context_lines":[{"line_number":307,"context_line":"  ``released_compute_nodes_count``."},{"line_number":308,"context_line":"* ``pipeline_volume_migrations_count`` — aggregates"},{"line_number":309,"context_line":"  ``planned_volume_migrate_count``."},{"line_number":310,"context_line":""},{"line_number":311,"context_line":"The combined indicators are stored as ``EfficacyIndicator`` rows linked to"},{"line_number":312,"context_line":"the Action Plan, using the existing data model without requiring new"},{"line_number":313,"context_line":"database columns or per-stage storage."},{"line_number":314,"context_line":""},{"line_number":315,"context_line":"Additionally, when the pipeline optimiser collapses or removes redundant"},{"line_number":316,"context_line":"migration chains, the number of eliminated migrations is recorded in the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"d3a2ab64_9795708b","line":313,"range":{"start_line":310,"start_character":1,"end_line":313,"end_character":38},"in_reply_to":"fc78dc31_551269db","updated":"2026-10-27 19:21:29.000000000","message":"Correct, the Efficacy Indicators today don\u0027t reflect efficacy indicators, but some output data information from resulting solutions, like counters. So yeah, it is just a counter that can be generated from the resulting action. \nThe only optimization result here is really the optimization made by the pipeline itseld in the end.\nAs I mentioned, without changing Ation Plan model to show a per Stage Efficacy Indicator, it is weird to present this info for the entire pipeline.\nWe can in this case: 1) keep these indicator as is proposed here as grouping equivalent. 2) remove all, and maybe just provide the optimization number from the pipeline planner.\nThe 1) is already implemented as a isolated patch, which we can decide to drop or not.\nI also think that these indicator needs to be normalised, and maybe have a difference field for: 1_ efficay indicators and 2_ strategy\u0027s counter/indicators (like instances skipped due to a constraint). I have this enhancement in my backlog, but it has lower priority than others that we have been discussing..","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"e7db942439562662e22c1f2e92ea65ead4388cd1","unresolved":true,"context_lines":[{"line_number":324,"context_line":"following items describe the expected future evolution of the feature, but are"},{"line_number":325,"context_line":"out of scope for this spec:"},{"line_number":326,"context_line":""},{"line_number":327,"context_line":"* Composite execution mode: group independent stages that do not require CDM or"},{"line_number":328,"context_line":"  metric simulation between them. This would allow operators to schedule a set"},{"line_number":329,"context_line":"  of independent audits as one unit, for example workload stabilization scoped"},{"line_number":330,"context_line":"  separately to multiple availability zones."},{"line_number":331,"context_line":"* CONTINUOUS and EVENT pipeline triggers: extend pipelines beyond ONESHOT"},{"line_number":332,"context_line":"  execution, including interval handling, webhook or event triggering,"},{"line_number":333,"context_line":"  ``next_run_time`` management, and interaction with the existing audit"}],"source_content_type":"text/x-rst","patch_set":3,"id":"f4c27ae2_ac3a9a9e","line":330,"range":{"start_line":327,"start_character":0,"end_line":330,"end_character":44},"updated":"2026-10-27 18:31:30.000000000","message":"for what its worth this is still what i woudl have started with\nas the inital pipeline target as its the simplest to implemnt and test the end to end bevior. secpilly if it procues one action plan per stage.","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"},{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"9f15d22914de37bacdb9a5eaa23f9ba75330988e","unresolved":true,"context_lines":[{"line_number":324,"context_line":"following items describe the expected future evolution of the feature, but are"},{"line_number":325,"context_line":"out of scope for this spec:"},{"line_number":326,"context_line":""},{"line_number":327,"context_line":"* Composite execution mode: group independent stages that do not require CDM or"},{"line_number":328,"context_line":"  metric simulation between them. This would allow operators to schedule a set"},{"line_number":329,"context_line":"  of independent audits as one unit, for example workload stabilization scoped"},{"line_number":330,"context_line":"  separately to multiple availability zones."},{"line_number":331,"context_line":"* CONTINUOUS and EVENT pipeline triggers: extend pipelines beyond ONESHOT"},{"line_number":332,"context_line":"  execution, including interval handling, webhook or event triggering,"},{"line_number":333,"context_line":"  ``next_run_time`` management, and interaction with the existing audit"}],"source_content_type":"text/x-rst","patch_set":3,"id":"46ca965e_69488d1c","line":330,"range":{"start_line":327,"start_character":0,"end_line":330,"end_character":44},"in_reply_to":"f4c27ae2_ac3a9a9e","updated":"2026-10-27 19:21:29.000000000","message":"Yeah, I remember that. I personally decided to go through this path and implement the Cascade first, which is harder to validate and get merged, yeah..","commit_id":"55a31f081bb2d00fca5f9215b3d35c9e59b4a685"}]}
