)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"381a92764d01f8892f6bb4589fa83a5ccc1a8d5a","unresolved":true,"context_lines":[{"line_number":12,"context_line":"   threading usage during a same SLURP release, so operators could test services"},{"line_number":13,"context_line":"   threading performance and possibly be back using eventlet if they find issues"},{"line_number":14,"context_line":" - we can\u0027t drop eventlet by a non-SLURP release or operators wouldn\u0027t be able"},{"line_number":15,"context_line":"   to verify performance before upgrading"},{"line_number":16,"context_line":" - we don\u0027t know the current state of effort for all the projects"},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"I propose then those new deadlines for the goal."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"ab388e29_790dfe70","line":15,"updated":"2025-06-19 17:16:46.000000000","message":"this is wrong.\n\nwe can drop event supprot in an a non slurp and we shoudl do that.\n\nwhat we shoudl avoid is droping it in a non slurp if the prior slurp could not run in threaded mode.\n\nplease fix this.\n\nit is very missleanign as currently written.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"8b89a708ec7eaa23a057fd3d4fc5795b0b54bcf7","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"cd15bdc4_f7e5759f","updated":"2025-06-20 12:11:58.000000000","message":"Hey Sylvain, do you mind to slightly change the `topic` of this review to make it visible into https://review.opendev.org/q/prefixtopic:%22eventlet-removal%22 ?","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"9f74d83b0af1dedad2987e501c7095395213b46d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"4e2bfc22_0de2cab2","updated":"2025-06-19 17:13:56.000000000","message":"Thanks @sbauza@redhat.com for pushing the proposal","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"cc994bed0494296c39368afbd6cd557c189759ac","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f8cc767d_92e24c55","updated":"2025-06-19 17:23:02.000000000","message":"by the way from my perspective this is all off by 1 cycle.\n\nthe current plann was one cycle to early the new one is one cycle too late.\n\nwe shoudl meet in the middle with the deprecations and support for both version aligning to the SLURP release(2027.1) and the removal to the next Non Slurp release.\n\nfor project that can run without eventlet in 2026.1 they should consider droping supprot for it in 2026.2 as 2026.1 will server as there bridge release.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"fa0a437f325f2ef3488cdb7890972513f3ec41b3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"66be85de_64e76b6d","updated":"2025-06-19 16:05:55.000000000","message":"proposal about timeline lgtm, but I would like to see more details about olso support and deprecation time.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"7bff53b011e25d8f06a416f8cce5905c1eeea191","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"da8db50a_cbf59704","updated":"2025-07-10 14:33:44.000000000","message":"thanks all for your comments, I\u0027ll update this change with another revision hopefully clarifying the milestones.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"dd5735c13b045500d6c8465c2ec0982998140e27","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"47549902_a8676ea8","in_reply_to":"f8cc767d_92e24c55","updated":"2025-06-20 18:38:22.000000000","message":"I agree on it. I think main goal for the change in timeline is to keep oslo support eventlet until 2027.1 (remove in 2027.2) which is achieved in your proposal also.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"6ef9b66ecf8c5d17ca0b90d4b414126ef544e2e5","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"06e832df_6eca55e6","updated":"2025-07-22 09:21:00.000000000","message":"LGTM thanks","commit_id":"981727b3d549d50eb81db18d2497abf716a3e6ed"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"c567c411c7b2a35a0ccc890bcc011f00a8706944","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"47e43c4f_7e6e96d4","updated":"2025-07-22 16:49:54.000000000","message":"This has had sufficient soak time, thank you..","commit_id":"981727b3d549d50eb81db18d2497abf716a3e6ed"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"abd85da2e4ac000d98f28cd1478ad899b222e0a5","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"6dd57212_5ae687ea","updated":"2025-07-10 16:46:16.000000000","message":"lgtm, thanks Sylvain for update.","commit_id":"981727b3d549d50eb81db18d2497abf716a3e6ed"},{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"61b8af1c5f22ed40448ffb0841e046ab42f04a91","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"8c5b8a6a_c49d7de8","updated":"2025-07-11 13:52:59.000000000","message":"looks good to me.","commit_id":"981727b3d549d50eb81db18d2497abf716a3e6ed"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"642b34886a87b9d7c1ab2b475fbb8baccfe62f72","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"15cea486_def05f01","updated":"2025-07-15 17:06:37.000000000","message":"that timeline looks beyond reasonable to me","commit_id":"981727b3d549d50eb81db18d2497abf716a3e6ed"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"bcce886ff4ff5bbfad0073f98f2562644a4f531e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"9f744674_c66f2d97","updated":"2025-07-10 14:38:04.000000000","message":"this looks both pragmatic and correct to me","commit_id":"981727b3d549d50eb81db18d2497abf716a3e6ed"}],"goals/selected/remove-eventlet.rst":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"fa0a437f325f2ef3488cdb7890972513f3ec41b3","unresolved":true,"context_lines":[{"line_number":51,"context_line":"   test Oslo changes related to new Asyncio based drivers;"},{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"cc4d8a37_fc6248e4","line":54,"range":{"start_line":54,"start_character":39,"end_line":54,"end_character":40},"updated":"2025-06-19 16:05:55.000000000","message":"As all deliverables are running without eventlet, can we declare (per project or global if all projects completed the work defined for 2026.2) the eventlet \u0027deprecation for removal\u0027 in 2028.1/future.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"5624f82cf7198e1fe7f9e95029eccd89d2ce0901","unresolved":true,"context_lines":[{"line_number":51,"context_line":"   test Oslo changes related to new Asyncio based drivers;"},{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"49df9acc_cecc4977","line":54,"range":{"start_line":54,"start_character":39,"end_line":54,"end_character":40},"in_reply_to":"0f156037_74390275","updated":"2025-06-19 17:28:42.000000000","message":"yeah, we can say \"mark it deprecation in your project as soon as you have new mode ready to use\". if any project finish early, we do not stop them to deprecate early.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"dd5735c13b045500d6c8465c2ec0982998140e27","unresolved":true,"context_lines":[{"line_number":51,"context_line":"   test Oslo changes related to new Asyncio based drivers;"},{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"59730243_dee64eee","line":54,"range":{"start_line":54,"start_character":39,"end_line":54,"end_character":40},"in_reply_to":"2e03b5eb_6007438c","updated":"2025-06-20 18:38:22.000000000","message":"I am little confused about what is difference between Sean proposal and this proposal which mainly want oslo to remove support in 2027.2 where original does in 2027.1.\n\n2028.1 timeline about retirement is confusing it. I agree to add deprecation phase which can be 2027.1. something like below:\n\n--------------------------\n#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained\n   support for running without Eventlet.\n#. (2027.1) Deprecate the Eventlet support. To have a SLURP target release supporting both the old Eventlet and\n any new concurrency mode, this release keeps the Eventlet support.\n#. (2027.2) Oslo drop the Eventlet support and OpenStack retire the Eventlet.\n\n\n- NOTE: Any project finishing the work before 2026.2 can do the step mentioned in 2027.1 early but make sure you have a one SLURP cycle to support both mode and deprecation phase.\n-------------------------","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"f7152454c1fb6db9e0e2264a9b626efaf3dcb425","unresolved":true,"context_lines":[{"line_number":51,"context_line":"   test Oslo changes related to new Asyncio based drivers;"},{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"2e03b5eb_6007438c","line":54,"range":{"start_line":54,"start_character":39,"end_line":54,"end_character":40},"in_reply_to":"49df9acc_cecc4977","updated":"2025-06-20 08:54:43.000000000","message":"I totally agree with Sean. In parallel of that, from a resource point of view and maintenance of Eventlet, I think 2028 is really something infeasible for many reasons I quoted them here https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/5PRCKO2NQBXGJLFHXM6QP5SAGGL2PEJZ/. RLocks and non-GIL mode in the lead.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"a346fc1bf1a530452c09efcb2e08b5e4aa7f9390","unresolved":false,"context_lines":[{"line_number":51,"context_line":"   test Oslo changes related to new Asyncio based drivers;"},{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"62db97ed_7427a01f","line":54,"range":{"start_line":54,"start_character":39,"end_line":54,"end_character":40},"in_reply_to":"59730243_dee64eee","updated":"2025-07-10 14:32:46.000000000","message":"I\u0027ll propose the above modification from Gmaan.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"9f74d83b0af1dedad2987e501c7095395213b46d","unresolved":true,"context_lines":[{"line_number":51,"context_line":"   test Oslo changes related to new Asyncio based drivers;"},{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"225e9396_d1e2be82","line":54,"range":{"start_line":54,"start_character":39,"end_line":54,"end_character":40},"in_reply_to":"cc4d8a37_fc6248e4","updated":"2025-06-19 17:13:56.000000000","message":"I think as based on this plan 2026.2 will have all the alternative concurrency mode available it is a good time to mark eventlet deprecated here suggesting to switch to the newly available concurrency mode.\n\nAs of when we remove Eventlet I think we can say either 2027.2 or 2028.1.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"381a92764d01f8892f6bb4589fa83a5ccc1a8d5a","unresolved":true,"context_lines":[{"line_number":51,"context_line":"   test Oslo changes related to new Asyncio based drivers;"},{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"0f156037_74390275","line":54,"range":{"start_line":54,"start_character":39,"end_line":54,"end_character":40},"in_reply_to":"cc4d8a37_fc6248e4","updated":"2025-06-19 17:16:46.000000000","message":"if we get to  this point in 2026.2 we can deprecate it in 2027.1 and remove it in 2027.2\n\nwe shoudl not wait till 2028.1 to do the removal\n\nalso project that have completed support for threaded mode in 2026.1 can do the removal in 2026.2 they do not need to wiat for all openstack to have got to that point ot drop supprot.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"ec48d7d38a6dd619dcb1ddffa65d38f335bf6c90","unresolved":true,"context_lines":[{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"961586c7_c4ee54cb","line":55,"updated":"2025-06-19 15:21:33.000000000","message":"These pushed-forward deadlines ignore a technical reality: newer versions of python will become more and more difficult to get working with eventlet; to the point where it\u0027s possible upcoming GIL or rlock changes will cause us to break these promises.\n\nI\u0027d rather make a promise that we can keep, rather than trying to keep eventlet on life support well-past when it\u0027s reasonable.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"c3185c384468b0b1abcbf102cbc7e6ad134a7657","unresolved":true,"context_lines":[{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"18e1d06f_6c027816","line":55,"in_reply_to":"0cfcfbdd_32b5ad76","updated":"2025-06-19 16:27:18.000000000","message":"Re py3.13 support, Yes that is where we need to take decision about we continue support py3.12 until we are not ready with eventlet-removal, the timeline mentioned in this proposal and python 3.12 EOL is giving us room to continue supporting py3.12. As per process[1], we do not need to be in hurry to stop support of python verions.\n\nAlso, there is no mandate or hurry for us to declare the support for py3.13. I know it mismatch with the distro shipping py3.13 as default but that is some compromise we need to do in this situation. \n\n\n[1] https://governance.openstack.org/tc/reference/pti/python.html#specific-commands\n\"Projects should avoid removing Python versions that have not reached End Of Life without a solid reason. It is recommended to keep compatability with older Python versions as long as possible. \"","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"2d274a241aac2ce3e1ecb3daa661cb2d87a32f36","unresolved":true,"context_lines":[{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"cb62ee0c_9fa535d7","line":55,"in_reply_to":"18e1d06f_6c027816","updated":"2025-06-19 16:33:57.000000000","message":"I like the idea of limiting support to specific python versions if you\u0027re going this way; it significantly limits the risk of keeping eventlet-the-library alive.\n\n\nI am completely against any sort of dictation to individual projects to provide two running modes. I wonder who you\u0027d get to develop the eventlet-compatible mode for Ironic?","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"c0c68ab662bf3868d980ce42b27e19535f5221b9","unresolved":true,"context_lines":[{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"802cb7d1_1cf2af46","line":55,"in_reply_to":"3d2a206f_1fa23eb6","updated":"2025-06-20 11:18:57.000000000","message":"we remove supprot for python verison in .2 release.\n\nwe removed 3.9 in 2025.2 and 3.10 will be 2026.2  so 3.11 would be 2027.2 and 3.12 will be there until 2028.2\n\nthis is aliging to the fact that python has adtoped a yearly release schdule and we wanted to do the removal in the non slurps ot not drop python version in slurp releases but also did not want to start development on a unsupproted version.\n\nhttps://devguide.python.org/versions/#supported-versions\n\nso we are doing the removal in the last non-slurp before the upstream Python EOL date rather than the first slurp where it is eol.\n\nthat leaning into the pattern of announcing the deprecations in slurps and removals in non-slurps.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"f7152454c1fb6db9e0e2264a9b626efaf3dcb425","unresolved":true,"context_lines":[{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"c93c4711_65340473","line":55,"in_reply_to":"3ed9fe7d_cf8e5602","updated":"2025-06-20 08:54:43.000000000","message":"\u003e That\u0027s actually a fair question : do we, as a community, want to accept that a release won\u0027t be accepting both eventlet and non-eventlet usages at the same time ? If so, we would force operators to downgrade to a previous release if they find performance issues with the components, which is a pretty high risk I wouldn\u0027t personnally take.\n\nI think that it is already too late to have this rethink... If I\u0027m right, Mistral and other deliverable already, started months ago, a strict removal of eventlet, without dual mode, and so without any possibility to revert, so... I think the same is true for Neutron. They started to replace their WSGI eventlet implementation by something else, and their migrated code is not dual, their migration is simply incremental.\n\nAn other aspect that I can imagine, is that, in parallel of eventltet migration, deliverables continued to have their life, they surely continued to aligne to the updates imposed by CPython, (removal of deprecated things, etc...) I do not see how we can ask them to revert back strictly to an old version of Python (e.g 3.12), if their usages of the CPython API are not anymore aligned. But maybe I\u0027m wrong. I\u0027d say that we have to check that point before considering that reverting to Python 3.12 is something that can be doable.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"efb444ee7a81601d01163a0a273134c1bda5c83c","unresolved":true,"context_lines":[{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ebc95bcf_e85173b8","line":55,"in_reply_to":"4d497d3b_664b135e","updated":"2025-06-19 16:09:28.000000000","message":"I hereby don\u0027t disagree with you Jay on the fact that eventlet can\u0027t magically support py3.13.\nThat said, py3.12 will be supported until Oct 2028 which leaves us enough room to validate such proposal.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"85858ad1c18e1a653cb769fb3f8e7ed4ac142384","unresolved":true,"context_lines":[{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ed9fe7d_cf8e5602","line":55,"in_reply_to":"51ff7afd_75d93ead","updated":"2025-06-19 17:20:15.000000000","message":"yes i also think that we will liekly decare that 3.13 requires threaded mode unless the current eventbug get fixed.\n\nwe may want to consider adding a startup chck that prevents using eventlet mode or simialr at some point. at the very least it shoudl have a large warning that its an unsupported combination (py3.13 + eventlet mode).","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"a346fc1bf1a530452c09efcb2e08b5e4aa7f9390","unresolved":false,"context_lines":[{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"d9f872af_c31daca7","line":55,"in_reply_to":"802cb7d1_1cf2af46","updated":"2025-07-10 14:32:46.000000000","message":"I\u0027ll mention 2027.2 as the target version for the removal.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"ea614ef711c968b7557293336ce15e47afb6c233","unresolved":true,"context_lines":[{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"4d497d3b_664b135e","line":55,"in_reply_to":"961586c7_c4ee54cb","updated":"2025-06-19 15:23:14.000000000","message":"An additional note: Not all OpenStack projects have promised operators the ability to control eventlet/non-eventlet running modes. This policy presumes that most have, and will put strain on the entire OpenStack project -- a strain that will not be required for many deliverables.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"7b8675a117eeae0999d8f38308a41d24ff2d6991","unresolved":true,"context_lines":[{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3d2a206f_1fa23eb6","line":55,"in_reply_to":"c93c4711_65340473","updated":"2025-06-20 09:54:19.000000000","message":"\u003e An other aspect that I can imagine, is that, in parallel of eventltet migration, deliverables continued to have their life, they surely continued to aligne to the updates imposed by CPython, (removal of deprecated things, etc...) I do not see how we can ask them to revert back strictly to an old version of Python (e.g 3.12), if their usages of the CPython API are not anymore aligned. But maybe I\u0027m wrong. I\u0027d say that we have to check that point before considering that reverting to Python 3.12 is something that can be doable.\n\nDo we plan to remove the support for py312 in 2027.1? If not then our deliverables should still work with py312 in this time frame. So I think it is reasonable to say in this time frame in the nova doc that if the deployer wants to keep using nova with eventlet mode due to any reasons (bug or severe performance degradation in threading mode, or convenience to change the mode after the upgrade is finished to 2027.1) then they can do it by enabling eventlet mode while running nova top of py3.12.\n\n\n\u003e I think that it is already too late to have this rethink... If I\u0027m right, Mistral and other deliverable already, started months ago, a strict removal of eventlet, without dual mode, and so without any possibility to revert, so... I think the same is true for Neutron. They started to replace their WSGI eventlet implementation by something else, and their migrated code is not dual, their migration is simply incremental.\n\n\nSure not all openstack projects supports such a dual mode. Probably those projects have more confidence about that their services works well in the new concurrency mode, or they can offer quicker workaround and bugfix turnaround time than nova.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"9f74d83b0af1dedad2987e501c7095395213b46d","unresolved":true,"context_lines":[{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"51ff7afd_75d93ead","line":55,"in_reply_to":"cb62ee0c_9fa535d7","updated":"2025-06-19 17:13:56.000000000","message":"I\u0027m totally OK to say that the eventlet mode of nova is only supported on py3.12 and not in newer python versions.\n\nBut I do want to emphasize that we are not keeping eventlet around in nova because we the developers want to keep it but because:\n\n* We don\u0027t have enough capacity to remove it in time to align with the current timeline. If the patch author and core reviewer capacity can be increased magically then the current timeline can be revisited.\n\n* We are responding to customer requests to keep a release with a way to switch back to eventlet due to concerns on performance and stability of the new threading model. The Nova core team agreed on the PTG that this is a fair request. Walking back on this promise does not sit well with me but sure can be brought up for discussion with the core team.\n\n\u003e I am completely against any sort of dictation to individual projects to provide two running modes. I wonder who you\u0027d get to develop the eventlet-compatible mode for Ironic?\n\nI see how this patch can be understood that way. We need to reformulate it to only include the possibility for some modules to support both modes.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"071f4760e4de2a87bef4a0ca9fcd043d9d844853","unresolved":true,"context_lines":[{"line_number":52,"context_line":"#. (2025.2) Get non actively maintained OpenStack deliverables retired;"},{"line_number":53,"context_line":"#. (2026.2) Ensure all other OpenStack deliverables relying on Eventlet gained"},{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"}],"source_content_type":"text/x-rst","patch_set":1,"id":"0cfcfbdd_32b5ad76","line":55,"in_reply_to":"ebc95bcf_e85173b8","updated":"2025-06-19 16:12:36.000000000","message":"\u003e This policy presumes that most have, and will put strain on the entire OpenStack project -- a strain that will not be required for many deliverables.\n\nThat\u0027s actually a fair question : do we, as a community, want to accept that a release won\u0027t be accepting both eventlet and non-eventlet usages at the same time ? If so, we would force operators to downgrade to a previous release if they find performance issues with the components, which is a pretty high risk I wouldn\u0027t personnally take.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"fa0a437f325f2ef3488cdb7890972513f3ec41b3","unresolved":true,"context_lines":[{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"References"}],"source_content_type":"text/x-rst","patch_set":1,"id":"33b86b5b_8db39eea","line":57,"range":{"start_line":57,"start_character":11,"end_line":57,"end_character":63},"updated":"2025-06-19 16:05:55.000000000","message":"for me this was the confusion, can we add here explicitly that oslo will still support the eventet in this release.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"9f74d83b0af1dedad2987e501c7095395213b46d","unresolved":true,"context_lines":[{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"References"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ad2eb39c_570ece01","line":57,"range":{"start_line":57,"start_character":11,"end_line":57,"end_character":63},"in_reply_to":"33b86b5b_8db39eea","updated":"2025-06-19 17:13:56.000000000","message":"for me when oslo removes the eventlet backend in 2027.2 it automatically forces all the other modules to drop the usage of eventlet. Sure we can clarify that here that not just oslo but all openstack removes the eventlet import. \n\nI\u0027m not sure why we had this originally as two steps. So I might missing something here.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"381a92764d01f8892f6bb4589fa83a5ccc1a8d5a","unresolved":true,"context_lines":[{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"References"}],"source_content_type":"text/x-rst","patch_set":1,"id":"a32d3658_49cc347c","line":57,"range":{"start_line":57,"start_character":11,"end_line":57,"end_character":63},"in_reply_to":"33b86b5b_8db39eea","updated":"2025-06-19 17:16:46.000000000","message":"i think this is off by one. this is the release wehre oslo should be removing eventlet \n\nthe last SLURP to supprot eventelt shodl be 2027.1 unless thre is an excptional reasons not to. i.e large project that have nto completed the ablity to run in threading mode in 2027.1.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"f7152454c1fb6db9e0e2264a9b626efaf3dcb425","unresolved":true,"context_lines":[{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"References"}],"source_content_type":"text/x-rst","patch_set":1,"id":"61161d6b_87db0418","line":57,"range":{"start_line":57,"start_character":11,"end_line":57,"end_character":63},"in_reply_to":"42618a51_8d295c69","updated":"2025-06-20 08:54:43.000000000","message":"oslo have to remove its eventlet support once all services are migrated. In other words oslo should come last in their eventlet retirement and close the migration from an openstack PoV.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"dd5735c13b045500d6c8465c2ec0982998140e27","unresolved":true,"context_lines":[{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"References"}],"source_content_type":"text/x-rst","patch_set":1,"id":"612c0160_c51937ac","line":57,"range":{"start_line":57,"start_character":11,"end_line":57,"end_character":63},"in_reply_to":"61161d6b_87db0418","updated":"2025-06-20 18:38:22.000000000","message":"Ok to here oslo will remove the eventlet support so we do not need 2028.1 to retire the eventlet which is basically happening 2027.2","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"8dc32e81cdec1e39ace84b196e77686e4a1df882","unresolved":false,"context_lines":[{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"References"}],"source_content_type":"text/x-rst","patch_set":1,"id":"12ef1f74_86a7e788","line":57,"range":{"start_line":57,"start_character":11,"end_line":57,"end_character":63},"in_reply_to":"612c0160_c51937ac","updated":"2025-07-10 14:36:38.000000000","message":"Done","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"5624f82cf7198e1fe7f9e95029eccd89d2ce0901","unresolved":true,"context_lines":[{"line_number":54,"context_line":"   support for running without Eventlet."},{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"References"}],"source_content_type":"text/x-rst","patch_set":1,"id":"42618a51_8d295c69","line":57,"range":{"start_line":57,"start_character":11,"end_line":57,"end_character":63},"in_reply_to":"a32d3658_49cc347c","updated":"2025-06-19 17:28:42.000000000","message":"yeah, we should merge 2028.1 here and oslo drop support and all deliverables have to remove support and global retirement needs to happen together in 2027.2","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"fa0a437f325f2ef3488cdb7890972513f3ec41b3","unresolved":true,"context_lines":[{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"References"},{"line_number":61,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"25d4ada9_d28dd675","line":58,"range":{"start_line":58,"start_character":12,"end_line":58,"end_character":14},"updated":"2025-06-19 16:05:55.000000000","message":"To clearly mentioned about explicit when oslo will drop eventlet support, can we add here about \"Oslo drop the eventlet support and Eventlet will be retired from OpenStack.\"","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"381a92764d01f8892f6bb4589fa83a5ccc1a8d5a","unresolved":true,"context_lines":[{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"References"},{"line_number":61,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ffa7a6e0_5f4677b2","line":58,"range":{"start_line":58,"start_character":12,"end_line":58,"end_character":14},"in_reply_to":"25d4ada9_d28dd675","updated":"2025-06-19 17:16:46.000000000","message":"-1 this is far later then i think is reaonable.\n\nthe removal in oslo can only happen when all user have moved but that shoudl happen in 2027.2 not 2028.1\n\ndoing it in 2028.1 mean we missed or goal of beign able to run all service without eventlet in 2027.1","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"f7152454c1fb6db9e0e2264a9b626efaf3dcb425","unresolved":true,"context_lines":[{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"References"},{"line_number":61,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"d941f434_3795d9e6","line":58,"range":{"start_line":58,"start_character":12,"end_line":58,"end_character":14},"in_reply_to":"349eec24_eaba4d4e","updated":"2025-06-20 08:54:43.000000000","message":"-1 agree with Sean.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"a346fc1bf1a530452c09efcb2e08b5e4aa7f9390","unresolved":false,"context_lines":[{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"References"},{"line_number":61,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"bfc57b5a_deefc703","line":58,"range":{"start_line":58,"start_character":12,"end_line":58,"end_character":14},"in_reply_to":"93840c50_d2933c25","updated":"2025-07-10 14:32:46.000000000","message":"Done.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"dd5735c13b045500d6c8465c2ec0982998140e27","unresolved":true,"context_lines":[{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"References"},{"line_number":61,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"93840c50_d2933c25","line":58,"range":{"start_line":58,"start_character":12,"end_line":58,"end_character":14},"in_reply_to":"d941f434_3795d9e6","updated":"2025-06-20 18:38:22.000000000","message":"My point here what is difference between 2027.2 and 2028.1 timeline/goal?\n\nif oslo drop support of eventlet in 2027.2 then that time only it is gone. what is meaning of \u0027#  (2028.1) Get Eventlet retired from OpenStack;\u0027 ?\n\nI am saying let\u0027s merge the 2027.2 and 2028.1 timeline in single line otherwise it is confusing.\n\n- (2027.1) Oslo drop the support of Eventlet and get Eventlet retired from OpenStack.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"5624f82cf7198e1fe7f9e95029eccd89d2ce0901","unresolved":true,"context_lines":[{"line_number":55,"context_line":"#. (2027.1) To have a SLURP target release supporting both the old Eventlet and"},{"line_number":56,"context_line":" any new concurrency mode, this release keeps the Eventlet support."},{"line_number":57,"context_line":"#. (2027.2) Get usage of Eventlet in oslo deliverables removed;"},{"line_number":58,"context_line":"#  (2028.1) Get Eventlet retired from OpenStack;"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"References"},{"line_number":61,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"349eec24_eaba4d4e","line":58,"range":{"start_line":58,"start_character":12,"end_line":58,"end_character":14},"in_reply_to":"ffa7a6e0_5f4677b2","updated":"2025-06-19 17:28:42.000000000","message":"yeah that is where this 2028.1 timeline was confusing to me. Let\u0027s drop this and if any project missed 2027.2 deadline then we anyways have \"do it asap\" timeline for them.","commit_id":"c47339bf5f34bccb898cb6da822271dda1197a70"}]}