[openstack-dev] [Keystone] Unified logging and Eventlet conflict

Lance D Bragstad ldbragst at us.ibm.com
Thu Jun 27 00:17:47 UTC 2013



Hey all,

Recently there has been some push to get a unified logging implementation
pulled from Oslo-incubator into Keystone (Blueprint:
https://blueprints.launchpad.net/keystone/+spec/unified-logging-in-keystone).
 Keystone has been actively working to isolate eventlet code within
Keystone and bringing in the current implementation from Oslo-incubator
would go against that work, as /oslo-incubator/openstack/common/log.py
imports  /oslo-incubator/openstack/common/local.py which has a dependency
on eventlet
(https://github.com/openstack/oslo-incubator/blob/master/openstack/common/local.py#L22)
 and is used for storing references to contexts. I know there has been a
couple of projects looking to not be dependent on eventlet and thought this
might be a good topic for the mailing list, especially if these changes end
up in Oslo-incubator.

After discussion with a couple of the Keystone members, one option is to
tweak local.py to check if eventlet is even installed (similar to def
_ensure_subprocess here:
https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/common/cms.py#L11)
 and if it isn't then try implementing a different WeakLocal store not
using corolocal.local. Any other ideas on how to approach this are more
than welcome. Thanks!



Best Regards,

Lance Bragstad
Software Engineer - OpenStack
Cloud Solutions and OpenStack Development
T/L 553-5409, External 507-253-5409
ldbragst at us.ibm.com, Bld 015-2/C118
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130626/075e63ad/attachment.html>


More information about the OpenStack-dev mailing list