-
Spike
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
False
-
-
False
-
rhos-ops-platform-services-pidone
-
-
-
Important
Goal: Through the Scrum of Scrums ceremony, the Product Owner of the PIDONE team will convene and chair a cross-project PO meeting (video/Slack) covering all OpenStack services that rely on oslo.service (Nova, Neutron, Cinder, Keystone, Glance, Heat...). Objectives are to
- Present the upcoming spawn-method migration and its deadlock-prevention rationale.
- Collect per-project impacts, blockers, and timelines.
- Create or delegate creation of Jira tasks/stories in each project's board for any required code, test, or documentation work, all linked back to this ticket.
Acceptance Criteria:
- Ownership: Ticket is assigned to the PIDONE Product Owner (Tatiana) and marked "Scrum of Scrums".
- Invite: PIDONE PO schedules a Scrum-of-Scrums session (date, time, platform) including POs from Nova, Neutron, Cinder, Keystone, Glance, Heat at minimum.
- Agenda: Shared 48 h in advance by PIDONE PO; must include slide summarising the fork deadlock issue and spawn solution.
- Attendance: At least one Product Owner (or delegate) from each invited project attends (verify via attendee list).
- Minutes: PIDONE PO posts concise minutes within 24 h: decisions, action items, owners, and due dates.
- Downstream tasks: For every action item affecting another project, a linked Jira task/story exists in that project's backlog, created or verified by the PIDONE PO, and linked in a "Related Issues" section here.
- Acknowledgement: Each downstream project's PO comments or updates status on their new task(s) within one week, confirming ownership.
Additional Details:
See https://pythonspeed.com/articles/python-multiprocessing/ and explanatory video https://youtu.be/RIc-Tut95YM?t=185.
- is blocked by
-
OSPRH-17949 [fork vs multiprocessing] 9 - Prepare and deliver public all hand presentation on spawn-safe multiprocessing in oslo.service
-
- Backlog
-