On 19 June 2012 12:43, John Arbash Meinel <j...@arbash-meinel.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > ... >> Some routes are: - move to postgresql using the lower level APIs >> and add storm later - work on the storm patchset to make it >> reliable with sqlite - do both postgresql and sqlite at the same >> time. >> >> My recommendation, given the existing investment, is to bite the >> bullet: bring up a postgresql instance in staging and prod, dump >> and import the data to it, and switch over to postgresql. Debug any >> issues in real-time, and move on. The depth of potential issues is >> sharply limited, because postgresql handles many more combinations >> of client interaction than SQLite (by design and necessity). >> >> -Rob >> > > Note that there is no staging for udd, and we currently do not even > have backups of the databases. > > I'm personally most in favor of an incremental approach that brings in > storm (with a hack for the isolation level), and then postgres. > > I know that we are all in agreement that moving to postgres is what we > want to do. The argument is mostly about how we do the transition, and > what steps are most relevent towards getting there.
We haven't had any movement on this for a few days. To sum up, this is my understanding of the situation. 1. We need to switch our udd to postgres 2. We need to make code changes to do so 3. We want to integrate these changes into trunk to avoid a fork 4. We cannot because udd core developers consider it too dangerous to do so, and the costs of production experimentation too high 5. We therefore must demonstrate that it's not too dangerous 6. We do not know how to do so 7. Thus, to proceed, we need a finite, clear, actionable, cheap plan about to demonstrate the safety of this change or to reduce the cost/risk of changes to production to an acceptable level 8. We need this from you. Until we receive it, we are blocked on this task I hope this helps. I really, really look forward to hearing a plan from the udd maintainers on how we can do this. jml -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
