Re: [openstack-dev] [nova] Future of turbo-hipster CI

2016-10-05 Thread Joshua Hesketh
On Wed, Oct 5, 2016 at 12:39 AM, Dan Smith wrote: > > Having said that, I think Dan Smith came across a fairly large > > production DB dataset recently which he was using for testing some > > archive changes, maybe Dan will become our new Johannes, but grumpier of > > course. :) > > That's quite

Re: [openstack-dev] [nova] Future of turbo-hipster CI

2016-10-05 Thread Joshua Hesketh
On Wed, Oct 5, 2016 at 12:02 AM, Dean Troyer wrote: > On Mon, Oct 3, 2016 at 11:29 PM, Joshua Hesketh > wrote: > >> 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

Re: [openstack-dev] [nova] Future of turbo-hipster CI

2016-10-05 Thread Joshua Hesketh
On Tue, Oct 4, 2016 at 11:49 PM, Matt Riedemann wrote: > On 10/3/2016 11:29 PM, Joshua Hesketh wrote: > >> 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

Re: [openstack-dev] [nova] Future of turbo-hipster CI

2016-10-04 Thread Dan Smith
> Having said that, I think Dan Smith came across a fairly large > production DB dataset recently which he was using for testing some > archive changes, maybe Dan will become our new Johannes, but grumpier of > course. :) That's quite an insult to Johannes :) While working on the db archiving thi

Re: [openstack-dev] [nova] Future of turbo-hipster CI

2016-10-04 Thread Dean Troyer
On Mon, Oct 3, 2016 at 11:29 PM, Joshua Hesketh wrote: > 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. > Is there any value i

Re: [openstack-dev] [nova] Future of turbo-hipster CI

2016-10-04 Thread Matt Riedemann
On 10/3/2016 11:29 PM, Joshua Hesketh wrote: 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

[openstack-dev] [nova] Future of turbo-hipster CI

2016-10-03 Thread Joshua Hesketh
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 downtime