<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 25, 2021 at 8:38 PM Jeremy Stanley <<a href="mailto:fungi@yuggoth.org">fungi@yuggoth.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2021-03-25 14:47:09 +0000 (+0000), Sean Mooney wrote:<br>
> nova does not support create a base vm and then doing a local live<br>
> migration or restore for memory snapshots to create another vm.<br>
> <br>
> this approch likely has several security implciations that would<br>
> not be accpeatable in a multi tenant enviornment.<br>
> <br>
> we have disucssed this type of vm creation in the past and<br>
> determined that it is not a valid implematnion of spawn. a virt<br>
> driver that precreate vms or copys an existing instance can be<br>
> faster but that virt driver is not considered a compliant<br>
> implementation.<br>
> <br>
> so in short there is no way to achive this today in a compliant<br>
> openstack powered cloud.<br>
[...]<br>
<br>
The next best thing is basically what Nodepool[*] does: start new<br>
virtual machines ahead of time and keep them available in the<br>
tenant. This does of course mean you're occupying additional quota<br>
for whatever base "ready" capacity you've set for your various<br>
images/flavors, and that you need to be able to predict how many of<br>
what kinds of virtual machines you're going to need in advance.<br>
<br>
[*] <a href="https://zuul-ci.org/docs/nodepool/" rel="noreferrer" target="_blank">https://zuul-ci.org/docs/nodepool/</a></blockquote><div><br></div><div><br></div><div>Is it recommended to use nodepool in a production environment?</div><div><br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
-- <br>
Jeremy Stanley<br>
</blockquote></div></div>