OpenStack Orchestration (Heat)
Go to file
ghanshyam 98723966ce Set Tempest's service_availability setting for Heat
Tempest's service_availability config option includes all the service
availability which is further used by tests to take decision of skip
or run the test.

For example, [service_availability].heat is true then, heat test will run
or if [service_availability].heat is false then, all the heat related tests either
in heat tempest plugin or any other plugins will be skipped.

Currently this setting for heat service[1] is in devstack lib/tempest
which is being removed by - https://review.openstack.org/#/c/619973/

For better maintenance, we are moving all tempest non-owned service setting
to service devstack plugin side.

This commit add the setting of heat service on ceilometer devstack plugin.

Related-Bug: #1743688
[1] d6b253502a/heat_tempest_plugin/config.py (L15)

Depends-On: https://review.openstack.org/#/c/619990/
Change-Id: I5013ce8be1a4fb5219ea89a63add812558191025
Needed-By: https://review.openstack.org/#/c/619973/
2018-11-26 10:03:01 +00: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 Set Tempest's service_availability setting for Heat 2018-11-26 10:03:01 +00:00
doc Add heat-status to man page output 2018-11-12 09:23:28 +05:30
etc/heat Restore auth-less version negotiation 2018-06-12 10:57:08 +00:00
heat Merge "Return execution state_info in ExternalResource" 2018-11-22 08:58:48 +00: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 Revert "Add openstack/placement as a required project for heat-grenade*" 2018-10-24 08:48:58 -04:00
rally-scenarios Adds doc8 check to pep8 2018-07-26 14:57:58 +07:00
releasenotes Merge "Add heat-status upgrade check command framework" 2018-11-11 01:17:41 +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 convert py35 jobs to py3 2018-11-11 06:16:36 +00: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 Add heat-status upgrade check command framework 2018-10-22 14:19:36 +00:00
requirements.txt Add heat-status upgrade check command framework 2018-10-22 14:19:36 +00:00
setup.cfg Merge "Add heat-status upgrade check command framework" 2018-11-11 01:17: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 change the dist name to 'openstack-heat' 2018-11-01 11:54:05 -04: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