Ask Your Question

heat orchestration service - purpose?

asked 2020-04-14 00:33:20 -0500

happy75 gravatar image

Hi Openstack experts, With the heat orchestration service, does that allow you to automate the creation of a number of VM instances in one go (and can you specify the different specification for the instances e.g. different size of CPU/memory/disk/network for all the instances)? Can you use that to automate the creation of containers within the cloud (if the cloud contains the swift service)?


edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2020-04-30 11:55:17 -0500

zaneb gravatar image

Heat provides a declarative user interface to OpenStack resources. You give it a template and it figures out how to create all of the resources in the right order (if they are dependent on each other) and does it for you. You can update the stack with a modified template, or delete it altogether, and it figures out how to do that for you too.

In general it supports most resource types provided by OpenStack APIs (see the full list).

The Zun service provides an OpenStack API for spinning up (Linux) containers, and is supported by Heat.

edit flag offensive delete link more

answered 2020-04-14 02:01:47 -0500

updated 2020-04-14 02:04:31 -0500

Heat creates an application consisting of various cloud resources like instances, volumes and networks that are interconnected. You can create autoscaling applications where the number of instances depends on performance measures that you define. Yes, instance properties are defined by the Heat template that describes your application. Yes, Heat also allows the creation of Swift containers. See the Heat template guide.

A short video introducing Heat:

edit flag offensive delete link more


Thanks so does that mean heat does a similar job to ansible which can be used to automate the installation and configuration of VMs)?

happy75 gravatar imagehappy75 ( 2020-04-14 07:36:29 -0500 )edit

It can loosely be compared with Ansible, since it can also customize instances, but it also manages networks and other resources and can be used for autoscaling.

Bernd Bausch gravatar imageBernd Bausch ( 2020-04-14 08:42:21 -0500 )edit

so is that correct to say that heat can be used to automate the installation/configuration of instances and magnum is used to create containers within the instances?

happy75 gravatar imagehappy75 ( 2020-04-14 19:53:57 -0500 )edit

The first half is correct, but Heat does more than that.

Magnum doesn't create containers. It creates and manages container management environments based on Kubernetes, Mesos or Docker Swarm. To create containers, you use the tools of those environments.

Bernd Bausch gravatar imageBernd Bausch ( 2020-04-14 23:49:22 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2020-04-14 00:33:20 -0500

Seen: 52 times

Last updated: Apr 30 '20