Open Stack

On Mon, Feb 19, 2018 at 10:23 AM, Paul Belanger <pabelanger at redhat.com>
wrote:

> On Mon, Feb 19, 2018 at 08:28:27AM -0500, David Shrewsbury wrote:
> > Hi,
> >
> > On Sun, Feb 18, 2018 at 10:25 PM, Ian Wienand <iwienand at redhat.com>
> wrote:
> >
> > > Hi,
> > >
> > > How should we go about restricting certain image builds to specific
> > > nodepool builder instances?  My immediate issue is with ARM64 image
> > > builds, which I only want to happen on a builder hosted in an ARM64
> > > cloud.
> > >
> > > Currently, the builders go through the image list and check "is the
> > > existing image missing or too old, if so, build" [1].  Additionally,
> > > all builders share a configuration file [2]; so builders don't know
> > > "who they are".
> > >
> > >
> >
> > Why not just split the builder configuration file? I don't see a need to
> > add code
> > to do this.
> >
> In our case (openstack-infra) this will require another change to
> puppet-nodepool to support this. Not that we cannot, but it will now mean
> we'll
> have 7[1] different nodepool configuration files to now manage. 4 x
> nodepool-launchers, 3 x nodepool-builders, since we have 7 services
> running.
>

We don't have to have 1 config file per builder. Just one additional file
for the
arm64 builder. The others can still share the config we have now.


-Dave
-- 
David Shrewsbury (Shrews)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20180219/9b8ad682/attachment.html>