Ask Your Question
0

OS::Heat::WaitCondition delete functionality

asked 2017-09-28 13:32:42 -0500

stevend gravatar image

Similarly to how OS::Heat::SoftwareDeployment allows the user to specify 'actions' with allowed values CREATE, UPDATE, DELETE, SUSPEND, RESUME to manage the lifecycle of the software deployment, is there a some functionality for OS::Heat::WaitCondition and/or Handle?

This would be helpful for software deployments that want to leverage the wait condition functionality for stack deletion as well as as for creation, update, etc...

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-09-29 10:58:46 -0500

zaneb gravatar image

If you're using software deployments, you don't need WaitConditions. A SoftwareDeployment resource will wait for the deployment to complete before marking the resource complete - in a sense it has the WaitCondition built in. So you can do exactly what you want using only SoftwareDeployments.

WaitConditions are primarily useful when you're not using SoftwareDeployments, but you want a signal to notify you when a server has fully booted.

edit flag offensive delete link more

Comments

Understood, using SoftwareDeployment would be easier. In my environment I'm limited to TEMP_URL_SIGNAL as the signal_transport, and during delete this is unreliable, stack delete fails 50% with this same error https://review.openstack.org/#/c/144317/ . A wait condition would be useful in this case

stevend gravatar imagestevend ( 2017-09-29 12:17:25 -0500 )edit

That sounds like a bug we want to fix. Could you report it in Launchpad?

zaneb gravatar imagezaneb ( 2017-10-02 09:03:38 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2017-09-28 13:32:42 -0500

Seen: 229 times

Last updated: Sep 29 '17