Please note: This schedule is for OpenStack Active Technical Contributors participating in the Icehouse Design Summit sessions in Hong Kong. These are working sessions to determine the roadmap of the Icehouse release and make decisions across the project. To see the full OpenStack Summit schedule, including presentations, panels and workshops, go to http://openstacksummitnovember2013.sched.org.
5) Run unit tests against all backends (not only sqlite)
6) If we implement 3 & 4 we could drop support of sqlite in migration
7) Get rid of soft delete or implement fast and safe purge engine (not archiving).
We have a lot of problems with soft deletion: 1) must have purge engine 2) bad performance 3) complicated logic
It seems that in almost all cases we are able to delete instantly records. So we should deep analyze this situatiin & probably refactor current DB to get rid of soft deletion.
8) Get from DB only what we actually need. Now we are always getting 3 columns "create_at", "updated_at", "deleted_at" (it is half of DB traffic sic.. ) and they are pretty rare used.
(Session proposed by Boris)
Next steps for database improvement:
I'd like to see a general database session in the nova track.
Proposed items to discuss:
* the database CI stuff that Josh Hesketh and I have been working on * whether a move to alembic makes sense