OpenStack Orchestration (Heat)
Go to file
ricolin c8d1a9f901 Migrate functional test jobs to zuul v3
Something are introduced in this patch:
* As devstack-gate/devstack-vm-gate-wrap.sh is not really zuul v3
native, we move all configs in to `devstack/lib/heat` and .zuul.yaml.

* Remove extra configs process in devstack. Like setup tempest(which
is well covered by tempest itself.) or overlapping heat test configs setup.
Use tempest config for all heat_integration tests. Also remove
heat_integrationtests/common/configs since they're no longer required.

* copy post.yaml for grenade jobs. As we migrate to zuul v3 for
functional tests but not grenade (not yet), the post.yaml should exists
under grenade dir. since it's only required by grenade jobs.

* Use post.yaml in functional tests for cleanup test environments.

Story: #2007056
Task: #37908

Depends-On: https://review.opendev.org/701105
Change-Id: I4f531161a7222e2c2a21f8d483f9c2a1d91dc38d
2020-01-07 09:38:04 +08:00
api-ref/source Bump the openstackdocstheme extension to 1.20 2019-08-01 09:43:50 +08:00
bin Remove CloudWatch API 2018-01-28 09:11:17 +05:30
contrib/heat_docker Update devel info: mailing list 2018-12-05 09:02:33 +08:00
devstack Migrate functional test jobs to zuul v3 2020-01-07 09:38:04 +08:00
doc Merge "tox: Keeping going with docs" 2019-12-20 05:26:43 +00:00
etc/heat Restore auth-less version negotiation 2018-06-12 10:57:08 +00:00
heat Merge "Use resource description as default description property" 2019-12-19 12:33:48 +00:00
heat_integrationtests Migrate functional test jobs to zuul v3 2020-01-07 09:38:04 +08:00
heat_upgradetests In-tree grenade support for Heat 2015-07-02 17:23:22 +05:30
playbooks/devstack Migrate functional test jobs to zuul v3 2020-01-07 09:38:04 +08:00
rally-scenarios Switch to use opendev.org 2019-04-22 09:36:50 +05:30
releasenotes Merge "zun: add 'tty' property to container" 2019-12-19 08:23:21 +00:00
roles/run-heat-tests Migrate functional test jobs to zuul v3 2020-01-07 09:38:04 +08:00
tools pep8: Permit ".)" at the end of resource docs 2019-10-14 21:51:43 -04:00
.coveragerc Update .coveragerc after the removal of openstack directory 2016-11-12 09:21:05 +05:30
.gitignore include sample config file in docs 2018-02-01 15:38:25 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:33:28 +00:00
.stestr.conf Use stestr for unit tests 2017-12-15 12:39:37 +05:30
.zuul.yaml Migrate functional test jobs to zuul v3 2020-01-07 09:38:04 +08:00
babel.cfg Add setup.py and friends 2012-03-14 09:25:54 +11:00
bindep.txt Add local bindep.txt 2019-06-26 17:48:15 +02:00
config-generator.conf Remove SSLMiddleware from oslo.config namespace 2017-11-27 13:05:00 +05:30
CONTRIBUTING.rst Update http links for doc migration 2018-05-11 09:32:14 +08:00
HACKING.rst Clean up test requirements 2018-07-27 13:38:27 +00:00
install.sh Remove use of heat_watch_server_url 2018-01-28 09:11:18 +05:30
LICENSE Initial commit (basics copied from glance) 2012-03-13 21:48:07 +11:00
lower-constraints.txt Use client_retry_limit for keystone connection retry 2019-12-03 09:35:08 +05:30
README.rst Update readme 2019-10-31 17:50:05 +08:00
requirements.txt Use client_retry_limit for keystone connection retry 2019-12-03 09:35:08 +05:30
setup.cfg Drop Python2 support 2019-11-06 16:55:41 +08:00
setup.py Updated from global requirements 2017-03-02 17:42:22 +00:00
test-requirements.txt Blacklist bandit 1.6.0 and cap Sphinx on Python2 2019-05-14 16:50:24 -04:00
tox.ini Merge "tox: Keeping going with docs" 2019-12-20 05:26:43 +00:00
uninstall.sh use stderr for error echo message 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