It took me a while to untangle this so prepare for links. :)
I noticed this change [1] today for global-requirements to require tooz
[2] for a ceilometer blueprint [3].
The sad part is that tooz requires pymemcache [4] which is, from what I
can tell, a memcached client that is not the same as python-memcached [5].
Note that python-memcached is listed in global-requirements already [6].
The problem I have with this is it doesn't appear that RHEL/Fedora
package pymemcache (they do package python-memcached). I see that
openSUSE builds separate packages for each. It looks like Ubuntu also
has separate packages.
My question is, is this a problem? I'm assuming RDO will just have to
package python-pymemcache themselves but what about people not using RDO
(SOL? Don't care? Other?).
Reverting the requirements change would probably mean reverting the
ceilometer blueprint (or getting a version of tooz out that works with
python-memcached which is probably too late for that right now). Given
the point in the schedule that seems pretty drastic.
Maybe I'm making more of this than it's worth but wanted to bring it up
in case anyone else has concerns.
[1] https://review.openstack.org/#/c/93443/
[2] https://github.com/stackforge/tooz/blob/master/requirements.txt#L6
[3]
http://specs.openstack.org/openstack/ceilometer-specs/specs/juno/central-agent-partitioning.html
[4] https://pypi.python.org/pypi/pymemcache
[5] https://pypi.python.org/pypi/python-memcached/
[6]
https://github.com/openstack/requirements/blob/master/global-requirements.txt#L108
--
Thanks,
Matt Riedemann
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
