Open Stack

On Tue, Nov 26, 2019 at 05:31:07PM +1100, Ian Wienand wrote:
> What I would propose is that projects do *not* have a single,
> top-level Dockerfile, but only (potentially many) specifically
> name-spaced versions.

> [2] I started looking at installing these together from a Dockerfile
>     in system-config.  The problem is that you have a "build context",
>     basically the directory the Dockerfile is in and everything under
>     it.

I started looking closely at this, and I think have reversed my
position from above.  That is, I think we should keep the OpenDev
related dockerfiles in system-config.

[1] is a change in system-config to add jobs to build openstacksdk,
diskimage-builder and nodepool-[builder|launcher] containers.  It does
this by having these projects as required-projects: in the job
configuration and copying the Dockerfile into the Zuul-checked-out
source (and using that as the build context).  A bit ugly, but it
works.

However, to use these jobs for nodepool CI requires importing them
into zuul/nodepool.  This is tested with [2].

However, Zuul just reports:

  This change depends on a change with an invalid configuration.

It only depends-on [1], which has a valid configuration, at least in
the opendev tenant.

I think that this has to do with the zuul tenant not having the
projects that are used by required-jobs: from the new system-config
jobs [3], but am not certain it doesn't have something else to do with
the config errors at [4].  I have filed [5] because at the minimum a
more helpful error would be good.

-i

[1] https://review.opendev.org/696000
[2] https://review.opendev.org/696486
[3] https://review.opendev.org/696859
[4] https://zuul.opendev.org/t/zuul/config-errors
[5] https://storyboard.openstack.org/#!/story/2006968