Thanks Pavlo. It would be nice if the the heat template file could directly put as an input parameter to the stack-adopt.
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". Thank you and very appreciate it. Kind regards, - j On Fri, Mar 6, 2015 at 8:00 PM, Pavlo Shchelokovskyy < [email protected]> wrote: > Jupiter, > > 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. > > Best regards, > > Pavlo Shchelokovskyy > Software Engineer > Mirantis Inc > www.mirantis.com > > On Fri, Mar 6, 2015 at 10:47 AM, jupiter <[email protected]> wrote: > >> 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. >> >> $ head stack-adopt -a spec_HOT.yml test_stack >> >> Thank you. >> >> Kind regards, >> >> - j >> >> >> >> >> On Fri, Mar 6, 2015 at 3:33 AM, Pavlo Shchelokovskyy < >> [email protected]> wrote: >> >>> Hi, >>> >>> 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. >>> >>> [1] https://review.openstack.org/#/c/124707/ >>> [2] https://review.openstack.org/#/c/134848/ >>> >>> Best regards, >>> >>> Pavlo Shchelokovskyy >>> Software Engineer >>> Mirantis Inc >>> www.mirantis.com >>> >>> On Thu, Mar 5, 2015 at 6:27 AM, jupiter <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> 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. >>>> >>>> Is there anyway to force heat to use existing VMs name, or to add >>>> existing VMs to heat stack? >>>> >>>> Thank you. >>>> >>>> - j >>>> >>>> _______________________________________________ >>>> Mailing list: >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>>> Post to : [email protected] >>>> Unsubscribe : >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>>> >>>> >>> >>> _______________________________________________ >>> Mailing list: >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> Post to : [email protected] >>> Unsubscribe : >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> >>> >> > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : [email protected] > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
