<div dir="ltr"><div>Thank you for your reply.</div><div><br></div>This approach has 3 disadvantages that I can think of:<div><br></div><div>1. An image might have configurations processes that only happen on the first boot and require user input. This is a probable use-case</div><div>2. Not all images support cloud-init</div><div>3. This creates an unnecessary load on the compute node.</div><div><br></div><div>I believe a create-in-shutoff-state is a more scalable, more robust approach.</div><div><br></div><div>Shoham Peller</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 27, 2016 at 11:06 AM, Rui Chen <span dir="ltr"><<a href="mailto:chenrui.momo@gmail.com" target="_blank">chenrui.momo@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Looks like we can use user_data and cloud-init to do this stuff.<div><br></div><div>Adding the following content into user_data.txt and launch instance like this: nova boot --user-data user_data.txt ..., </div><div>the instance will shutdown after boot is finished.</div><div><br></div><div><div>power_state:</div><div> mode: poweroff</div><div> message: Bye Bye</div></div><div><br></div><div>You can find more details in cloud-init document[1].</div><div><br></div><div>[1]: <a href="https://github.com/number5/cloud-init/blob/master/doc/examples/cloud-config.txt" target="_blank">https://github.com/number5/cloud-init/blob/master/doc/examples/cloud-config.txt</a></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2016-01-22 3:32 GMT+08:00 Fox, Kevin M <span dir="ltr"><<a href="mailto:Kevin.Fox@pnnl.gov" target="_blank">Kevin.Fox@pnnl.gov</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The nova instance user spec has a use case.<br>
<a href="https://review.openstack.org/#/c/222293/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/222293/</a><br>
<br>
Thanks,<br>
Kevin<br>
________________________________________<br>
From: Matt Riedemann [<a href="mailto:mriedem@linux.vnet.ibm.com" target="_blank">mriedem@linux.vnet.ibm.com</a>]<br>
Sent: Thursday, January 21, 2016 7:32 AM<br>
To: <a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a><br>
Subject: Re: [openstack-dev] [nova] Feature suggestion - API for creating VM without powering it up<br>
<div><div><br>
On 1/20/2016 10:57 AM, Shoham Peller wrote:<br>
> Hi,<br>
><br>
> I would like to suggest a feature in nova to allow creating a VM,<br>
> without powering it up.<br>
><br>
> If the user will be able to create a stopped VM, it will allow for<br>
> better flexibility and user automation.<br>
><br>
> I can personally say such a feature would greatly improve comfortability<br>
> of my work with nova - currently we shutdown each vm manually as we're<br>
> creating it.<br>
> What do you think?<br>
><br>
> Regards,<br>
> Shoham Peller<br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
What is your use case?<br>
<br>
--<br>
<br>
Thanks,<br>
<br>
Matt Riedemann<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>