OpenStack Orchestration (Heat)
Go to file
Michael Ionkin 3cf288bc8c no need to run integration tests in upgrade
the purpose of upgrade script is to upgrade service,
and heat shouldn't run any jobs inside of that. moreover
there is no benefit in executing these tests after upgrade
because it doesn't test anything related to upgrades:
if heat is correctly configured after upgrade it will be ready
to run tests (but this can be covered by usual integration job).
heat should be testing specific things like
updating stacks after migration to the new openstack code,
deleting stacks and so on.

Co-authored-by: Vitaly Gridnev <vgridnev@mirantis.com>
Change-Id: Ie600dfc09db0ffa91609f92be4b9ef27259b5314
2016-08-11 08:01:41 +00:00
api-ref/source Fix software config api-ref doc 2016-08-07 23:46:17 -04:00
bin Fix heat-keystone-setup-domain 2016-05-16 07:38:46 +00:00
contrib modify the home-page info with the developer documentation 2016-07-29 09:34:10 +08:00
devstack no need to run integration tests in upgrade 2016-08-11 08:01:41 +00:00
doc Merge "Update HOT template guide preface" 2016-08-09 15:15:53 +00:00
etc/heat Merge "Add stack files retrieval API" 2016-07-12 11:20:30 +00:00
heat Merge "Adds some infos for stack notification" 2016-08-10 04:01:40 +00:00
heat_integrationtests Merge "Add scenario test_server_signal" 2016-08-04 13:26:29 +00:00
heat_upgradetests In-tree grenade support for Heat 2015-07-02 17:23:22 +05:30
install-guide/source Install Guide: Set bug project 2016-06-24 15:34:11 +02:00
rally-scenarios Rally tests plugins for Heat 2016-03-02 12:20:37 -05:00
releasenotes Release note, api-ref for event list nested_depth 2016-08-04 12:18:31 +12:00
tools Refactor confusing code in custom_guidelines.py 2016-05-09 11:38:56 -04:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:26:58 +00:00
.gitignore Create integration tests requirements on the fly 2016-03-25 13:40:50 +00:00
.gitreview Update .gitreview for org move. 2012-12-02 17:46:15 +00:00
.testr.conf Add separate requirements.txt to integration tests 2015-04-01 09:02:13 +00:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:36 +00:00
HACKING.rst Restrict use of iteritems, iterkeys and itervalues 2016-03-23 10:05:54 +00:00
LICENSE Initial commit (basics copied from glance) 2012-03-13 21:48:07 +11:00
README.rst Add aodh client plugin 2016-06-24 09:07:51 +00:00
babel.cfg Add setup.py and friends 2012-03-14 09:25:54 +11:00
bandit.yaml tox environment for `bandit` 2015-07-08 09:13:35 -04:00
config-generator.conf Move heat_keystoneclient to clients package 2016-06-01 16:27:01 +05:30
install.sh install.sh: stop using deprecated option group for rabbit 2015-09-01 19:01:34 +02:00
openstack-common.conf Switch to oslo.service 2015-06-23 08:30:39 +02:00
pylintrc Directives to not use variable names that conflict with pdb 2012-03-20 07:16:16 -04:00
requirements.txt Updated from global requirements 2016-08-08 11:50:04 +00:00
setup.cfg Support 'conditions' section for templates 2016-08-03 09:17:31 +08:00
setup.py Updated from global requirements 2015-09-22 10:40:48 +00:00
test-requirements.txt Updated from global requirements 2016-08-08 11:50:04 +00:00
tox.ini Merge "Always use upper-constraints" 2016-07-29 17:18:45 +00:00
uninstall.sh use stderr for error echo message 2016-01-17 05:20:40 +00:00

README.rst

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

https://git.openstack.org/cgit/openstack/python-heatclient

References

We have integration with