Open Stack

Howdy,

Quick bit of background. Turbo-hipster is a 3rd party CI system that runs
nova's database migrations against real datasets to try and catch
real-world problems.

When it was initially written the state of migrations in nova would cause a
lot of pain for deployers (such as very long downtimes while upgrades were
performed or just not working at all). Since then nova has made conscious
efforts to minimise this time and are generally aware when implementing a
necessary migration may cause large downtimes and attempt to work around it
where possible.

turbo-hipster used to run against every change in nova. This was to catch
changes that may have affected migration performance as a side effect.
However for the last few months turbo-hipster has only been running against
changes modifying files in nova/db/*. Any changes outside of there that
causes pain can likely be reverted.

As a note, turbo-hipster is currently not running due to
https://review.openstack.org/#/c/374307/ until I have time to update the
datasets used.

The question now is whether or not to continue running. Is there still
value in running turbo-hipster? It uses significant resources and it feels
that developers have learned the lessons it was designed to teach.

Not running it increases the risk a migration will fail or take a very long
time for a real user, but turbo-hipster is far from perfect anyway and only
tests a couple of datasets so that risk is still there.

Are nova developers still getting value out of turbo-hipster or has it
achieved its goal and is it time for it to retire?

Thanks,
Josh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161004/1ca710bc/attachment.html>