Given that sqla 0.9 just came out, I wanted to explore, again, what the
state of the world was with sqla 0.8 (especially given that Ubuntu and
Red Hat are both shipping 0.8 in their OpenStack bundles) -
https://review.openstack.org/#/c/64831/
The answer is not great. But more importantly, the answer is actually
worse than the last time we checked, which I think gives this some
urgency to move forward.
One of the key problems is taskflow, which has an sqla pin, which breaks
all the cinder entry points. This was actually entirely the problem
global requirements was meant to address, but it really can't when there
are nested requirements like this, in stackforge projects that aren't
installing via git (so we can rewrite their requirements).
So why does taskflow have the SQLA pin? And if the answer is global
requirements, then taskflow can't be installing via pypi like it is now,
because it's by nature taking a wedge. So we need a real solution here
to un bind us, because right now it's actually impossible to upgrade
sqla in requirements because of taskflow.
-Sean
--
Sean Dague
Samsung Research America
s...@dague.net / sean.da...@samsung.com
http://dague.net
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
