On 11/14/2013 10:38 PM, Matt Riedemann wrote:
Joe,
Hey, I missed this question. I moved email accounts for the
openstack-dev mailing list and missed this in my old pile.
So I touched on this a bit in response here [1] and also a bit when
talking about the plans for CI for the nova PowerVM virt driver here
[2]. The blueprint for adding DB2 support to sqlalchemy-migrate and the
DB2 enablement wiki [3] does call out CI. Getting the
sqlalchemy-migrate unit tests to run against DB2 isn't that hard, I just
haven't figured out if it's something I can do with community
infrastructure or running as an external third party test, and I think
whether we use Express-C or not would matter there since that has a
trial license.
I'm open to suggestions/comments/ideas.
[1]
http://lists.openstack.org/pipermail/openstack-dev/2013-November/018714.html
[2]
http://lists.openstack.org/pipermail/openstack-dev/2013-October/016395.html
[3] https://wiki.openstack.org/wiki/DB2Enablement
Thanks to Brant Bknudson for pointing out that DB2 Express-C doesn't
have a time restriction:
http://www.ibm.com/developerworks/downloads/im/db2express/
"It is a fully licensed product available for free download. It does not
have any time restrictions."
I must have mistaken that with Enterprise Server Edition that we were
using in house for some bigger deployments for CI with Tempest.
So it sounds like Express-C is what we could use to get
sqlalchemy-migrate unit tests running against DB2 using the community
infrastructure (I hope), I just need some help with getting that going.
I know Roman got the migrate UT running for MySQL and PostgreSQL here:
https://review.openstack.org/#/c/40436/
I'll try working with Roman, Monty and any infra guys that will talk to
me to get this going.
--
Thanks,
Matt Riedemann
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
