Open Stack

On 26/03/15 15:56, Matt Fischer wrote:
> We don't have heat stack-abandon enabled. It's marked as a "preview
> feature", have you had any issues?

It's fairly safe for this use case. If it's important for you that you 
don't lose track of your resources and you want to adopt them again 
later, it's a bit more dicey:

https://bugs.launchpad.net/heat/+bugs?field.tag=abandon-adopt

> Once you abandon the stack I assume
> you remove the resources outside of heat using nova/neutron etc?

Correct.

- ZB

> On Thu, Mar 26, 2015 at 1:15 PM, Ala Rezmerita
> <ala.rezmerita at cloudwatt.com <mailto:ala.rezmerita at cloudwatt.com>> wrote:
>
>     Hi Matt
>
>     I had similar problems with heat, and the work-around that i used is
>     to abandon the stack (heat stack-abandon),
>     and then I delete stack resources created  one by one.
>
>     Hope this helps.
>
>     Ala Rezmerita
>     Software Engineer || Cloudwatt
>     M: (+33) 06 77 43 23 91 <tel:%28%2B33%29%2006%2077%2043%2023%2091>
>     Immeuble Etik
>     892 rue Yves Kermen
>     92100 Boulogne-Billancourt – France
>
>     ------------------------------------------------------------------------
>     *De: *"Matt Fischer" <matt at mattfischer.com
>     <mailto:matt at mattfischer.com>>
>     *À: *openstack-dev at lists.openstack.org
>     <mailto:openstack-dev at lists.openstack.org>
>     *Envoyé: *Jeudi 26 Mars 2015 19:17:08
>     *Objet: *[openstack-dev] [heat] heat delete woes in Juno
>
>
>     Nobody on the operators list had any ideas on this, so re-posting here.
>
>     We've been having some issues with heatdelete-stack in Juno. The
>     issues generally fall into three categories:
>
>     1) it takes multiple calls to heat to delete a stack. Presumably due
>     to heat being unable to figure out the ordering on deletion and
>     resources being in use.
>
>     2) undeleteable stacks. Stacks that refuse to delete, get stuck in
>     DELETE_FAILED state. In this case, they show up in stack-list and
>     stack-show, yet resource-list and stack-delete deny their existence.
>     This means I can't be sure whether they have any real resources very
>     easily.
>
>     3) As a corollary to item 1, stacks for which heat can never unwind
>     the dependencies and stay in DELETE_IN_PROGRESS forever.
>
>     Does anyone have any work-arounds for these or recommendations on
>     cleanup? My main worry is removing a stack from the database that is
>     still consuming the customer's resources. I also don't just want to
>     remove stacks from the database and leave orphaned records in the DB.
>
>     __________________________________________________________________________
>     OpenStack Development Mailing List (not for usage questions)
>     Unsubscribe:
>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>     __________________________________________________________________________
>     OpenStack Development Mailing List (not for usage questions)
>     Unsubscribe:
>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>