OpenStack Orchestration (Heat)
Go to file
Takashi Kajinami 14d2d859ef Set cache_ok to avoid SAWarning
Since sqlalchemy 1.4.14[1], the following warning is raised unless
the cache_ok flag is explicitly set in classes inheriting
TypeDecorator.

SAWarning: TypeDecorator Json() will not produce a cache key because
the ``cache_ok`` attribute is not set to True.  This can have
significant performance implications including some performance
degradations in comparison to prior SQLAlchemy versions.
Set this attribute to True if this type object's state is safe to use
in a cache key, or False to disable this warning. (Background on this
error at: https://sqlalche.me/e/14/cprf)

Because the flag was set to True by default in older releases, this
adds explicit cache_ok = True, to restore the previous behavior in
Wallaby and older. (wallaby u-c has SQLAlchemy===1.3.23 while xena u-c
has SQLAlchemy===1.4.23)

[1] 6967b45020

Change-Id: I6b84a626994543468f49373a554de44025576a9a
2022-06-15 10:35:35 +09:00
api-ref/source [goal] Deprecate the JSON formatted policy file 2021-06-17 01:35:45 +08:00
bin Fix hacking warnings 2020-04-16 06:43:27 +00:00
contrib/heat_docker Use unittest.mock instead of third party mock 2020-05-05 08:42:11 -05:00
devstack Use f36 instead of f33 for testing 2022-05-31 10:35:53 +02:00
doc Use f36 instead of f33 for testing 2022-05-31 10:35:53 +02:00
etc/heat Add a /healthcheck URL 2020-04-30 18:49:55 +02:00
heat Set cache_ok to avoid SAWarning 2022-06-15 10:35:35 +09:00
heat_integrationtests Use f36 instead of f33 for testing 2022-05-31 10:35:53 +02:00
heat_upgradetests In-tree grenade support for Heat 2015-07-02 17:23:22 +05:30
playbooks/devstack/functional Remove gabbi tempest plugin 2020-11-04 02:12:11 +00:00
rally-scenarios Switch to use opendev.org 2019-04-22 09:36:50 +05:30
releasenotes Merge "Update python testing as per zed cycle teting runtime" 2022-06-13 12:14:26 +00:00
roles/run-heat-tests Migrate functional test jobs to zuul v3 2020-01-07 09:38:04 +08:00
tools Fix lower-constraints errors 2020-09-10 14:19:03 -04:00
.coveragerc Update .coveragerc after the removal of openstack directory 2016-11-12 09:21:05 +05:30
.gitignore Ignore old 'vN-branch' tags when scanning for release notes 2020-03-27 17:44:43 +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 Merge "zuul: Declare queue at top level" 2022-06-13 12:14:30 +00:00
babel.cfg Add setup.py and friends 2012-03-14 09:25:54 +11:00
bindep.txt Remove python2 from bindep 2022-06-10 20:27:28 +03:00
config-generator.conf Merge "Add missing [oslo_reports] options" 2021-09-21 02:15:31 +00:00
CONTRIBUTING.rst [ussuri][goal] Update contributor documentation 2021-05-31 20:37:14 +00: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
README.rst Add ironic client plugin support 2020-04-09 14:14:38 +08:00
requirements.txt Drop lower-constraints.txt and its testing 2022-04-30 15:41:05 -05:00
setup.cfg Update python testing as per zed cycle teting runtime 2022-06-04 11:39:19 +08:00
setup.py Disable auto discovery 2022-03-29 01:15:03 +10:00
test-requirements.txt Update doc8 version 2021-01-06 16:28:32 +08:00
tox.ini Merge "Update python testing as per zed cycle teting runtime" 2022-06-13 12:14:26 +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