OpenStack - User contributions [en]

Heat/GettingStartedUsingDevstack

2013-05-01T17:12:01Z

Sacharya: /* Configure DevStack to enable Heat */

== Heat and Devstack ==

Heat is fully integrated into [http://devstack.org/ DevStack]. This is a convenient way to try out or develop heat alongside the current development state of all the other [[OpenStack]] projects. Heat on DevStack works on both Ubuntu and Fedora.

These instructions assume you already have a working DevStack installation which can launch basic instances.

== Configure DevStack to enable Heat ==

Adding the following line to your `localrc` file will enable the heat services

<pre><nowiki>
ENABLED_SERVICES+=,heat,h-api,h-api-cfn,h-api-cw,h-eng
## It would also be useful to automatically download and register VM images that Heat can launch.
# 64bit image (~660MB)
IMAGE_URLS+=",http://fedorapeople.org/groups/heat/prebuilt-jeos-images/F17-x86_64-cfntools.qcow2"
# 32bit image (~640MB)
IMAGE_URLS+=",http://fedorapeople.org/groups/heat/prebuilt-jeos-images/F17-i386-cfntools.qcow2"
</nowiki></pre>

URLs for any of [http://fedorapeople.org/groups/heat/prebuilt-jeos-images/ these prebuilt JEOS images] can be specified.

That is all the configuration that is required. When you run `./stack.sh` the Heat processes will be launched in `screen` with the labels prefixed with `h-`.

== Confirming heat is responding ==

Before any heat commands can be run, the authentication environment needs to be loaded

<pre><nowiki>
source openrc
</nowiki></pre>

You can confirm that Heat is running and responding with this command

<pre><nowiki>
heat list
</nowiki></pre>

This should return an empty line

== Preparing Nova for running stacks ==

Enabling Heat in devstack will replace the default Nova flavors with flavours that the Heat example templates expect. You can see what those flavors are by running

<pre><nowiki>
nova flavor-list
</nowiki></pre>

Heat needs to launch instances with a keypair, so we need to generate one

<pre><nowiki>
nova keypair-add heat_key > heat_key.priv
chmod 600 heat_key.priv
</nowiki></pre>

== Launching a stack ==
Now lets launch a stack, assuming that DEST is left as the default /opt/stack

<pre><nowiki>
heat create teststack --template-file=/opt/stack/heat/templates/WordPress_Single_Instance.template --parameters="InstanceType=m1.large;DBUsername=wp;DBPassword=verybadpassword;KeyName=heat_key;LinuxDistribution=F17"
</nowiki></pre>

Which will respond

<pre><nowiki>
+--------------------------------------+-----------+--------------------+----------------------+
| ID | Name | Status | Created |
+--------------------------------------+-----------+--------------------+----------------------+
| (uuid) | teststack | CREATE_IN_PROGRESS | (timestamp) |
+--------------------------------------+-----------+--------------------+----------------------+
</nowiki></pre>

=== List stacks ===

<pre><nowiki>
heat list
</nowiki></pre>

=== List stack events ===

<pre><nowiki>
heat event-list teststack
</nowiki></pre>

=== Describe the wordpress stack ===

<pre><nowiki>
heat describe teststack
</nowiki></pre>

Note: After a few seconds, the stack_status should change from IN_PROGRESS to CREATE_COMPLETE.

=== Verify instance creation ===

Because the software takes some time to install from the repository, it may be a few minutes before the Wordpress instance is in a running state.

Point a web browser at the location given by the WebsiteURL Output as shown by heat stack-show teststack::

<pre><nowiki>
wget ${WebsiteURL}
</nowiki></pre>

=== Delete the instance when done ===

<pre><nowiki>
heat delete teststack
heat list
</nowiki></pre>

Note: This operation will show no running stack.

== Troubleshooting ==

If you encounter issues running heat, see if the solution to the issue is documented on the
[http://wiki.openstack.org/Heat/TroubleShooting Troubleshooting wiki page]. If not, let us know about the problem in the #heat IRC channel on freenode.

Heat/GettingStartedUsingDevstack

2013-05-01T17:11:43Z

Sacharya: /* Launching a stack */

== Heat and Devstack ==

Heat is fully integrated into [http://devstack.org/ DevStack]. This is a convenient way to try out or develop heat alongside the current development state of all the other [[OpenStack]] projects. Heat on DevStack works on both Ubuntu and Fedora.

These instructions assume you already have a working DevStack installation which can launch basic instances.

== Configure DevStack to enable Heat ==

Adding the following line to your `localrc` file will enable the heat services

<pre><nowiki>
ENABLED_SERVICES+=,heat,h-api,h-api-cfn,h-api-cw,h-eng
## It would also be useful to automatically download and register VM images that Heat can launch.
# 64bit image (~660MB)
IMAGE_URLS+=",http://fedorapeople.org/groups/heat/prebuilt-jeos-images/F16-x86_64-cfntools.qcow2"
# 32bit image (~640MB)
IMAGE_URLS+=",http://fedorapeople.org/groups/heat/prebuilt-jeos-images/F16-i386-cfntools.qcow2"
</nowiki></pre>

URLs for any of [http://fedorapeople.org/groups/heat/prebuilt-jeos-images/ these prebuilt JEOS images] can be specified.

That is all the configuration that is required. When you run `./stack.sh` the Heat processes will be launched in `screen` with the labels prefixed with `h-`.

== Confirming heat is responding ==

Before any heat commands can be run, the authentication environment needs to be loaded

<pre><nowiki>
source openrc
</nowiki></pre>

You can confirm that Heat is running and responding with this command

<pre><nowiki>
heat list
</nowiki></pre>

This should return an empty line

== Preparing Nova for running stacks ==

Enabling Heat in devstack will replace the default Nova flavors with flavours that the Heat example templates expect. You can see what those flavors are by running

<pre><nowiki>
nova flavor-list
</nowiki></pre>

Heat needs to launch instances with a keypair, so we need to generate one

<pre><nowiki>
nova keypair-add heat_key > heat_key.priv
chmod 600 heat_key.priv
</nowiki></pre>

== Launching a stack ==
Now lets launch a stack, assuming that DEST is left as the default /opt/stack

<pre><nowiki>
heat create teststack --template-file=/opt/stack/heat/templates/WordPress_Single_Instance.template --parameters="InstanceType=m1.large;DBUsername=wp;DBPassword=verybadpassword;KeyName=heat_key;LinuxDistribution=F17"
</nowiki></pre>

Which will respond

<pre><nowiki>
+--------------------------------------+-----------+--------------------+----------------------+
| ID | Name | Status | Created |
+--------------------------------------+-----------+--------------------+----------------------+
| (uuid) | teststack | CREATE_IN_PROGRESS | (timestamp) |
+--------------------------------------+-----------+--------------------+----------------------+
</nowiki></pre>

=== List stacks ===

<pre><nowiki>
heat list
</nowiki></pre>

=== List stack events ===

<pre><nowiki>
heat event-list teststack
</nowiki></pre>

=== Describe the wordpress stack ===

<pre><nowiki>
heat describe teststack
</nowiki></pre>

Note: After a few seconds, the stack_status should change from IN_PROGRESS to CREATE_COMPLETE.

=== Verify instance creation ===

Because the software takes some time to install from the repository, it may be a few minutes before the Wordpress instance is in a running state.

Point a web browser at the location given by the WebsiteURL Output as shown by heat stack-show teststack::

<pre><nowiki>
wget ${WebsiteURL}
</nowiki></pre>

=== Delete the instance when done ===

<pre><nowiki>
heat delete teststack
heat list
</nowiki></pre>

Note: This operation will show no running stack.

== Troubleshooting ==

If you encounter issues running heat, see if the solution to the issue is documented on the
[http://wiki.openstack.org/Heat/TroubleShooting Troubleshooting wiki page]. If not, let us know about the problem in the #heat IRC channel on freenode.