-
Spike
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
False
-
-
False
-
rhos-ops-platform-services-pidone
-
-
-
Moderate
Summary:
Investigate adding first-class link() (callback-on-completion) support to oslo_service.backend.threading so Heat and other projects can drop their custom ThreadWithCallback wrapper discussed in Gerrit review #952090 (comment 61b8bffe_9b04c5cb).
Goal:
Determine whether a generic, reusable callback API inside oslo.service is technically feasible, offers clear value over local wrappers, and can be introduced without breaking existing consumers. Success means we can deliver a well-reasoned recommendation—proceed, defer, or reject—plus a high-level implementation plan that downstream projects accept.
TimeBox:
☑ One sprint (≤ 2 weeks) from ticket start to decision.
Deliverables / Outcomes:
| Artifact | Description |
|---|---|
| Technical Brief (Markdown/Confluence) | • Current usage patterns in Heat and any other projects • Gap analysis of oslo.service threading vs. required link() semantics • Proposed API surface & lifecycle diagrams • Risk/benefit assessment (performance, deadlock potential, maintenance cost) |
| Proof-of-Concept Patch (optional but preferred) | Minimal implementation of link() in oslo.service with unit tests to demonstrate viability. |
| Decision & Next-Step Epic/Stories | Jira Epic (if we proceed) or summary comment (if we defer/reject) capturing implementation tasks, testing, documentation, and migration guidance. |
| Meeting Summary | 5-minute presentation or written update shared in PIDONE weekly team meeting and a related thread on openstack-discuss. |
