| sean-k-mooney | hberaud: genuine question. looking at oslo service im not sure i agree with | 11:23 |
|---|---|---|
| sean-k-mooney | the assertion that we cant make this work with or without eventlet | 11:23 |
| sean-k-mooney | i was orgianlly goign to put of the oslo seveice part of the eventlet removal till next cycle | 11:24 |
| sean-k-mooney | but i would realy like to understand why we can just supprot both in oslo | 11:25 |
| sean-k-mooney | oslo.messaging support using eventlet or useing a thread pool executor | 11:25 |
| sean-k-mooney | ignoring the wsgi server part | 11:25 |
| sean-k-mooney | i think we coudl suport the same for oslo service and delegate part to futureist | 11:25 |
| sean-k-mooney | in the unlikely event i find time to work on that would the oslo comunity be opposed to tryign to enabel that | 11:26 |
| sean-k-mooney | basiclly the idea woudl be to keep oslo services current api and refactor it into two backend | 11:27 |
| sean-k-mooney | the first being the current implemation | 11:27 |
| sean-k-mooney | and the second perhaps beign a wraper aroudn cotyledon or a refactorign of the existing oslo service impleation to be very similar | 11:28 |
| sean-k-mooney | basically upstreamign the cotyledon into oslo.service | 11:28 |
| sean-k-mooney | hberaud: is there an oslo spec for the oslo.service evolotuion in the context fo the eventlet refactor sepeate form teh goal document | 11:30 |
| sean-k-mooney | all of the wsgi stuff for example i think shoudl be refector to a serpeate oslo.wsgi repos as an optional depency of oslo servie with a dprecation phase | 11:31 |
| sean-k-mooney | that way we can either select a replacement framework ro stop using it entirly | 11:32 |
| *** haleyb|out is now known as haleyb | 13:34 | |
| abhishekk | hey all, I need some reviews on this patch, https://review.opendev.org/c/openstack/oslo.middleware/+/920055 | 17:00 |
| *** jph5 is now known as jph | 17:46 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!