Go to file
Takashi Kajinami 81586711f5 Remove some notes no longer valid
setup.py is no longer maintained by the global sync. Also the note
in requirements.txt does not apply since pip 20.3.

[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-June/034073.html

Change-Id: I8c9fef97e5e62d1024da9231e2cbb96b15edbf80
2023-06-14 04:09:52 +09:00
2023-03-22 17:16:30 +00:00
2023-03-25 12:00:35 +09:00
2023-03-22 17:16:30 +00:00
2019-04-22 09:36:50 +05:30
2020-09-10 14:19:03 -04:00
2019-04-19 19:33:28 +00:00
2023-03-22 17:16:30 +00:00
2017-12-15 12:39:37 +05:30
2012-03-14 09:25:54 +11:00
2022-06-10 20:27:28 +03:00
2018-07-27 13:38:27 +00:00
2018-01-28 09:11:18 +05:30
2020-04-09 14:14:38 +08:00
2023-06-14 04:09:52 +09:00
2021-01-06 16:28:32 +08: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%