<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2017-06-09 22:18 GMT+02:00 Paul Belanger <span dir="ltr"><<a href="mailto:pabelanger@redhat.com" target="_blank">pabelanger@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-HOEnZb"><div class="gmail-h5">On Fri, Jun 09, 2017 at 07:58:44PM +0000, Jeremy Stanley wrote:<br>
> On 2017-06-07 14:26:10 +0800 (+0800), Xinliang Liu wrote:<br>
> [...]<br>
> > we already have our own pre-built debian cloud image, could I just<br>
> > use it and not use the one built by diskimage-builder?<br>
> [...]<br>
><br>
> The short answer is that nodepool doesn't currently have support for<br>
> directly using an image provided independent of its own image build<br>
> process. Clark was suggesting[*] in IRC today that it might be<br>
> possible to inject records into Zookeeper (acting as a "fake"<br>
> nodepool-builder daemon basically) to accomplish this, but nobody<br>
> has yet implemented such a solution to our knowledge.<br>
><br>
> Longer term, I think we do want a feature in nodepool to be able to<br>
> specify the ID of a prebuilt image for a label/provider (at least we<br>
> discussed that we wouldn't reject the idea if someone proposed a<br>
> suitable implementation). Just be aware that nodepool's use of<br>
> diskimage-builder to regularly rebuild images is intentional and<br>
> useful since it ensures images are updated with the latest packages,<br>
> kernels, warm caches and whatever else you specify in your elements<br>
> so reducing job runtimes as they spend less effort updating these<br>
> things on every run.<br>
><br>
> [*] <URL: <a href="http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2017-06-09.log.html#t2017-06-09T15:32:27-2" rel="noreferrer" target="_blank">http://eavesdrop.openstack.<wbr>org/irclogs/%23openstack-<wbr>infra/%23openstack-infra.2017-<wbr>06-09.log.html#t2017-06-09T15:<wbr>32:27-2</a> ><br>
> --<br>
> Jeremy Stanley<br>
<br>
</div></div>Actually, I think 458073[1] aims to fix this use case.  I haven't tired it<br>
myself but it adds support for using images which are not built and managed by<br>
nodepool.<br>
<br>
This is currently only on feature/zuulv3 branch.<br>
<br>
[1] <a href="https://review.openstack.org/#/c/458073/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/458073/</a><br>
<br></blockquote><div><br></div>That's right, support for cloud-images on feature/zuulv3 is now merged and working.<div>I just setup a Nodepool using this new feature over the weekend.</div><div><br></div><div>This is a nodepool.yaml that can help you get going:</div><div><br></div><div><a href="http://paste.openstack.org/show/612191/">http://paste.openstack.org/show/612191/</a><br></div><div><br></div><div>HTH</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> ______________________________<wbr>_________________<br>
> OpenStack-Infra mailing list<br>
> <a href="mailto:OpenStack-Infra@lists.openstack.org">OpenStack-Infra@lists.<wbr>openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-infra</a><br>
<br>
<br>
______________________________<wbr>_________________<br>
OpenStack-Infra mailing list<br>
<a href="mailto:OpenStack-Infra@lists.openstack.org">OpenStack-Infra@lists.<wbr>openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-infra</a></blockquote></div><br></div></div>