OpenStack Orchestration (Heat)
Go to file
ricolin 6990331639 Support remote stack with another OpenStack provider
Allow OS::Heat::Stack to access remote stack from another OpenStack
provider. Also enable functional tests for multi-cloud.

Implement multi-cloud support as an extension to the existing multi-region
support. Allow operate a remote stack (from another OpenStack cloud) as a
resource in stack from local OpenStack cloud.

I propose we add multi cloud support into ``OS::Heat::Stack`` and change the
property schema for ``context``. Within context, we should adding
following properties:

* credential_secret_id: ID of Barbican Secret. Which stores authN
  information for remote cloud.

Service will use auth information from Barbican Secret to access
 Orchestration service in another OpenStack.
Must make sure you're able toget that secret from Barbican service when
provide `credential_secret_id` property.

Story: #2002126
Task: #26907
Depends-On: https://review.openstack.org/579750

Change-Id: I2f3de3e7c29cf7debb1474228c8a9a81725a72ed
2019-03-13 22:15:45 +08: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 Allow users to disable the tests run by Grenade 2019-03-01 22:47:28 +01:00
doc Merge "Fix indentation in HOT specification" 2019-02-18 08:53:45 +00:00
etc/heat Restore auth-less version negotiation 2018-06-12 10:57:08 +00:00
heat Support remote stack with another OpenStack provider 2019-03-13 22:15:45 +08:00
heat_integrationtests Support remote stack with another OpenStack provider 2019-03-13 22:15:45 +08:00
heat_upgradetests In-tree grenade support for Heat 2015-07-02 17:23:22 +05:30
playbooks/devstack Add heat-agents as required project 2019-01-03 18:16:52 +05:30
rally-scenarios Adds doc8 check to pep8 2018-07-26 14:57:58 +07:00
releasenotes Support remote stack with another OpenStack provider 2019-03-13 22:15:45 +08: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 Merge "Replace tripleo-scenario002-multinode with scenario002-standalone" 2019-01-21 11:13:26 +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 Add Release Notes in README 2018-11-12 10:02:46 +08: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 a Blazar Lease resource 2019-02-18 06:35:05 +00:00
requirements.txt Add a Blazar Lease resource 2019-02-18 06:35:05 +00:00
setup.cfg Heat support for Tap-as-a-Service resources 2019-01-30 21:01:21 +13: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