Open Stack

On 17/02/14 23:43, Robert Collins wrote:
> So we experimented with the ci-overcloud (a TripleO deployed cloud for
> running CI for TripleO) and it uncovered some bugs/limitations in
> nodepool and zuul.
> 
> We need to fix these to reduce our negative impact on the
> Openstack-infra team, before they'll be comfortable having the
> ci-overcloud back in rotation... and certainly before we can start
> checking  /  gating (because the reality is, until we're truely
> stable, things will go wrong).
> 
> https://bugs.launchpad.net/openstack-ci/+bug/1281319
I'll take a look at this one.

> https://bugs.launchpad.net/openstack-ci/+bug/1281320
> 
> One bug is to teach nodepool to startup even if a provider can't be
> contacted. The other is to have zuul timeout jobs that don't start at
> all. Both should be small - < 1 day of dev for a cold start on the
> project. Pure python.
> 
> -Rob
>