When executing "heat stack-update", can SoftwareDevelopment be used without rebooting its VM

asked 2014-05-11 06:30:21 -0600

casperl gravatar image

updated 2015-08-03 18:24:52 -0600

smaffulli gravatar image

In my stack which has 4 VMs (we can name them as VM1, VM2, VM3 and VM4), I have a requirement to execute one script on VM1 when I execute heat stack-update** -f <my_stack_template_file> -p <my_param_list> each time.

VM1 can be associated with SoftwareConfig and SoftwareDevelopment resources.

VM1 can NOT be rebooted or rebuilt during execution of "heat stack-update".

My question is:

(1) If a SoftwareDevelopment is set as "UPDATE" in 'actions' field of template and associated with VM1 and SoftwareConfig and when "heat stack-update" happens, can the VM1 execute SoftwareConfig without reboot?

(2) If SoftwareConfig can be execute successfully for VM1, then what packages/tools should be installed in VM instance? Such as hook-script.py(http://git.openstack.org/cgit/opensta...), is this a must for SoftwareDevelopment?

(3) Is my software version(icehouse) proper to support SoftwareDevelopment and SoftwareConfig? Below is the version of my Openstack pakages:

root@heatorch:~# pip freeze

SoftwareDeployment introduction is as below: http://docs.openstack.org/developer/h...

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2014-06-03 16:06:54 -0600

Steve Baker gravatar image
  1. Yes, doing a stack-update which changes your config or deployment resources will not reboot the server. Instead the deployment resource will go into an IN_PROGRESS state until it is signalled that the server has completed the configuration change.
  2. You do need to build your own image which contains the required agent and hooks to perform your configuration. The hooks and example templates are found in heat-templates software-config repo. There are instructions on how to build an image with every available hook but you are likely to only need one hook such as the one provided by the heat-config-script element.
  3. heat 2014.1 (icehouse release) is new enough to use software-config. python-heatclient release 0.2.9 is recommended for launching the stacks.
edit flag offensive delete link more

answered 2014-05-12 12:22:11 -0600

tarawa1943 gravatar image

I am not sure why pip failed on the install of the glanceclient but using the regular aptitude install, all the clients installed correctly. This is a circumvention not a solution. wm

apt-get install python-troveclient; apt-get install python-swiftclient; apt-get install python-novaclient; apt-get install python-neutronclient; apt-get install python-keystoneclient; apt-get install python-heatclient; apt-get install python-cinderclient; apt-get install python-ceilometerclient; apt-get install python-glanceclient
edit flag offensive delete link more


Actually I didn't meet pip install failure.

casperl gravatar imagecasperl ( 2014-05-13 01:55:30 -0600 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-05-11 06:30:21 -0600

Seen: 1,602 times

Last updated: Aug 03 '15