Go to file
David Hill 5bc84d6419 Add dns_domain support to OS::Neutron::ProviderNet
It is actually possible to set OS::Neutron::Net-dns_domain but
not OS::Neutron::ProviderNet-dns_domain with heat.   Since this
is allowed using python-neutronclient, there're no reasons to
not allow this using heat.

Change-Id: I5b085e469f3fd24c797d5dcaf39dbe56f6ad5cdf
Task: 36808
2020-02-24 23:02:41 +00:00
2018-01-28 09:11:17 +05:30
2019-08-01 08:53:27 +08:00
2019-04-22 09:36:50 +05:30
2018-02-01 15:38:25 +00:00
2019-04-19 19:33:28 +00:00
2017-12-15 12:39:37 +05:30
2019-07-01 16:18:19 +02:00
2012-03-14 09:25:54 +11:00
2019-06-26 17:48:15 +02:00
2018-07-27 13:38:27 +00:00
2018-01-28 09:11:18 +05:30
2019-07-31 17:19:40 +08:00
2017-03-02 17:42:22 +00:00
2019-07-22 18:55:34 +02:00
2016-01-17 05:20:40 +00:00

Team and repository tags

image

Heat

Heat is a service to orchestrate multiple composite cloud applications using templates, through both an OpenStack-native REST API and a CloudFormation-compatible Query API.

Why heat? It makes the clouds rise and keeps them there.

Getting Started

If you'd like to run from the master branch, you can clone the git repo:

git clone https://opendev.org/openstack/heat

Python client

Report a Story (a bug/blueprint)

If you'd like to report a Story (we used to call a bug/blueprint), you can report it under Report a story in Heat's StoryBoard. If you must report the story under other sub-project of heat, you can find them all in Heat StoryBoard Group. if you encounter any issue.

References

We have integration with

Description
OpenStack Orchestration (Heat)
Readme 214 MiB
Languages
Python 99.5%
Shell 0.5%