Hi all, Yes, once the oslo.db initial release is cut, we expect the migration from using of its oslo-incubator version to a library one to be as simple as following the steps you've mentioned. Though, we still need to finish the setup of oslo.db repo (AFAIK, this is currently blocked by the fact we don't run gate tests for oslo.db patches. Doug, Victor, please correct me, if I'm wrong).
Thanks, Roman On Mon, May 5, 2014 at 7:47 AM, Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote: > Just wanted to get some thoughts down while they are in my head this > morning. > > Oslo DB is now a library [1]. I'm trying to figure out what the steps are > to getting Nova to using that so we can rip out the sync'ed common db code. > > 1. Looks like it's not in global-requirements yet [2], so that's probably a > first step. > > 2. We'll want to cut a sqlalchemy-migrate release once this patch is merged > [3]. This moves a decent chunk of unique constraint patch code out of oslo > and into sqlalchemy-migrate where it belongs so we can run unit tests with > sqlite to drop unique constraints. > > 3. Rip this [4] out of oslo.db once migrate is updated and released. > > 4. Replace nova.openstack.common.db with oslo.db. > > 5. ??? > > 6. Profit! > > Did I miss anything? > > [1] http://git.openstack.org/cgit/openstack/oslo.db/ > [2] > http://git.openstack.org/cgit/openstack/requirements/tree/global-requirements.txt > [3] https://review.openstack.org/#/c/87773/ > [4] https://review.openstack.org/#/c/31016/ > > -- > > Thanks, > > Matt Riedemann > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
