<div dir="ltr"><div>Hi,<br><br></div>I am running heat version 0.3.0. I tried to run stack_adopt, but got following error "ERROR: No template specified"<br><br>$ heat stack-adopt -a data.txt adopted_stack<br><br><div><div><div class="gmail_extra">/usr/lib/python2.6/site-packages/heatclient/shell.py:26: DeprecationWarning: The oslo namespace package is deprecated. Please use oslo_utils instead.<br> from oslo.utils import encodeutils<br>/usr/lib/python2.6/site-packages/keystoneclient/i18n.py:21: DeprecationWarning: The oslo namespace package is deprecated. Please use oslo_i18n instead.<br> from oslo import i18n<br>/usr/lib/python2.6/site-packages/keystoneclient/session.py:20: DeprecationWarning: The oslo namespace package is deprecated. Please use oslo_config instead.<br> from oslo.config import cfg<br>/usr/lib/python2.6/site-packages/keystoneclient/session.py:21: DeprecationWarning: The oslo namespace package is deprecated. Please use oslo_serialization instead.<br> from oslo.serialization import jsonutils<br>ERROR: No template specified<br><br></div><div class="gmail_extra">The data.txt is a json file outputed from stack_abando -O. My understanding is there is no template file it could specify, what is the error about?<br><br></div><div class="gmail_extra">Thank you.<br><br></div><div class="gmail_extra">Kind regards,<br><br></div><div class="gmail_extra">- j<br><br></div><div class="gmail_extra"><div class="gmail_quote">On Mon, Mar 9, 2015 at 9:18 PM, jupiter <span dir="ltr"><<a href="mailto:jupiter.hce@gmail.com" target="_blank">jupiter.hce@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div>Thanks Pavlo. It would be nice if the the heat template file could directly put as an input parameter to the stack-adopt. <br><br>Anyway, I guess I have to convert the heat template file into a stack-adopt data file similar to the format of the "stack-abandon -O data.txt", then run "heat stack-adopt -a data.txt adopted_stack".<br><br></div>Thank you and very appreciate it.<br><br></div>Kind regards,<br><br></div> - j<br></div><div class=""><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 6, 2015 at 8:00 PM, Pavlo Shchelokovskyy <span dir="ltr"><<a href="mailto:pshchelokovskyy@mirantis.com" target="_blank">pshchelokovskyy@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div>Jupiter,<br><br></div>not exactly. Adopt takes a so called "abandon data" as input, which is an output of heat stack-abandon. It is somewhat similar to a template but not completely. You can try creating and abandoning a stack to see how it looks like.<br><br></div>Best regards,<br></div><div class="gmail_extra"><span><br clear="all"><div><div><div dir="ltr">Pavlo Shchelokovskyy<div>Software Engineer</div><div>Mirantis Inc</div><div><a href="http://www.mirantis.com" target="_blank">www.mirantis.com</a></div></div></div></div>
<br></span><div><div><div class="gmail_quote">On Fri, Mar 6, 2015 at 10:47 AM, jupiter <span dir="ltr"><<a href="mailto:jupiter.hce@gmail.com" target="_blank">jupiter.hce@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div><div>Thanks Pavio and Richard. Should the -a <HOT templete file> be used for passing the heat template file? Please correct me if thefollowing command is wrong.<br><br></div>$ head stack-adopt -a spec_HOT.yml test_stack<br><br></div>Thank you.<br><br></div>Kind regards,<br><br></div>- j<br><div><div><div><br><br><div> <br></div></div></div></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 6, 2015 at 3:33 AM, Pavlo Shchelokovskyy <span dir="ltr"><<a href="mailto:pshchelokovskyy@mirantis.com" target="_blank">pshchelokovskyy@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div>Hi,<br><br></div>you could try to play with adopt/abandon feature, e.g. forge an adopt data, but beware it is buggy. An alternative approach was discussed during last summit, and here are the specs of for might be relevant to your use case ([1] and [2]), but they are not approved yet.<br><br>[1] <a href="https://review.openstack.org/#/c/124707/" target="_blank">https://review.openstack.org/#/c/124707/</a><br>[2] <a href="https://review.openstack.org/#/c/134848/" target="_blank">https://review.openstack.org/#/c/134848/</a><br><br></div>Best regards,<br></div><div class="gmail_extra"><br clear="all"><div><div><div dir="ltr">Pavlo Shchelokovskyy<div>Software Engineer</div><div>Mirantis Inc</div><div><a href="http://www.mirantis.com" target="_blank">www.mirantis.com</a></div></div></div></div>
<br><div class="gmail_quote"><div><div>On Thu, Mar 5, 2015 at 6:27 AM, jupiter <span dir="ltr"><<a href="mailto:jupiter.hce@gmail.com" target="_blank">jupiter.hce@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><div dir="ltr"><div><div><div><div>Hi,<br><br></div>I have several VMs already created from nova command line, when I create a heat stack, the template list the those VMs name, but the heat stack-create did not pick up those VMs, instead created the new VMs with the same name.<br><br></div>Is there anyway to force heat to use existing VMs name, or to add existing VMs to heat stack?<br><br></div>Thank you.<span><font color="#888888"><br><br></font></span></div><span><font color="#888888">- j<br></font></span></div>
<br></div></div>_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div></div></div>