On Mon, 2014-07-07 at 18:11 +0000, Angus Salkeld wrote: > On 03/07/14 05:30, Mark McLoughlin wrote: > > Hey > > > > This is an attempt to summarize a really useful discussion that Victor, > > Flavio and I have been having today. At the bottom are some background > > links - basically what I have open in my browser right now thinking > > through all of this. > > > > We're attempting to take baby-steps towards moving completely from > > eventlet to asyncio/trollius. The thinking is for Ceilometer to be the > > first victim. > > Has this been widely agreed on? It seems to me like we are mixing two > issues: > 1) we need to move to py3 > 2) some people want to move from eventlet (I am not convinced that the > volume of code changes warrants the end goal - and review load) > > To achieve "1)" in a lower risk change, shouldn't we rather run eventlet > on top of asyncio? - i.e. not require widespread code changes. > > So we can maintain the main loop API but move to py3. I am not sure on > the feasibility, but seems to me like a more contained change.
Right - it's important that we see these orthogonal questions, particularly now that it appears eventlet is likely to be available for Python 3 soon. For example, if it was generally agreed that we all want to end up on Python 3 with asyncio in the long term, you could imagine deploying (picking random examples) Glance with Python 3 and eventlet, but Ceilometer with Python 2 and asyncio/trollius. However, I don't have a good handle on how your suggestion of switching to the asyncio event loop without widespread code changes would work? Mark. _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
