openstack
/
heat
Code Issues Proposed changes
OpenStack Orchestration (Heat)
15,072 Commits
8 Branches
38 Tags
208 MiB
Python 99.3%
Shell 0.7%
 
 
Go to file
Zane Bitter bb3ddcf573 Ensure Functions can be created without stack definition 
In a number of places we parse templates passing None as the stack
definition, in order to be able to extract information from the template
in cases where we don't actually need to resolve functions.

However, the GetParam and GetFile HOT functions require an actual stack
definition to be passed in order to initialise them. So far we haven't
encountered any cases where those functions appear where we pass None
for the stack definition. Ensure that all Functions can always be
created even with no stack definition.

Note that the cfn ParamRef class is not affected, as the Ref function
always selects the GetResource implementation when the stack definition
is None.

Change-Id: Ic947dcdc17e9dbc58459a92ba970c292d70578cd
 		2018-10-18 17:00:10 -04:00
api-ref/source Add API doc for files_container support 2018-07-26 09:50:54 +05:30
bin Remove CloudWatch API 2018-01-28 09:11:17 +05:30
contrib/heat_docker Merge "Docs: modernise links" 2018-04-27 11:36:18 +00:00
devstack Run the specified set of tests in grenade-multinode job 2018-03-02 12:16:51 +07:00
doc Change "services" to "service" 2018-10-18 18:14:13 +08:00
etc/heat Restore auth-less version negotiation 2018-06-12 10:57:08 +00:00
heat Ensure Functions can be created without stack definition 2018-10-18 17:00:10 -04:00
heat_integrationtests Merge "Remove unnecessary shebangs from service scripts" 2018-09-10 05:01:27 +00:00
heat_upgradetests In-tree grenade support for Heat 2015-07-02 17:23:22 +05:30
playbooks/devstack Merge "Add openstack/placement as a required project for heat-grenade*" 2018-10-03 16:08:17 +00:00
rally-scenarios Adds doc8 check to pep8 2018-07-26 14:57:58 +07:00
releasenotes Imported Translations from Zanata 2018-10-08 06:24:05 +00:00
tools Add StoryBoard migration docs and releasenote 2018-07-26 13:05:04 +08: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 Update .gitreview for org move. 2012-12-02 17:46:15 +00:00
.stestr.conf Use stestr for unit tests 2017-12-15 12:39:37 +05:30
.zuul.yaml Add openstack/placement as a required project for heat-grenade* 2018-09-30 11:51:16 -04:00
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
LICENSE Initial commit (basics copied from glance) 2012-03-13 21:48:07 +11:00
README.rst Merge "Drop ceilometerclient requirement" 2018-08-09 10:21:34 +00:00
babel.cfg Add setup.py and friends 2012-03-14 09:25:54 +11:00
config-generator.conf Remove SSLMiddleware from oslo.config namespace 2017-11-27 13:05:00 +05:30
install.sh Remove use of heat_watch_server_url 2018-01-28 09:11:18 +05:30
lower-constraints.txt Merge "Clean up test requirements" 2018-08-03 07:43:35 +00:00
requirements.txt Drop ceilometerclient requirement 2018-08-08 16:56:41 +00:00
setup.cfg Drop ceilometerclient requirement 2018-08-08 16:56:41 +00:00
setup.py Updated from global requirements 2017-03-02 17:42:22 +00:00
test-requirements.txt Merge "Clean up test requirements" 2018-08-03 07:43:35 +00:00
tox.ini Don't quote {posargs} in tox.ini 2018-10-09 10:13:15 +07:00
uninstall.sh use stderr for error echo message 2016-01-17 05:20:40 +00:00

README.rst

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://git.openstack.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