Open Stack

On Tue, Jun 28, 2016, at 08:18 PM, James E. Blair wrote:
> Clark Boylan <cboylan at sapwetik.org> writes:
> 
> > Could we do this by slightly changing the zuul gearman protocol to drop
> > the "label" suffix and expect that all jobs have this hardcoded? Then we
> > could do the second option and we would have:
> >
> > build:tempest-trusty
> > build:tempest-xenial
> >
> > This should come out to roughly the same number of jobs registered as we
> > have today.
> 
> Yes, especially if we just do that in the zuul launcher which we aren't
> recommending anyone else use at this point.  Doesn't really need to be a
> change in the protocol as much as an intentionally incomplete
> implementation.  :)
> 
> We could adopt the convention of suffixing the job names for, say,
> tempest jobs but leave other jobs (such as translations) alone since
> they only have one potential node anyway.
> 
> (As an aside, in retrospect, having the workers register the *labels*
> and have the job name as payload rather than registering *jobs* might
> have been a better approach.  It would certainly solve the immediate
> technical problem, but as it does not improve the user experience is not
> something that I think we should do in Zuul v2 and should instead focus
> on doing things right in v3.)

I went ahead and pushed a change that should implement this,
https://review.openstack.org/336311. On grepping through zuul's codebase
this should be sufficient as long as we don't use the ZUUL_NODE
parameter anywhere and we currently don't.

Clark