Orchestration with Heat

This article introduces the virtual machine service orchestration using OpenStack Heat available for Pouta.

You can access this feature in the web user interface's left hand panel or using the OpenStack or Heat command line client. Orchestration provides an easy way to create the entire infrastructure based on a reusable and human-readable template file. The template can describe many components of the infrastructure, such as servers, volumes and floating IPs. In the same file, it can attach the volumes and IPs to specific instances. A template can also define multiple instances connected to specific networks, some of which have floating IPs and some a volume attached. The file can also be used to modify the existing infrastructure.

Orchestration via the web user interface

Note

You should use "2016-10-14" or older as the Heat template version. Features in newer template versions may not be supported. Template versions

These instructions provide a simple example on how to set up a stack via the web user interface. To create a Heat stack, click the "Stacks" link in the Orchestration menu. The opened view displays all existing stacks and provides the button "Launch Stack" to launch a new stack. In the window which was opened after clicking the "Launch Stack" button, you can start configuring your stack. Selecting a template is mandatory, and the template data can also be provided as direct input, as depicted in the picture below. Note that this picture contains a valid, yet simple example of a template which builds two instances and displays the IP address of the first instance.

Template selection

After choosing "Next", the web user interface asks for a stack name and your password. After this, you can launch the stack. When the stack is built, it can be managed from the orchestration's Stacks view. The items which were built as a part of the stack can be found in their corresponding menus. In this case, the two instances can be seen and managed in the instances menu. In the stack's Overview tab (Orchestration -> Stacks -> click the stack), you can also see the output defined by the "outputs" section in the picture's example. To delete all components created by the stack template, simply press "Delete Stack" on the Stacks page.

Using orchestration with the command line client

Heat can be operated with the OpenStack command line client, but currently you can still use the deprecated Heat command line client as well. Create a stack on the command line:

openstack stack create -t /path/to/my/stack.yml my-heat-stack

Show the details of the newly created stack among other existing stacks:

openstack stack list
+--------------------------------------+---------------+-----------------+----------------------+--------------+
| ID                                   | Stack Name    | Stack Status    | Creation Time        | Updated Time |
+--------------------------------------+---------------+-----------------+----------------------+--------------+
| 98077bd5-9d69-47c3-98db-b0e19a60b1fa | my-heat-stack | CREATE_COMPLETE | 2016-06-08T07:34:46Z | None         |
+--------------------------------------+---------------+-----------------+----------------------+--------------+

Heat guidelines and command references

For more information, visit the OpenStack Heat wiki. For a full reference to the OpenStack command line client, see the command line reference, and for the Heat command line client, see the Heat CLI reference.

To try out the example provided here, modify at least the "key_name" in the template code:

heat_template_version: 2015-10-15

description: >
  Simple template to deploy
  a single instance in cPouta

resources:
  instance0:
    type: OS::Nova::Server
    properties:
      image: Ubuntu-16.04
      flavor: standard.tiny
      key_name: my-key
  instance1:
    type: OS::Nova::Server
    properties:
      image: CentOS-7
      flavor: standard.small
      key_name: my-key
outputs:
    server_networks:
      description: >
        Outputs the networks of the
        deployed server
      value: { get_attr: [instance0, networks] }

Last edited Tue Mar 24 2020