[OpenStack-Infra] Status of check-tempest-dsvm-f20 job

2014-06-18 Thread Eoghan Glynn
Hi infra-ninjas, I missed this thread originally, not previously having been subscribed to os-infra ML. So I just wanted to throw out onto the table a (possibly naïve) alternative way of looking at this issue. The core problem seems to be that the node allocation algorithm has a tendency to ske

Re: [OpenStack-Infra] Status of check-tempest-dsvm-f20 job

2014-06-18 Thread Eoghan Glynn
> On 06/18/2014 06:46 PM, Eoghan Glynn wrote: > > If we were to use f20 more widely in the gate (not to entirely > > supplant precise, more just to split the load more evenly) then > > would the problem observed tend to naturally resolve itself? > > I would be happ

Re: [OpenStack-Infra] Status of check-tempest-dsvm-f20 job

2014-06-18 Thread Eoghan Glynn
> On 06/18/2014 05:45 AM, Eoghan Glynn wrote: > > > > > >> On 06/18/2014 06:46 PM, Eoghan Glynn wrote: > >>> If we were to use f20 more widely in the gate (not to entirely > >>> supplant precise, more just to split the load more evenly) then &g

Re: [OpenStack-Infra] Status of check-tempest-dsvm-f20 job

2014-06-18 Thread Eoghan Glynn
> >> >>> If we were to use f20 more widely in the gate (not to entirely > >> >>> supplant precise, more just to split the load more evenly) then > >> >>> would the problem observed tend to naturally resolve itself? > >> >> > >> >> I would be happy to see that, having spent some time on the Fedora

Re: [OpenStack-Infra] Status of check-tempest-dsvm-f20 job

2014-06-18 Thread Eoghan Glynn
- Original Message - > On Wed, Jun 18, 2014 at 2:44 PM, Eoghan Glynn wrote: > > > > > >> >> >>> If we were to use f20 more widely in the gate (not to entirely > >> >> >>> supplant precise, more just to split the load m

Re: [OpenStack-Infra] Status of check-tempest-dsvm-f20 job

2014-06-18 Thread Eoghan Glynn
> On 06/18/2014 03:10 PM, Clark Boylan wrote: > > We are working on Trusty honest (I just got nodepool to build our > > first Trusty images), and that solves this problem. There is a bigger > > underlying issue in that projects should not depend on things like > > mongodb versions which are not a