Difference between revisions of "Modernize Openstack Networking Programming Model"

Revision as of 10:18, 11 December 2023

Short terms solutions

Legend: [x] = done [ ] = not yet done

[x] Open a discussion with current eventlet maintainers

[ ] (optional) Propose to migrate the official repository into the Openstack organisation

[ ] (optional) Start engaging a forking process of eventlet

[ ] (optional) Adapt testing and project structure to your tooling

[ ] (optional) Openstack deliverables that rely on it would have to update their requirements to pull the new fork instead of the original version

[ ] (optional) Socialize the move or the fork of eventlet

[ ] (optional) Cherry pick the existing CI fix into the new repository of eventlet into the Openstack organisation

[ ] Merge the CI patches.

[ ] (optional) Cherry pick the existing Python 3.12 fix into the new repository of eventlet into the Openstack organisation

[ ] Merge the fix for introduce the support of Python 3.12

[ ] Release the latest changes by creating a new version

[ ] Upgrade the Openstack requirements to match this new version

[ ] Validate that the main issues are now fixed

[ ] Announce the current state of the art after the previous steps are done

[ ] (optional) Decide with the TC to postpone the support of Python 3.12 within the next series ("D") if the validation failed and if we are to close from the deadline. Socialize that point to the community. This is a possible way out that we must still avoid at all costs.

[ ] (optional) If we previously postponed the support of Python 3.12 due to validation issue, see what happens and try to fix it during "D".

Medium terms solutions

[ ] Design specs of oslo.aiohub (https://wiki.openstack.org/wiki/Aiohub-Discussion)

[ ] identifying the low hanging fruits - deliverables that can be easily migrated (https://wiki.openstack.org/wiki/Eventlet-Based-Deliverables-Easily-Migrated)

@@ Line 5: / Line 5: @@
 [ ] = not yet done
-- [x] Open a discussion with current eventlet maintainers
+* [x] Open a discussion with current eventlet maintainers
-- [ ] (optional) Propose to migrate the official repository into the Openstack organisation
+* [ ] (optional) Propose to migrate the official repository into the Openstack organisation
-- [ ] (optional) Start engaging a forking process of eventlet
+* [ ] (optional) Start engaging a forking process of eventlet
-- [ ] (optional) Adapt testing and project structure to your tooling
+* [ ] (optional) Adapt testing and project structure to your tooling
-- [ ] (optional) Openstack deliverables that rely on it would have to update their requirements to pull the new fork instead of the original version
+* [ ] (optional) Openstack deliverables that rely on it would have to update their requirements to pull the new fork instead of the original version
-- [ ] (optional) Socialize the move or the fork of eventlet
+* [ ] (optional) Socialize the move or the fork of eventlet
-- [ ] (optional) Cherry pick the existing CI fix into the new repository of eventlet into the Openstack organisation
+* [ ] (optional) Cherry pick the existing CI fix into the new repository of eventlet into the Openstack organisation
-- [ ] Merge the CI patches.
+* [ ] Merge the CI patches.
-- [ ] (optional) Cherry pick the existing Python 3.12 fix into the new repository of eventlet into the Openstack organisation
+* [ ] (optional) Cherry pick the existing Python 3.12 fix into the new repository of eventlet into the Openstack organisation
-- [ ] Merge the fix for introduce the support of Python 3.12
+* [ ] Merge the fix for introduce the support of Python 3.12
-- [ ] Release the latest changes by creating a new version
+* [ ] Release the latest changes by creating a new version
-- [ ] Upgrade the Openstack requirements to match this new version
+* [ ] Upgrade the Openstack requirements to match this new version
-- [ ] Validate that the main issues are now fixed
+* [ ] Validate that the main issues are now fixed
-- [ ] Announce the current state of the art after the previous steps are done
+* [ ] Announce the current state of the art after the previous steps are done
-- [ ] (optional) Decide with the TC to postpone the support of Python 3.12 within the next series ("D") if the validation failed and if we are to close from the deadline. Socialize that point to the community. This is a possible way out that we must still avoid at all costs.
+* [ ] (optional) Decide with the TC to postpone the support of Python 3.12 within the next series ("D") if the validation failed and if we are to close from the deadline. Socialize that point to the community. This is a possible way out that we must still avoid at all costs.
-- [ ] (optional) If we previously postponed the support of Python 3.12 due to validation issue, see what happens and try to fix it during "D".
+* [ ] (optional) If we previously postponed the support of Python 3.12 due to validation issue, see what happens and try to fix it during "D".
 ==Medium terms solutions==
-===Design specs of oslo.aiohub===
+* [ ] Design specs of oslo.aiohub (https://wiki.openstack.org/wiki/Aiohub-Discussion)
-====Description====
+* [ ] identifying the low hanging fruits - deliverables that can be easily migrated (https://wiki.openstack.org/wiki/Eventlet-Based-Deliverables-Easily-Migrated)
-====Specs====
-===identifying the low hanging fruits - deliverables that can be easily migrated===
-====Ironic-Python-Agent====
-The Ironic-Python-Agent project is a good candidate as a pilot for a migration. It uses and relies on eventlet heavily, but has limited inter-openstack dependencies and co-installed dependencies. In general, the Ironic community is onboard to having IPA be a pilot project for this if it's useful (realistically; it may be too simple -- IPA may be an easy enough case just to completely rip eventlet out of without a migration).
 ==Long terms solutions==